Can the mod+signed AIO package be integrated into Windows installation media?
It is no problem to integrate all the INF files (the question is, whether the OS Setup will accept them without WHQL stamp), but it wouldn’t make any sense, because more than 90% of the INF files are unusable for the specific system.
@Fernando : I’ve just did a “test installation” of fresh Windows 7 setup by using only “pure” *.inf drivers for all devices (the only exception was a video driver where I used setup.exe file to also get some of its software) and I would like to share my experiences as I have a few questions at the end to not make any mistakes on my next “normal installation”.
Info #1: Almost all “pure” drivers got installed without bigger problems - the only “serious problem” was caused by ASMedia USB 3.0/3.1 driver (I described it here) and it was corrected by using proper Windows 7 driver.
Info #2: Two of my “pure” drivers (for Intel Turbo Boost Max Technology 3.0 and Realtek HD Audio) actually registered themselves in “Control Panel” -> “Uninstall a program” and I can uninstall them that way, which is/was a big suprise for me after what I was told in answer to my post here that I will not be able to.
Info #3 (with questions): I’m still not sure if I properly installed “pure” Intel Chipset Device “drivers” - and that’s the main reason why I’m posting here, in this topic. My previous experience was very simple - I used SetupChipset.exe, got Chipset “drivers” installed and four files appeared in C:\Windows\INF directory:
1. oem2.inf - it was original WellsburgSystem.inf
2. oem3.inf - it was original WellsburgUSB.inf
3. oem4.inf - it was original NULL_HECISystem.inf
4. oem5.inf - it was original Broadwell-DESystem.inf
This time I was not going to use SetupChipset.exe - I was going to install “pure” inf files instead.
Question #1: File oem4.inf (NULL_HECISystem.inf) was going to be replaced by Intel ME Interface inf driver later so I decided to not install it - was it a right decision?
To get oem2.inf (WellsburgSystem.inf) and oem5.inf (Broadwell-DESystem.inf) installed I used this way:
A) I found one unknown “!” device for each file - it was:
- “PCI Device” for WellsburgSystem.inf
- “Base System Device” for Broadwell-DESystem.inf
B) After each file was installed (= moved to C:\Windows\INF directory) RMB -> Scan for hardware changes - this installed rest of devices included in these files.
Question #2: Were A and B steps ok? I’m not sure about this “Scan for hardware changes”, because here I got the answer as “I will need to point each device separately to the same file” - is manual way better?
Question #3: Some of devices from oem2.inf (WellsburgSystem.inf) and oem5.inf (Broadwell-DESystem.inf) were already “known” on my freshly installed system (they have some “basic” names, like “PCI standard ISA bridge”) but I remember that when I used SetupChipset.exe they still got replaced - should I manually force installation of inf files on such devices now just like SetupChipset.exe did in the past? Is Intel Chipset Device “driver” in any way better than original system Microsoft one? What about “descriptive” names of these alredy known devices?
Question #4: It is a question connected to #3 and about oem3.inf (WellsburgUSB.inf) - it contains only two devices:
- “Intel C610 series/X99 chipset USB Enhanced Host Controller #1 - 8D26”
- "Intel C610 series/X99 chipset USB Enhanced Host Controller #2 - 8D2D"
Both of them are already “known” as 2x "Standard Enhanced PCI to USB Host Controller"
I manually forced installation of WellsburgUSB.inf on these devices - but I do not know if it is ok? Reason “why I did this?” was “simple”: if I won’t force it then WellsburgUSB.inf file will not be installed at all and it was installed when I used SetupChipset.exe my previous time so I am not really sure what to do now.
Question #5: What happens if I point device to a directory where could be two (or more) separate inf files for it? For example: Realtek HD Audio driver has so many different inf files that I’m not sure if I should do this that way for it (or maybe use of setup.exe is a better way in this case).
If any installed driverpack is listed within the Control Panel’s “Uninstall a program” section, this is the proof, that the installed driverpack contained more than the “pure” drivers (e.g. an additional *.exe file). “Pure” drivers usually just consist of *.sys, *.inf, *.cat and maybe *.dll files, but never of *.exe files.
Yes!
To answer all your other questions here is my advice regarding the order and the procedure of the driver installation after having done a clean install of any Windows OS:
- Once the OS installation is completed, set the OS up-to-date by running Windows Update (if your network connection should not be available due to a missing driver, install the Network Controller driver as first step and then run Windows Update).
- Install the latest/best drivers for your Storage Controller (AHCI/RAID/NVMe), Graphics Controller, Network Controller (if not already done) and the device named “Intel(R) Management Engine Interface” (should be listed within the “System devices” section, if you are unsure, check the HardwareIDs). All related drivers can be installed manually from within the Device Manager by doing a right-click onto the related device and choosing the options “Update driver software” > “Browse my computer…” > “Browse” and navigating to the folder, which contains the related driver). If you should not have access to other important devices (e.g. USB Controllers), install the related drivers the same way.
- Now to the least important Intel Chipset Device INF files:
- Make sure, that you have access to the folder, which contains the “Latest Intel Chipset Device INF files” (either as WHQL or as mod+signed variant, in the latter case don’t forget to import the Certificate).
- Open the Device Manager and look for yellow flagged devices.
- Right-click - one after the other - onto all devices, which are yellow flagged or show the “Missing driver” message, and choose the options “Update driver software” > “Browse my computer…”. Then click onto the “Browse” button and navigate into the root of the folder, which contains all the Intel CPUs and their Chipset INF files. The OS Hardware Detection will find the suitable INF file itself (if there is any inside the folder and its various subfolders) and install it. If no suitable INF file should be found, you will get a related message. Don’t worry about getting a “wrong” driver/INF file installed!
- If finally there should still be one or more yellow flagged devices listed within the Device Manager, do a right-click onto them and check their HardwareIDs (“Properties” > “Details” > “Property” > “HardwareIDs”). Then you can do a Google search for the manufacturer (VEN_XXXX) and the model (DEV_XXXX) of the related device.
That’s it!
Don’t copy any INF files into the C:\Windows\Inf directory. Let the OS Hardware Management do the job.
So, for these devices not marked with yellow "!", I should not even try to install them from Intel Chipset Device INF package and leave them with Microsoft default OS inf?
What’s the difference between downloaded Intel and default Microsoft OS Chipset Device INF? Is it just the name?
As I said in my Questions #3 and #4, it seems that default setup (by using SetupChipset.exe) did some reinstallation of already known Device INFs, not just these with yellow "!"s.
No, the installation of these text files is only useful, if the OS Hardware Management doesn’t know what to do with the related devices. I repeat: None of the Intel Chipset Device INF file has a real function except to tell the OS, that the related device is manufactured by Intel and no driver is required to manage it.
Yes.
Yes.
Ah, so WellsburgUSB.inf looks like another file to "skip" (first one was NULL_HECISystem.inf as I explained earlier) - my OS already somehow managed to get the info about these two "USB Host Controllers" (as I explained in Question #4).
In the end I will need only some (not all) information from WellsburgSystem.inf and Broadwell-DESystem.inf.
I have one more question: for drivers like noted here (which shows in Control Panel after installation, like Realtek HD Audio) - should I still use inf-only way or maybe it is better to install them normally by using provided exe file?
Will there be any difference? Have you ever installed Realtek drivers? If yes then which way do you prefer? 
@Lex :
Everything depends on the user’s specific system and personal preferences.
For me the performance of my system has the highest priority. That is why I don’t like not essential software, which is filling up my system drive, or “Services”, which are permanently running in the background.
No, I neither need nor use the >500MB sized drivers and features package. I have sound, that’s all what I need and want.
So are you using Windows OS default audio drivers or something else?
It seems that this package takes 40MB after installation from inf file. I’ve started "full setup" exe and there are no other software options, "just drivers".
Yes, my Realtek HD Audio Controller is managed by the latest Win10 in-box MS HD Audio driver.
By the way: Your recent questions have nothing to do with the topic of this thread…
They were the result of your previous answers and I thought it would be nice to have all in one place for any other user who will want to follow.
Anyway, I know what I wanted to know for now - thank you for help. 
Possible to have the .inf latest drivers
http://station-drivers.com/index.php?opt…id=3315&lang=fr
Thanks
Run the installer with the following command:
1
SetupChipset.exe /extract <path>
Note: change <path> to the path you want to extract the INF files to, or use a period if you want to extract it to the current directory examples:
1
2
3
2
3
SetupChipset.exe /extract D:\Intel\Chipset
or
SetupChipset.exe /extract .
new driver with same date problem
Guys, this complaining about the “wrong” date should stop. It is a feature. It is a good thing that the date is set that back. I’m personally against changing it and then re-signing with a 3rd party certificate. It only adds a lot of extra steps to follow for something which is not important in 99% of cases. In fact, updating the date will probably cause issues for people who still don’t understand what the Chipset INF files do. The safest thing to do is to add a note or something and explain that the dates appear wrong for x,y reason and that is totally normal and should be ignored.
Update of the Start post
Changelog:
- new: "Intel Chipset Device Software Set v10.1.17541.8066 WHQL dated 01/10/2018 (original Set with installer)
-
new: “Latest Intel Chipset Device INF Files v10.1.x.xx Series WHQL” composed at 02/08/2018
(= AIO package with the “pure” original Intel Chipset Device INF files, extracted from the InstallerSet v10.1.17541.8066 WHQL, shown with the wrong date 07/18/1968)
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.16.3: CannonLake-H
- v10.1.15.2: CannonLake-LP
- v10.1.14.3: CoffeeLake
- v10.1.13.2: Geminilake
- v10.1.11.1: KabyLake-PCH-H
- v10.1.10.2: Kabylake
- v10.1.9.1: Lewisburg
- v10.1.8.3: Skylake-E
- v10.1.7.1: Skylake
- v10.1.6.1: SunrisePoint-H
- v10.1.5.1: SunrisePoint-LP
- v0.0.0.1: NULL_HECI
- v10.1.3.1: all other supported Intel Chipsets/CPU systems
Thanks to Station-Drivers for the source package!
Any feedback is much appreciated.
Regards
Dieter (alias Fernando)
the problem is the installation with normal compressed package, if u extract the package can install this drivers, but not with the executable driver