Intel Chipset Device "Drivers" (= INF files)

The start post of this thread has been updated by me today (12/21/2024).

Changelog:
Updated: Installer of the Intel Chipset Device Software Set
Updated: *.INF files for Intel Systems with one of the following CPUs:

  • ArrowLake (now v10.1.57.5)
  • Emmitsburg (now v10.1.40.6)
  • LunarLake (now v10.1.48.18)
  • RaptorLake (now v10.1.49.10)
  • SaphireRapids (now v10.1.39.10)
1 Like

The start post of this thread has been updated by me today (02/24/2025).

Changelog:

  • New: Intel Chipset Device Software Set v10.1.20062.8627 dated 12/05/2024
    (thanks to S-D for the Set!)
  • Customized: My “Latest Intel Chipset Device INF files v10.1 Series WHQL” AIO Set for the manual installation dated 02/24/2025

Note:

  • The officially released Intel Chipset Device Software Set contains a new Installer and freshly digitally signed INF files, but no new or updated Intel Chipset Device INF file.

Just letting you know: there doesn’t seem to be a LynxPointSystem.inf file in the AiO package. Probably a mistake?

1 Like

@MorningGlory
Thanks for your contribution. I will check it once I am home (in June) and will let you know the result.

@MorningGlory
You were right: When I composed in February the “Latest Intel Chipset Device INF files v10.1 Series”, I forgot to add the old files for the Intel “LynxPoint” CPUs - my bad.
Meanwhile I have found and added them. You will find the previously missing files within the freshly uploaded and linked package named “Latest Intel Chipset Device INF files v10.1 Series WHQL comp 06-04-2025”.
Thanks again for your input!

The start post of this thread has been updated by me on 07/25/2025 and 07/27/2025.

Changelog:

  • New: Intel Chipset Device Software Set v10.1.20266.8668 dated 06/28/2025
  • Customized: My “Latest Intel Chipset Device INF files v10.1 Series WHQL” AIO Set for the manual installation dated 07/27/2025

Note:

  • The officially released Intel Chipset Device Software Set contains a new Installer and some freshly digitally signed INF files, but no new or updated Intel Chipset “drivers”.

Hello everyone.
I came here out of curiosity and found…
an error?
In my hardware or Windows. I honestly don’t know which is the cause, probably Windows.
When checking my drivers, I found a common one listed by Windows:
PCI-to-PCI Bridge
with the full hardware ID:
PCI\VEN_8086&DEV_1901&SUBSYS_86941043&REV_07
But there’s something strange here.
According to the hardware ID, that ID is for the Skylake series of chipsets.
My motherboard theoretically has a Coffee Lake chipset.
But I’ve also had to extract compatible CPUs from Canon Lake H, such as Intel(R) PCI Express Root Port #5, 6, 7, etc.
Continuing with the PCI to PCI bridge, this controller refers to:

Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core™ PCIe Controller (x16) - 1901

Which is odd because it’s for older processors, and I use an i5 8400 on my mobo.
My question, in addition to all this, is: if Windows gave that name to the .inf file,
wouldn’t it be controlling it correctly?
I searched the internet and the updated .inf files @Fernando provides to date and tried to find the equivalent based on my chipset.

In the chipset file, I find an “equivalent” that I haven’t installed yet for reasons that it might crash or whatever. It would be this:

PCI\VEN_8086&DEV_3E81Desc="Intel(R) PCIe Controller (x16) - 3E81

I honestly don’t know if this is normal or if Windows made a mistake or if my motherboard manufacturer made a mistake, which would be:
Asus Prime H310M-E.

On the other hand, hwinfo on the bus says this:
Original Device Name:
Intel Skylake/Kaby Lake/Coffee Lake - PCI Express x16 Controller [R0]

Should I install the Coffee Lake chipset INF file or not?
PCI\VEN_8086&DEV_3E81Desc="Intel(R) PCIe Controller (x16) - 3E81
???

@ema-prowler

As written within the initial post of this thread, the Intel Chipset Device INF files are not real drivers, but simple text files without any impact on the performance or stability of the OS. Their only sense is to give the OS the information about the manufacturer and the correct name of the related device. Nothing will happen, if you try to install a wrong (not matching) Intel Chipset Device INF file.

As long as the Device Manager of your Windows OS doesn’t show a yellow flagged device, everything is fine and nothing has to be done.

ok ty