Zitat von Lex im Beitrag #450

---

So are you using Windows OS default drivers or something else?

---

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)

• 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

@pipes80:
You can install the Intel Chipset Device INF files manually from within the Device Manager (extraction of the SetupChipset.exe file is required) or automaticly by executing the SetupChipset.exe file. The disadvantage of the latter option is, that the user may get much more installed than he/she needs.

Update of the Start post
Changelog:

• new: "Latest Intel Chipset Device INF Files v10.1.x.xx Series WHQL comp 02/23/2018"
  (= AIO package with the newest "pure" original Intel Chipset Device INF files)
  Notes:
  • All included *.INF files (except the Denverton, Geminilake and Lewisburg ones) have been finalized by Intel on 11/11/2017 and were digitally signed by Microsoft on 12/27/2017. The INF files for Denverton, Geminilake and Lewisburg CPU systems have been finalized by Intel in August/September 2017, but are misleadingly dated 07/18/1968.
  • Supported are all currently available Intel Chipsets from 6-Series up and all 32/64bit Windows Operating Systems from XP up.
  • The source package v10.1.1.44 has been delivered by Windows Update and was published today by StationDrivers (big thanks to fdrsoft).
  • The NULL_HECI files have been removed by me (to avoid an installation by mistake)
  • Here are the version numbers and dates of the INF files for the specific Intel CPU systems:
    • v10.1.19.1 dated 07/18/1968: Denverton
    • v10.1.13.2 dated 07/18/1968: Geminilake
    • v10.1.9.1 dated 07/18/1968: Lewisburg
    • v10.1.1.44 dated 11/11/2017: all others

@tistou77:
If you don't mind the misleading dates, you can stick with the currently installed INF files.
I doubt, that the content of the INF files is different (except the date).