I had tried the drivers modded on my platform X99, integrated in ISO
But it is not the correct version that installs for some drivers (version 10.1.1.44 instead of 10.1.2.86 for WellsburgSystem and WellsburgUSB)
I use those from Intel, the date is not important 
Do I understand correctly that HECI will be completely replaced if I install IME driver and after that HECI will not be used anymore and will not cause any troubles on my system in future? 
Am I right that three other INF files (tied to Wellsburg/Broadwell) are ok to have?
It also seems that no "extra files" were installed and I do not really need to use your "pure" package in case of my system?
Yes, I recommend to manually replace the Heci INF file by the real Intel ME driver from within the Device Manager.
Yes!
I doubt, that you didn’t get any bloatware installed, but these files are usually hidden.
Thank you very much for your help so far, Fernando.
As I will have some additional questions about IME itself, I hope you don’t mind I’ll move the rest of this discussion to the "proper" IME topic.
One last question about Chipset Device "Drivers":
I am using Far Manager with "Show hidden and system files" option turned on to search files, so it should help to find such normally "hidden" files.
But anyway, in your opinion: how "dangerous" is this "Intel’s hidden bloatware"?
Can it cause some troubles or conflicts?
Or it is just taking some additional storage space and I should not worry about it too much?
It is the latter option.
By the way: The installer itself will remain within the drive C, because there is no uninstall option for it.
Other bloatware may be found within the folder C:\Windows\Temp or C:\User<username>\AppData\Local\Temp.
@Fernando : I have most of my Temp folders moved to other drive (non system HDD) so space shouldn’t be an issue. Also, not every other application can be researched so well as you did with these drivers so sooner of later I will end up with some other “similar bloatwares” or installators taking some space on my drive - “one less” would not make such a big difference.
Anyway, if it is not “dangerous” for my system at all (and that’s the most important thing to me) I think I will use Intel’s original installer in latest version (10.1.2.86) to stick with official release for convenience of use and any updates in future. 
10.1.17415.8036
Note: The versioning scheme has changed
Note 2: It is possible that 17 is the year and 36 is the week (September 4-10, 2017). The setup signature is from the 6th of September so it could make sense. More samples are needed to figure that out for sure.
Intel_INF-Utility_v10.1.17415.8036_2k12-R2_64_2K16_64.rar (4.71 MB)
Update of the Start post
Changelog:
- new: "Intel Chipset Device Software v10.1.17415.8036 WHQL (original Set with installer)
-
new: “Latest Intel Chipset Device INF Files v10.1. Series WHQL” composed at 11/06/2017
(= AIO package with the “pure” original Intel Chipset Device INF files, extracted from the InstallerSet v10.1.17415.8036, shown with the wrong date 07/18/1968) -
new: “Latest Intel Chipset Device INF Files v10.1. Series mod+signed at 11/06/2017 by Fernando”
(= AIO package with the “pure” Intel Chipset Device INF files from the Installer Set v10.1.17415.8036, but correctly dated 08/08/2017)
Notes:
-
Intel has changed a lot of things with this new Intel Chipset Device Utility package:
- There is no differentiation anymore between “Normal” and “Enterprise” Edition Intel Chipsets/CPU systems. All systems are supported now by 1 single package.
- From now on the version number of the INF files has nothing to do with the compilation date (the higher the version number, the newer the files), but just with the related Intel CPU system.
Here are the version numbers of the INF files for the specific Intel CPU systems:- v10.1.19.1: Denverton
- v10.1.17.1: ApolloLake
- v10.1.13.2: Geminilake
- v10.1.11.1: KabyLakePCH-H
- v10.1.10.1: Kabylake
- v10.1.9.1: Lewisburg
- v10.1.8.1: Skylake-E
- v10.1.7.1: Skylake
- v10.1.6.1: SunrisePoint-H
- v10.1.5.1: SunrisePoint-LP
- v10.1.4.1: NULL_HECI
- v10.1.3.1: all other supported Intel Chipsets/CPU systems
- Thanks to plutomaniac for the package!
Any feedback is much appreciated.
If you should find any Intel chipset device, which is not supported by my original resp. modded “All-in-One packages”, please let me know it.
Regards
Dieter (alias Fernando)
it’s better to keep 10.1.2.86 for X99 and X299 ?
Broadwell-E are v10.1.3.1 and Skylake-E are v10.1.8.1 with this “new version”, and therefore more recent ?
Hello,
I don’t know if i post this in the right place,
But i installed the latest chipset ‘drivers’ but some drivers in the device manager wil never update. On my other laptop these always update to the same version as the rest of the chipset devices.
its about:
Inter(R) 8 Series/C220 Series USB EHCI #1 - 8C26 and #2 8C2D
The drivers are dated always: 21-6-2006 and version 10.0.150630.0 and are Microsoft drivers. Is there no new version, or why can’t they update with the rest of the devices, what are now version 10.1.3.1
(sorry for my bad English)
@Ricks :
Since you have already asked a rather similar question before, I gave you my answer >here<.
By the way: The “drivers” you are talking about do not belong to the so-named “Intel Chipset Drivers” and have nothing to do with the topic of this thread. The file named usbport.inf, which supports the Intel devices DEV_8C26 and DEV_8C2D, has been compiled by Microsoft and not by Intel.
I am looking for the newst and stable Intel Chipset Driver for Haswell. Maybe You can advice me in this, please.
What about the folders named “Haswell” or “HaswellE”, which can be found within the latest AIO packages?
By the way:
1. None of the Intel Chipset Device Software Sets do contain any real driver (= *.SYS file).
2. An installation resp. update of the specific Intel Chipset Device INF files only makes sense for brandnew Intel Chipset systems.
3. Users with an old Intel CPU (like Haswell) should not expect anything new or better from a freshly released Intel Chipset Device Utility.
Questions:
1. What is the reason for your request? Have you realized any PC stability problems, which may be caused by the Intel Chipset INF files?
2. Does your Device Manager show any yellow flagged device? If yes, which ones?
thanks Fernando, Can You write me where Can I find the latest AIP packeages, please?
I know that doesn’t do contain any real driver.
I am after clean instalation Windows 10 1709 version and I would like to only correct shows chipset devices in device manager. I don’t have any yellow flagged device. Do You think that I don’t need to install the chipset driver ?
As always in the past: The download links to these AIO packages (original with wrong dates and mod+signed with correct dates) are within the start post of this thread.
Yes, as long as all devices have been detected and managed by the Device Management, there is no need to install or to update any Intel Chipset Device INF file.
even it no shows that is Xeon proces E3-1200 v3/4th gen etc. - detected but without well name???
that’s Elan Smbus Driver no shows in device manager for example, but no any yellow flagged device. When I use script WUMT it shows me that Windows Update has update to Chipset to 10.1.1.38 ? Probabply when I will do update device by Windows Update it will install this version 10.1.1.38. But do I need this ?
Some of device shows only bridge Pci to Pci is correct ?
@Dromadus :
As long as the Device Manager doesn’t show any yellow flagged devices or “missing driver” messages, there is nothing to do or to worry about.