@plutomaniac:
You are right - I will put the latest Intel Chipset Device Software Sets of the v10.1.1.xx and v10.1.2.xx series into the start post.
Thank you for your explanation, which sounds to be comprehensible regarding the INF files, which are just placeholders for real drivers (RST/Heci/USB), but I cannot understand why Intel has recently started to put these old dates into all INF files of the latest Intel Chipset Device Software Sets, although >90% of the Intel Chipset Devices neither need nor will ever use a real driver.

@all:
The AIO Set, which I am offering within the start post, contains the latest available Intel Chipset Device INF files with the correct date of their compilation, but the Set doesn't contain placeholders for the HECI and RST drivers.

Zitat von Fernando im Beitrag #316

---

[...] but I cannot understand why Intel has recently started to put these old dates into all INF files of the latest Intel Chipset Device Software Sets, although >90% of the Intel Chipset Devices neither need nor will ever use a real driver.

---

@ all:
Following the advice given by plutomaniac, I have decided to update the start post and to present the latest original Intel Chipset Device Software Sets and their included "pure" INF files, although they have been misleadingly dated 01/01/1970 by Intel.

Update of the Start post
Changelog:

• new: "Original Intel Chipset Device Software v10.1.1.42 WHQL" dated 01/18/2017 (Original Set with Installer, all included INF files INF Files compiled in January 2017, but misleadingly dated 01/01/1970)
• new: "Original Intel Chipset Device Software v10.1.2.85 WHQL" dated 02/14/2017 (Original Set with Installer, all included INF files compiled in February 2017, but misleadingly dated 01/01/1970)
• new: "Latest Intel Chipset Device INF Files v10.1.x.xx WHQL" composed at 04/09/2017 (= AIO package with the "pure" original Intel Chipset Device INF files v10.1.142 resp. v10.1.2.85, all compiled by Intel in 2017, but shown with the wrong date 01/01/1970)

@khanmein:
Within which package did you find the related INF file(s)?

Zitat von khanmein im Beitrag #319

---

how come the digital signer is not Windows?

---

Zitat von akm im Beitrag #322

---

The mirror download link for the latest chipset INF files v10.1.x.xx for manual installation is not updated for the download of 10.1.1.42 drivers. The drivers from that link are of v10.1.1.38. Please fix it.

---

Zitat

---

I wonder if the system needs some driver for proper functioning of SMBus Host Controller, and where to find it.

---

The SMBus Host Controller doesn't need any real driver. So you will not find any.

Zitat von Pete12 im Beitrag #324

---

This new 1703-version of Win10 ( latest) , did not take these newer drivers , I would like to know why not , Fernando.

---

Zitat

---

Previous version of Win10 is not a problem with drivers signed by you, what can we do............?

---

The only difference between previous Windows Operating Systems and the "Creators Update" of Win 10 is, that the user has to change the procedure regarding the import of the Certificate. When you do a right click onto the *.cmd file and choose the option "Run as Administrator", nothing happens.
Solution: You have to run the Command Prompt or the Windows PowerShell as Admin, to navigate into the Certificate folder and then to execude the *.cmd file.

@khanmein:
What is "pretty weird" in your eyes?
Pete12 wanted to get the latest Intel Chipset INF files installed and not old ones. The Intel Chipset Driver Update Utility v10.1.1.14 has been released by Intel at 02/04/2016.

@khanmein: The Intel Chipset Device Utility v10.1.1.14 wil only offer Intel Chipset Device INF files v10.1.1.14. If you want newer INF files, you have to take a newer Intel Chipset Device Software version.