I’m using Windows 7 OS, i7-6850K CPU and X99 mainboard. I want to reinstall system with now "pure" version of INF files, but I’d like to know if I need them at all.
As I said earlier in this thread, after previous installation of full installer package I’ve found these INF files in my C:\Windows\INF folder: - oem2.inf - which supposed to be original WellsburgSystem.inf - oem3.inf - which supposed to be original WellsburgUSB.inf - oem4.inf - which supposed to be original NULL_HECISystem.inf - oem5.inf - which supposed to be original Broadwell-DESystem.inf
As you said, @Fernando , oem4.inf (=NULL_HECISystem.inf) will not be needed any more after installation of Intel Management Engine driver so I think I don’t need to install it. But what about the three other INF files?
Also, I’m not really sure - what "series" does my chipset belong to?
@Lex : This is what I recommend to do: 1. Download and unzip the latest AIO package with the latest Intel Chipset Device INF files (either the WHQL one with the wrong dates or the mod+signed one with correct dates). 2. Do a clean install of Win7 onto your system. 3. Once the OS is up and all Windows Updates are installed, look into the “System Devices” section of the Device Manager for devices with a “missing drivers” flag. 4. Right-click onto them, choose the options “Update driver software” > “Browse my computer” and navigate to the folder, where you have stored the AIO package with the Intel Chipset Device INF files. 5. The rest will be done automaticly by the Win7 Device Management, which will find itself the matching INF files. This way you will get only the useful INF files installed.
@Fernando : Thank you for answer. Last time I did like you said in step 3 - I’ve installed Chipset package just after installation of Windows 7 and all Windows Updates. My problem was that, for example, oem4.inf file (which was NULL_HECISystem.inf) was still present in C:\Windows\INF folder after installation of Intel MEI Driver v11.7.0.1045 - IMEI driver did not replace oem4.inf but created another one, oem32.inf.
This is absolutely normal. Even if you uninstall the related device from within the Device Manager or install the Intel MEI driveron-top of the Intel NULL_HECISystem.inf file, the related oemxx.inf file will remain within the Windows\INF folder. Nevertheless the related Intel INF file will not be used by the system anymore (you can check it by looking for the in-use driver of the device named “Intel(R) Management Engine Interface”). The only way to prevent the automatic installation of the NULL_HECISystem.inf file - done by the OS during the hardware detection part of the OS installation or by Windows Update later on - is to integrate the Intel MEI driver into the OS image.
Hmm… I am almost sure that this file was installed by my previous installation of all INF package (by using SetupChipset.exe) not by OS itself. What if I try to install IMEI drivers before Chipset INF? Can this be done in that order?
I have one more question - if NULL_HECISystem.inf can be "replaced" by installation of "proper IMEI driver", do you know any "proper drivers" that will render other three INFs (WellsburgSystem.inf, WellsburgUSB.inf, Broadwell-DESystem.inf) useless and also not needed any more?
No, there are no real drivers (= *.SYS files) available, which could be used instead of the Intel Chipset Device INF files. On the other hand there is nothing to worry about these few INF files, whose task is to tell the OS, that no real driver (= *.SYS file) is required for the related device.
So the plan is: a) Manually install WellsburgSystem.inf, WellsburgUSB.inf, Broadwell-DESystem.inf from your “pure” package. b) Manually install heci.inf from IMEI package listed in Section A1 (as plutomaniac told me) instead of NULL_HECISystem.inf.
For some devices, as I can see, there is possibility to install also “proper drivers” (with *.sys) just by pointing to the right INF file - one example I mentioned above (IMEI driver), the other can be AHCI driver. I think this is a good way to not install any additional “bloatware”, just the needed files.
The problem is that most of publishers does not use “zip” package for easy unpacking and manual installation but use “full installers” instead (like this SetupChipset.exe which contains INF files AND some installer). Are there any useful general tools to “unpack” such exe files without actually running them and then manually install these INF files which are hidden inside?
Some of these *.exe file Installer Sets can be unzipped with 7-zip. Others (like the Intel Chipset Device Software) can be extracted by running the *.exe file with a certain “Run” command (e.g.: “SetupChipset.exe -extract D:\Intel”), but a lot of them are not easy to be split or can only be partly extracted (like the Intel RST Installer).
If I manage to extract such exe file then is it always safe to use just INF file from inside or some INF files could not be prepared for such manual installation and such manually installed drivers will not always work 100% properly?
@Lex : What you need for a proper manual driver installation are the related *.SYS, *.INF and *.CAT files (some drivers need additionally a specific *.DLL file). All the other components are not essential for the function of the related device.
No, if you click onto the *.INF file, nothing will happen, because it is a simple text file. You have to open the related section of the Device Manager, right-click onto the matching device and choose the options “Update driver software” > “Browse my computer…” and navigate to the folder, which contains the related *.INF file.
As I never used your “pure” INF files I’m curious about one thing. Some of these INF files contains information for more than one device (for example Broadwell-DESystem.inf) - if I point one device to such inf file then: A) does Windows 7 auto-recognize other devices in this INF file and auto-install them as well B) I will need to point each device separately to the same file A or B?
BTW: Is latest release of Intel Chipset Device Software version 10.1.17464.8052 “not so official” one? I tried to find it on Intel’s website, but version 10.1.2.86 is still shown as the latest one for my system (X99). https://downloadcenter.intel.com/downloa…ver-for-Windows
Not Intel, but the mainboard manufacturer is responsible to offer appropriate up-to-date drivers for the customers of their product. 2. The Intel Download Center is not up-to-date regarding the Intel Chipset Device Software, because Intel doesn’t produce anymore Intel Chipset mainboards. 3. All WHQL certified Intel drivers (incl. the Intel Chipset INF files) are manufactured by Intel and officially released to the OEMs (mainboard and PC/Notebook manufacturers). That is why the Intel Chipset Device Utility v10.1.17464.8052 has been officially released by Intel.
I’ve just checked my ASUS website and they are still offering very old version of INF files, v10.1.2.19 - so, yeah, no comments for them. I know that Intel doesn’t produce mainboards anymore but it’s sad that it isn’t so easy for “average user” to find the latests versions.
What do you expect from the latest version of a text file, which contains nothing more than the information, that a) no driver is necessary and b) the related device should get a certain name with the word “Intel” in it?
