if by support you mean by "windows updates" i have disabled the drivers from being updated via windows updates. if you mean the OS, by default, its understandable and logical!
i see some size differences in the files (inside the "ALL" folder), thats why i ask and try to understand what is the latest one from those 2!
Believe me - there is no difference regarding their function and impact on your system.
I updated Win 8.1 to Win 10, and then installed Anniversary update.
Now I got a list of following updates in Windows Update Mini Tools and wushowhide.diagcab
Windows 10 Anniversary Update and later Servicing Drivers
Intel - Other hardware - Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Intel - Other hardware - Intel(R) 7 Series 216 Chipset Family PCI Express Root Port 1 - 1E10
Intel - Other hardware - Intel(R) 7 Series 216 Chipset Family PCI Express Root Port 5 - 1E18
Intel - Other hardware - Intel(R) 7 Series 216 Chipset Family SMBus Host Controller - 1E22
Intel - Other hardware - Intel(R) 7 Series 216 Chipset Family PCI Express Root Port 4 - 1E16
Intel - Other hardware - Intel(R) H77 Expree Chipset LPC Controller - 1E4A
Windows 10 and later drivers:
Intel - Other hardware - Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller - 0150
In addition to this list I got a following update from DUMO:
Intel(R) Watchdog Timer Driver (Intel(R) WDT) Intel 11.0.0.1007 Update available (11.0.0.1010)
Is it make sense to update above mentioned drivers?
@UriF :
Welcome at Win-RAID Forum!
Only the "Intel(R) Watchdog Timer Driver" is a real driver (that means, that it contains a *.sys file).
All other "drivers" are no real drivers, but just textmode files and belong to the "Intel Chipset Device Software".
You can update them, but should not expect any performance boost.
For details please read the start post of >this< thread.
Regards
Dieter (alias Fernando)
Thank you. I contacted MS and they recommended to update. I could not update Watchdog because (I guess) it done (DUMO gave me a lot of updates for 14986 from 14393) for April update.
The other updates have been installed successfully. MS guy recommended to install these updates because of stability (???) issues. He also recommended to create a restore point if I am afraid anything. No problems for now. Thank you any way.
There is a brandnew Intel Chipset Device Software Set v10.1.1.42 WHQL dated 01/20/2017 available.
All included INF files have been digitally signed by Microsoft at 01/18/2017 and are shown within the Windows Eplorer as being dated 01/20/2017.
The problem: Since Intel had entered by mistake the absolutely wrong date 01/01/1970 into the INF files, they are detected by the Windows Hardware Management and shown within the Device Manager with this wrong date.
Bad consequence: Older INF files will not been updated unless this procedure will be forced.
Since I am not sure, whether I should offer this brandnew, but wrongly dated Set within the start post of this thread and replace the INF files of my "All-In-One"-Set by the much newer (but much older dated) INF files, I attach the new Set and the "pure" extracted INF files v10.1.1.42 WHQL here:
Intel Chipset Device Software Set v10.1.1.42 WHQL.rar (3 MB)
Intel Chipset Device INF Files v10.1.1.42 WHQL for manual installation.rar (226 KB)
We are on Intel 10.1.1.38 ( 3-10-2016) , can not update with the manual inf-files to 10.1.1.42 ( Jan.2017) ! Used this; Intel Chipset Device INF Files v10.1.1.42 WHQL for manual installation.rar
Why not ??
@Pete12 :
As I have already written within my previous post, you have to force the installation of the much newer INF files, because the OS doesn’t know, that the date 01/01/1970, which has been written by Intel into all INF files, is absolutely wrong and misleading.
So if you want to get these wrongly dated INF files installed, you have to use the “Let me pick…” > “Have Disk” driver update option.
By the way: An update of the Intel Chipset Device INF files is not worth the effort.
Thanks for your clear explanation ! I thought you will chance these files to the right date !
Will stay on 10.1.1.38 for now , Intel will correct this failure in near future ,I guess…
I would be able to do it, but it is not my task to correct Intel’s mistakes. Furthermore my date correction would break the WHQL stamp.
By the way: The WHQL stamp for absolutely wrong dated drivers indicate the worth of Microsoft’s digital signature.
" The WHQL stamp for absolutely wrong dated drivers indicate the worth of Microsoft’s digital signature. " …exactly !
This driver is a big mistake from Intel , also from Microsoft WHQL .
This wrong driver-date appears in the Intel-installer also ?? If not , we could use the installer instead of the manual inf-files…
I don’t Think Intel put the date 01/01/1970 by mistake, it has been seen before and with an explanation.
Yes, the installer will install exactly the same INF files (with the same dates) as the ones, you will get manually installed.
The explanation may be acceptable for INF files, which are just meant as placeholders for the later installation of real drivers (like the HECI or RST ones), but for all the other INF files, which cannot be replaced by any real driver, it is not acceptable.
Ok Fernando , if I understand you well , then its better to skip this driver-update (?) and wait for next ( better) version !
Yes, if you generally want to get the latest INF files resp. drivers installed.
This is my personal opinion: As long as everything is running fine and you don’t see any yellow flagged device within the Device Manager, I do not recommend to install/update any Intel Chipset Device INF file.
Intel Chipset Device Software v10.1.2.84 WHQL
Date: 1/20/2017
It is the same date in the inf’s as 10.1.1.42, 01/01/1970, so it does seem like a choice made by Intel.
@Pacman :
Thanks for the info and for your comment.
This verifies my statement regarding the importance of the so-named "Intel Chipset Drivers" (they aren’t real drivers), which I have layed down within the start post of this thread a long time ago.
Summary: For 99% of the users it doesn’t make any sense to install/update any Intel Chipset Device Software resp. the included INF files.
Only exceptions:
1. The Device Manager shows an Intel device with a yellow flag.
2. Any Intel chipset device doesn’t run properly.
Yes, normally i just install the latest inf’s after a Clean install of windows and leave it at that.
For X99, the Device Manager shows an Intel device with a yellow flag
Possible to have .inf file ?
Thanks