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?

Zitat von Fernando im Beitrag #1

---

Only users with a brandnew Intel chipset (from 8-Series up for Windows 7, from 9-Series up for Windows 8/8.1) or a very old Windows OS should install the latest suitable *.INF files for their specific Intel Chipset Devices to get rid from the "missing driver" message within the Device Manager.

---

@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.

Zitat von Fernando im Beitrag #424

---

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.

---

OK, that should solve "my problem". :)

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?

Thank you for explanation. :)

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?

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?

So, if I have all such files then the driver always installs 100% properly by clicking on INF file?

I'm sorry, yes, of course this is what I meant by "clicking". I should be more specific and use "selecting" word at least. :)

So, will the driver always work after such manual method of installation?