Intel Chipset Device "Drivers" (= INF files)

Important Drivers Other Drivers
601

As long as the Device Manager doesn’t show any yellow flagged "missing driver" device, there is no benefit by installing any Intel Chipset Device Software. You will only get bloatware installed.

602

New Intel Chipset Driver ver. 10.1.18015.8142.

603

@maks :
Thanks for the info and the link. I was unable to download your linked package (registration required), but fortunately found the same Set >here< at Intel’s Download page.

@all:
Update of the Start post
Changelog:

  • New:
    • “Intel Chipset Device Software Set v10.1.18015.8142 WHQL” dated 05/29/2019 (original Set with installer)
      Note: Only the latest Intel CPU systems are supported by this Installer Set.
    • “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 05/30/2019
      (= AIO package with the latest “pure” original Intel Chipset Device INF files for all Intel systems from 6-Series up, extracted from the related original Installer Sets

Important note:
Both packages contain some freshly digitally signed, but no really updated Intel Chipset INF files.

Regards
Dieter (alias Fernando)

604

@all:
Update of the Start post
Changelog:

  • New:
    • “Intel Chipset Device Software Set v10.1.18019.8144 WHQL” dated 06/11/2019 (original Set with installer)
      Note: Only the latest Intel CPU systems are supported by this Installer Set.
    • “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 06/13/2019
      (= AIO package with the latest “pure” original Intel Chipset Device INF files for all Intel systems from 6-Series up, extracted from the related original Installer Sets

Important note:
The only really updated INF files are for CannonLake-H CPU systems (now v10.1.16.7).

Regards
Dieter (alias Fernando)

605

Hello to everyone!

I need pure inf-files for version “10.1.1.40” of Intel Chipset Device Software. I found the exe-file of this version on the Station-Drivers website, but couldn’t find any sort of “unpacked” inf-files on the Internet. I tried to extract files from the exe-file using some extractors, but it didn’t work.

I would appreciate any kind of help!

606

@Kirill :
Why are you searching for old Intel Chipset Device INF files? Which benefits do you expect?

By the way: You can extract the SetupChipset.exe file of all Intel Chipset Device Software versions by doing the following:
1. Move the downloaded SetupChipset.exe file into a certain folder (e.g. C:\Download).
2. Create a target folder, into which the *.inf and *.cat files should be extracted (e.g. C:\Intel_Chipset).
3. Right-click onto the "Start" button and choose the option "Run".
4. Click onto the button "Search" and navigate to the file named SetupChipset.exe you want to get extracted.
5. In my example the "Run" command would look like this:

1
 
C:\Download\SetupChipset.exe -extract C:\Intel_Chipset
 
After a few seconds you will find all extracted *.inf and *.cat files within the folder C:\Intel_Chipset or in any other target folder you had determined).
607

Thanks a lot, @Fernando !

I don’t expect any benefits at all. It’s just my obsession to make everything “the right” way.

All versions of this software from “10.1.1.42” and up write “18.07.1968” in the field with information about date of these “drivers”. So if I install any newer version and then try to refresh drivers with “automatic searching on the Internet” function of Windows, it will find and install version “10.1.1.38”.

So initially I was searching version “10.1.1.38”, but later I found that version “10.1.1.40” is the last one with let’s say correct date of drivers. And when I try to refresh drivers with “automatic searching on the Internet” function of Windows, it says that current version of drivers is an actual one.

Intel uses this date (“18.07.1968”) to prevent a situation of possible overwriting of drivers. And if I install newest version of this software and then tell Windows to find drivers for these devices, Windows will find and install older drivers. It doesn’t make sense, so I was wondering which version of these drivers suits best so that Windows wouldn’t find any “better drivers”.

And I know that these inf-files are not drivers at all. Just wanted to install “the right ones” inf-files.

608

@Kirill :
Thanks for your detailed answer.
As you have realized, the iNF file dates - given by Intel and shown within the Device Manager - may be absolutely wrong and misleading.
If you want to make sure, that you get the latest (and hopefully bug free) INF files for your specific Intel chipset, you should take the ones, which I am offering within the start post of this thread.

609

Hey, @Fernando !

I will try to explain my way of thinking. Warning: long-read.

First of all, I have an Asus motherboard Z-97K and Intel Core i7-4790K processor and I always use latest Windows 10 update. I prefer to make a clean installation of system, so I do it basically every 6 months or so. And I always install latest drivers for my devices (which are not many).

Maybe I’d be not even concern about these Intel “drivers” (aka “inf-files”) if Windows would “understand” one device in Device Manager (SMBus Host Controller), but it ain’t so.

After complex research I found 4 versions of this Intel Chipset Device Software: version “10.1.1.7” (on the Asus website for my motherboard), “10.1.1.42” and “10.1.17” (on the Intel website) and the one on this website (which seems to be the latest of the latest). And also I have a Windows update through Device Manager, which installs inf-files “10.1.1.38”.

Initially I was thinking that the Asus version is better, because Intel itself says that manufacturer version can be more suitable.

(From the Intel website:
About Intel® Drivers: The driver or software for your Intel® component might have been changed or replaced by the computer manufacturer. We recommend you work with your computer manufacturer before installing our driver so you don’t lose features or customizations.)

But this version doesn’t install inf-file for device “Intel(R) Xeon(R) processor E3-1200 v3 / 4th Gen Core processor DRAM Controller - 0C00”. All of the other versions installed this inf-file.

Then I decided to install version on this website. For me it seems strange, but if I install from exe-file, this version doesn’t install any of the inf-files, but installs driver (or maybe inf-file) for Intel Management Engine (version: 0.0.0.1, date: 04.01.2013). When I manually update inf-files (downloaded from this website too) through Device Manager, all of them are updating (including Intel Management Engine). Besides, this version named my Intel Management Engine (which is normally called “Intel(R) Management Engine Interface”, if I install drivers for this specific device) “Intel(R) 9 Series Chipset Family Mobile Management Engine Interface - 8CBA”. Why it think that it’s “mobile”, I don’t understand.

Anyway, after installing version from this website I tried to update these drivers through Device Manager, and Windows found and installed version “10.1.1.38”.

So I was thinking, that Intel is updating this software in sort of backward compatibility. They do inf-files for the newer systems and update inf-files for the older ones. But these “updating” inf-files can be less suitable for the particular system than their analogs from the older version of this software. But since these drivers are not drivers at all and their solely function is to provide information about specific Intel’s device to the Windows, Intel doesn’t care much. And at some moment they decided to set a “wrong” date for these inf-files, so the system can then update these drivers to a more suitable (and the older one) version. I think that it is the reason for including of a driver (or inf-file) for Intel Management Engine (with version “0.0.0.1”) in this software.

Situation like that is the one that I had. So I decided to find version “10.1.1.38”, because I prefer to install Windows without Internet connection, because Windows 10 tend to downloading any sort of useless software (“Candy Crash” etc.)

I found this version on the Station-Drivers, but also found a version “10.1.1.40” which seems to be the latest one without changing of date. Version “10.1.1.42” already change the date to “01.01.1970”.

So then I install version “10.1.1.40” and try to find drivers through Device Manager, Windows said that my drivers are the actual ones. And when I try to install any newer Intel Chipset Device Software (“10.1.1.42”, “10.1.17” and version on this website), version of drivers doesn’t change. All that is changing is the version of installed software in registry “HKEY_LOCAL_MACHINE\SOFTWARE\Intel\InfInst”.

It was very long and very hard way to find out which version is better. And maybe my logic is wrong, but since my inner perfectionist is calm, then everything is alright.

Sorry for a long-read. English is not my native language (as you already could see) and I use this chance to excercise.

610

as those XXX.inf files are basically useless, ideally you want the one with the smallest footprint (kB size). Unfortunately sometimes Microsoft update does try to replace them.
to deal with previous and existing drivers version I suggest to use "rapr" (google that) DriverStore explorer.

611

@Kirill :
Thanks for your detailed statement regarding the reasons why you spend so much time to make sure, that your freshly installed OS uses the “best” resp. “latest” Intel Chipset Device INF files.
If you want to estimate the up-to-dateness and the importance of these simple text files, you should keep in mind the following:

  1. Don’t trust the dates and the version numbers of the Intel Chipset Device INF files and the related Installer Set.
    Intel has not only released a lot of different versions of their “Intel(R) Chipset Device Utility” (former name) resp. “Intel(R) Chipset Device Software” (nowadays name), but changed the numeration and the dates of the files (and the versions of the related Installer Sets) very often.
  2. The importance of these INF files is not only overestimated by many users (due to the commonly used name “Intel Chipset Drivers”), they are absolutely useless regarding the function of the related Intel Chipset Devices. Even if all the related INF files are missing, the function, stabilty and performance of the Operating Systems is not affected at all.
    The only reason to install a missing INF file for a specific Intel Chipset Device is to get rid of the yellow flagged “Missing driver” message within the Device Manager.
  3. The installation of some specific INF files may even have bad consequences for the user’s system.
    Examples:
    • a) Some old Intel Chipset Device INF files (e.g. the “cougide.inf” or the “cougahci.inf”) do support Intel SATA IDE resp. Intel SATA AHCI Controllers, although such Controllers need and will work much better with a real IDE driver (from Microsoft) resp. a real AHCI driver (the generic one from Microsoft or the specific Intel MSM or RST one).
    • b) All Intel Chipset Device Software Sets contain a “NULL_HECISystem.inf” file, which may prevent, that the user installs the much better real Intel MEI driver.

612

@elisw , @Fernando , guys, thanks a lot for your answers!

I hope that I’m done with this theme (because I spent much more time on researching than it deserved).

Good luck to both of you and to all members of this forum!

613

Hi,


Right now for my msi h110m pro-d i use intel chipset 10.1.1.38 oem ones . My question is which drivers are the best for me when it comes to performance ( i saw fps difference between 10.1.1.38 and 10.1.1.45 ) those meltdown fixes lower performance. If i want lowest input lag which ones should i use oem or the one posted here ( please link me the best ones).

614

@podkaracz
The Intel chipset device INF files are no drivers, but just text files, which give the information to the OS, that the related device
a) has been manufactured by Intel and
b) doesn’t need any driver.
Consequence: Such text file cannot have any impact on the system’s performance.

615

@Fernando

Intel Chipset Device Software Version 10.1.18121.8164 WHQL

616

@all:
Update of the Start post
Changelog:

  • New:
    • “Intel Chipset Device Software Set v10.1.18121.8164 WHQL” dated 08/26/2019 (original Set with installer)
      Note: Only the latest Intel CPU chipsets from 100-Series up are supported by this Installer Set.
    • “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 09/02/2019
      (= AIO package with the latest “pure” original Intel Chipset Device INF files for all Intel systems from 6-Series up, extracted from the related original Installer Sets
      • Both packages contain for the first time INF files for IceLake (v10.1.20.3) and IceLakePCH-N (v10.1.22.3) CPU systems.
      No other INF files have been changed/updated.

Thanks to Pacman for the link to Intel’s source package.

Regards
Dieter (alias Fernando)

617

.

618

.

619

@babgozd :
Thank you very much for your find.
You are absolutely right: The latest Intel Chipset Software Sets do not contain anymore INF files for the following quite modern Intel CPU series:
ColetoCreek, CougarPoint, Crystalwell, Haswell, Haswell-E, IvyBridge, Ivytown and JakeTown.
That is why I have just added the related files to the recently offered latest AIO package for the manual installation of the “pure” INF files.
Thanks again!


@all:
Update of the Start post
Changelog:

  • Slightly customized:
    • “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me (now dated 09/05/2019)
      (= AIO package with the latest “pure” original Intel Chipset Device INF files for all Intel systems from 6-Series up, extracted from the related original Installer Sets
      • Added are now the latest available INF files for ColetoCreek, CougarPoint, Crystalwell, Haswell, Haswell-E, IvyBridge, Ivytown and JakeTown CPU series.

Thanks to babgozd for the info about the missing INF files.

Regards
Dieter (alias Fernando)

620

Hi @Fernando , I want your help to sign this modified INF file for my computer, I really thank you in advance.

By the way, I would send you a pm for this but already see that can’t be attached files there.