@ all: Since there are brandnew (but wrongly dated) Intel Chipset Device INF files v10.1.1.44 available since a few days, I decided to update my AIO package with the latest Intel Chipset Device INF files, but with corrected dates.
Update of the Start post Changelog:
updated: “Latest pure Intel Chipset Device INF Files v10.1.x.xx mod+signed by Fernando” with corrected dates (04/19/2017 for the included INF files v10.1.1.44 and 02/01/2017 for the v10.1.2.85 ones), the v10.1.1.44 INF files were modified and digitally signed by me today (05/27/2017).
This is what I got with my MS Surface Pro 3 (Intel 8-Series Chipset Mobile system) after having updated the related INF files: [[File:mod+signed INF file v10.1.1.44 - Pic1.png|none|auto]][[File:mod+signed INF file v10.1.1.44 - Pic2.png|none|auto]]
Any feedback is much appreciated. If you should find any Intel chipset device, which is not supported by my updated “All-in-One package”, please let me know it.
Corresponding Intel team said the following: “Intel(R) Chipset Device Software uses an unusual date for the devices it is targeting. The date 07/18/1968 is symbolic – Intel was founded that day. The reason this date is used is to lower the rank of Intel(R) Chipset Device Software. This is necessary because it’s a supporting utility that should not overwrite any other drivers. Updating Intel(R) Chipset Device Software is not needed."
If you want install the new 10.1.1.44 version of Intel chipset drivers, please try to run "SetupChipset.exe -overall", you can create shortcut for SetupChipset.exe and in target field add -overall key. Good luck!
@peagle : Welcome at Win-RAID Forum and thanks for your contribution!
In my eyes the insertion of these absolutely wrong dates into the INF files is not only misleadsing, but additionally useless. Such precaution action would have been necessary with older Intel Chipset Device Utility packages, which additionally contained INF files for the "Rapid Storage Technology" and "HECI", but doesn’t make sense for the latest Intel Chipset Device Software Sets, which do not contain such INF files anymore.
Regarding this statement I totally agree with Intel. There is no reason for users of a modern Windows Operating System to take care about the Intel Chipset Device INF files (unless the related device is so new, that the currently running OS doesn’t yet have a matching INF file "on board"). The OS natively supports nearly all Intel Chipset Devices.
I do not recommend to follow this tip. Reason: Please read the start post of this thread.
I have the ASUS HERO IX z170 motherboard and the latest windows 10. I am planing on a major reinstallation to Clean up my system and i am a bit fed with all missleading info on the web and also the Status of ASUS driver page. The Intel INF installation software on ASUS is not the latest version, The latest live version on Intel is older then the latest release of Windows.
Should i Bother installing the Intel INF installation software or is it already a part of the latest windows 10?
@Jerok : plutomaniac is right - it doesn’t make sense to install any Intel Chipset Device Software Set or any of its INF files, unless the related device is shown in the Device Manager with a yellow flag (“unknown device“ or “missing driver“). The Win10 v1703 Setup will detect all currently known Intel Chipset Devices and use the matching INF files (at latest after having run Windows Update for the first time).
Don’t care about the date, which is written into the Intel Chipset Device INF files and shown within the Device Manager. It may be right or wrong, but it is irrelevant anyway.
Awsome stuff. Another small thing. If you start manually updating the system drivers using device manager - update drivers - automatic there is a bunch of new drivers online that does not come with normal windows update. But when doing this method windows finds newer drivers for nearly ALL Intel system hardware and Chipset.
The drivers of which listed "System devices" did you try to update this way and for which specific devices (I need the names of them) did WU offer an update?
What means "newer"? Did you check the version and the real date of them?
You should better ask Microsoft or/and Intel. According to my knowledge everything is fine regarding all Intel Chipset Devices, which do not need a real driver (=*.sys file), if none of them has a yellow flag within the Device Manage - no matter how many of them are listed and which name and date they got. Note: The Intel devices "Intel(R) Management Engine Interface" and "Intel(R) SATA AHCI/RAID Controller" need a real driver and are not supported by any Intel Chipset Device Software resp. its included INF files.
Since My system is in a mess i did the stupid thing and just updated them. Could you check driver version and date you have on one or two and i Will compare when i get Home tonight. This could be some valid info IF they hide newer drivers this way.
I don’t see any red marked device on your screenshot, but I am pretty sure, that there is nothing to worry about. By the way: A lot of devices named "Intel(R) 200 Series Chipset Family LPC Controller - A2xx" are mentioned within the Intel Chipset Device INF file named "KabyLakePCH-HSystem.inf", which is within the latest Intel Chipset Device Software Sets v10.1.1.xx (I cannot read the last 2 numbers of the DeviceID, which is shown on your screenshot), but AFAIK the on-board Intel LPC Controller needs a real driver (= *.sys file), which is delivered by Microsoft and part of Win10 v1703.
The info was miss leading There is a small red DOTT on the left side of many divices on the image. I Will gett back to night With some driver info and dates
Yes they where to show the area of drivers that found New driver versions when Using the auto update funktion in the device manager. Not all of them but 3 to five drivers had newer versions according to the auto update.
What driver version do you currently hold on the pci Express root ports ?
Even the Xeon e3 1200 host bridge and pcie drivers had an update (wanna give me your driver version and date here as well if possible)
It might not be viable but it is weird to me
This is just to se what’s going on since I already done these updates and I thought it was worth to share.
Hello, I have installed the chipset 10.1.2.85 and I installed the new chipset 10.1.2.86 but it is not installed, in device management it is still installed 10.1.2.85, as I do to install 10.1.2.86.
I doubt, 1. that there really have been detected new devices and 2. that the listed devices have gotten an updated driver. Reason: The Intel Chipset Device Software doesn’t contain any driver, but just text files, which give the related devices a new name with the word "Intel" in it.
Here is a screenshot of my Z170 Device Manager after having done a fresh install of Win10 v1703 (all required drivers have been installed automaticly):
The brandnew Intel Chipset Device INF files of the v10.1.2.86 Set were not installed, because they are dated 07/18/1968, whereas the Intel Chipset Device INF files of the v10.1.2.85 seem to be "newer", because they are dated 01/01/1970. Why did you try to update the Intel Chipset Device Software Set at all? That is wasted time!
