Intel Chipset Device "Drivers" (= INF files)

Important Drivers Other Drivers
581

This is not true for all users of an Intel chipset system.

Do you really believe, that you resp.your system benefits from a forced update of all previously installed Intel chipset device INF files?
The only effect is, that you will get a lot of garbage installed this way. If you don’t believe me, look into your C:\Windows\INF directory for unused oemxxx.inf files.

582

Hello.

I think it will be not bad to mark that:

is for Windows 10 / Server 2016/19 only and not for Windows 7 (it’s in readme.txt + try to install it on Win7 system :wink: ).

Btw, what last version Intel Chipset Device Software Set For newer Intel Chipsets will be for Windows 7? 10.1.2.86 and 10.1.17833.8098?

583

@r1vver :
Since the Intel Chipset Device INF files are no real drivers, but simple text files, they are suitable for all Windows Operating Systems.

584

And another question: for Intel C600/C600+ systems having an Intel CPU Socket 2011 resp. 2011-3 (X79 and X99) - Intel Chipset Device INF files need to be 10.1.2.XX or 10.1.17xxx branch nowdays (Win7 OS)?

585

@r1vver :
Since Intel gave up already a long time ago its plan to devide the Intel Chipset Device Utility Sets into 2 different platforms (v10.1.1 for Consumer CPU systems and v10.1.2 for Corporate/Enterprise CPU systems), you can use them both.

586

ntel Chipset Device Software Version 10.1.17968.8131 WHQL new!!!

587

@panosxidis :
Thanks for the hint, but I already found it at Station-Drivers.

@all:
Update of the Start post
Changelog:

  • New:
    • “Intel Chipset Device Software Set v10.1.17968.8131 WHQL” dated 03/25/2019 (original Set with installer)

      • Thanks to Station-Drivers for the source package!

Important note:
This “new” Set doesn’t contain any updated INF file. Only the Installer itself seems to be new.

Regards
Dieter (alias Fernando)

588

v10.1.17968.8131 override the Intel MEI Driver

589

@Danhot :
Welcome to the Win-RAID Forum and thanks for your feedback!
Question: Did you just run the SetupChipset.exe or with the " -overall" command?

This verifies, that it is not always a good idea to run the installer of the Intel Chipset Device Software.
By the way - you can easily restore/reinstall the previously running Intel MEI driver from within the Device Manager.
Regards
Dieter (alias Fernando)

590

New Intel Chipset Device Software Version 10.1.17969.8134 WHQL

https://www.station-drivers.com/index.ph…id=3966&lang=fr

New version Skylake-E : 10.1.8.6

591

Update of the Start post
Changelog:

  • New:
    • “Intel Chipset Device Software Set v10.1.17969.8134 WHQL” dated 04/03/2019 (original Set with installer)
      Thanks to Station-Drivers for the source package and to tistou77 for the hint!
    • “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 04/05/2019
      (= AIO package with the latest “pure” original Intel Chipset Device INF files, extracted from the related original Installer Set, nearly all files digitally signed by Microsoft at 10/04/2018 (except the ones for CoffeeLake, KabyLake and SkyLak-E CPU systems), but all shown as being dated 07/18/1968)

Important note:
The only really updated INF file within both packages is the one for SkyLake-E (now v10.1.8.6) systems.

Regards
Dieter (alias Fernando)

592

Intel INF new v10.1.1.45 (18th April 2019) released, but while I tried to install it on the top of 10.1.17969.8134 it’s showing me a downgrading message.

593

@SM03 :
Please open the “new” INF file, which you think is dated 18th April 2019, and look for the written date you will find inside the file.
By the way: Which is the name of the INF file and which Intel CPU Generation has your system?

594

Intel Chipset Device Software 10.1.18010.8141 WHQL

595

Update of the Start post
Changelog:

  • New:
    • “Intel Chipset Device Software Set v10.1.18010.8141 WHQL” dated 04/30/2019 (original Set with installer)
      Thanks to Station-Drivers for the source package and to panosxidis for the hint!
    • “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 05/06/2019
      (= AIO package with the latest “pure” original Intel Chipset Device INF files, extracted from the related original Installer Set, nearly all files digitally signed by Microsoft at 10/04/2018 (except the ones for CoffeeLake, CometLake, IceLake, KabyLake and SkyLake-E CPU systems), but all shown as being dated 07/18/1968)

Important note:
The only new INF file within both packages are the ones for the upcoming CometLake and IceLake CPU systems.

Regards
Dieter (alias Fernando)

596

Hello @Fernando
I recently read your retirement post & it’s sad to see you go, but I understand your concern & need. Good luck & all the best for the rest of your retirement life.

BTW, about my earlier post about INF v10.1.1.45, it seems Intel re-released that v10.1.1.45 once again with some corrected date & adding some new INF file for newer systems, currently, I’m using the latest v10.1.18010.8141 for all of my systems consisting from Intel 2nd Gen to 7th Gen CPU including i3+i5 & i7 variants, so it’s a mixed bag for me & I get different version number along with the same date i.e. 18-07-1968, for example, for my old 2nd Gen i5, it is 10.1.3.1

597

@SM03 :
Thanks for your contribution.

Since I cannot find such new Intel Chipset INF Files Set v10.1.1.45, please post the link or attach the related package.

598

I just update chipset drivers using nòrmal setup method but all went fine but checking in device manager
the driver details still shows MS inbox driver? but on the main page it shows fine as driver provider INTEL, date, and driver ver?

can someone explain

599

Microsoft doesn’t manufacture any specific "driver" for the Intel Chipset Devices. The only MS INF files, which may be additionally used, are the generic ones (like pci.inf, machine.inf, mshdc.inf etc.).

600

so any benefit if update latest chipset driver package from manufactrer of mobo. or MS generic are sufficient?