@Jodec :
I am sorry, but I am neither willing nor able to give your attached INF file a digital signature.
As you surely know, I generally do not sign any drivers, which have been modified by someone else, and not upon personal request.
Nevertheless I have tried to give the related INF files a digital signature, but got an error message. This indicates, that there is something faulty or missing within the INF file text.
Just to satisfy my curiosity: Where is the link to the original source INF file, who modified it and which was the purpose for the modification?
@Fernando :
The second file in this MS catalog webpage, the “INTEL - System - 1/2/2018 12:00:00 AM - 10.1.1.45 Windows 10 and later drivers” are the original chipset files from Intel that I’m trying to modify, only the ValleyView2System.inf chipset inf file:
http://www.catalog.update.microsoft.com/…8086%26DEV_1E22
This is for overcome a problem that I’m facing since long time ago.
My family have 2 old and cheap Acer laptops, and they have stability problems since I installed Win10 in them log time ago, really huge problems like USB-Keys and portable HDDs attached to USB ports that disconnect and re-detected intermittingly and the windows and many processes be choppy and lagging, almost unusable computers they was. The past year in one of many exhaustive searches that did I do on the web, I found your website and become to understand more on how drivers work in Win10, and come to conclusion that many of the problems of the laptops was caused by the Generic MS USB3.0 drivers and that they hit the entire system too, when I installed your modded Intel USB 3.0 drivers for installing in Win10 almost all of the problems gone, the only thing that still has issues are the Touchpads, they are choppy and from time to time disappear at all, or stop working and no move anymore.
Acer put in its laptops a dual connected touchpads that can be changed in the UEFI/BIOS to function through the “new” I2C port OR the old PS/2 port. Since long time ago I been using the I2C ports + GPIO to have a “working” Touchpad but since the last Win10 update, the 1903, the touchpads became more buggy so in a last effort to trying to stabilizing them and finally have perfectly working computers, I’m become experimenting with different driver versions and through the I2C and PS/2 ports and found that the Touchpads are more stable through the old PS/2 port + LPC controller WHEN the I2C and the GPIOs does not have drivers installed at all, because although I select the PS/2 port in the UEFI seems to still have some connectivity to the GPIO ports and they have been less stable.
So, I left the I2C, GPIOs and TXE (this last for less drivers kicking in and cause I think they don’t need it) without drivers, but I fear that my family, an update or whatever, Install one of them, so I was trying to give them NULL Drivers like the Intel chipset driver do with some devices like the I2C or the SMBus to assigns null drivers to them for yellow-bang removal but at the same time preventing any driver installation for them that was older. I don’t have a problem with the I2C since the original ValleyView2System.inf has a Null Driver for it already, but the GPIO and TXE don’t so I’m trying to do the same for them, give them null drivers, changing the SMBus and I2C devices IDs with the TXE and GPIO IDs, deleting all the others devices IDs and given the INF file a different name for not conflict with the current original drivers.
Never be my purpose to spread this modded drivers on the web or give them to anyone, it will be for my personal and only use. In fact, I was in first instance sending you a PM but I realized that there i can’t attach files and came here instead.
@Jodec :
thanks for your detailed reply.
I will do a deeper look into the files, when I have the required time (not before Wednesday).
Hello what kind of Drivers/version can i use for the Chipsets Series 6/7/8/9 ?? As you can see there is a huge gab beetween series 5 and 100 in the forum Thread. so i am confused. (I want to use the official installer)
I. Latest Intel Chipset Device Software Sets (with installer):
A. For very old Intel Chipsets (usable up to 5-Series):
>Intel Chipset Device Software Set v9.4.2.1020 WHQL
B. For modern Intel Chipsets (from 100-Series up):
>Intel Chipset Device Software v10.1.18121.8164 WHQL (original Set with installer)
@bobs
Use the ‘Latest “pure” Intel Chipset Device *.INF files for all Intel systems from 6-Series up (manual installation)’ AiO pack instead. Locate any yellow-banged Intel (VEN_8086) device (99.9% sure they’ll be in Other devices category), and update the devices. Make sure you choose “Browse my computer…” option. The path should direct to the root of the unpacked package, and make sure the “Include subfolders” option is checked.
New Intel Chipset Device Software Version 10.1.18228.8176 WHQL
https://www.station-drivers.com/index.ph…id=4237&lang=fr
@tistou77 :
Thanks for the info.
After having checked all included INF files and compared its content with the previously released Intel Chipset Device Software v10.1.18121.8164 WHQ I realized, that the “new” Set doesn’t contain any new or updated INF files.
The only tiny difference is, that the Geminilake files obviously have been touched by Intel (are now shown within the Windows Explorer as being dated 11/28/2019), but in reality nothing has been changed (not even the WHQL signature dated 04/29/2019).
I don’t think, that it would make sense to offer here anything as being “new” and to stimulate the owners of a PC/Mobile system with an Intel Chipset to install the “new” Set with an old content.
new driver in station-drivers say for many chipset, included Intel X99 but no there is file to update this platform
Have a mobile Intel(R) 7 Series/C216 Chipset and Win10 1909 installed. Which of your Chipset packages do I Need? I) A. says: up to 5 series; I) B. says: from 100 series. What About 7 series??
@pustekuchencake :
Since the 7-Series is newer/higher than the 5-Series, but older/lower than the 100-Series, the answer should be clear:
Take my All-In-One package.
New Intel Chipset Device Software Version 10.1.18243.8188 WHQL
https://www.station-drivers.com/index.ph…id=4274&lang=fr
@tistou77 :
Thanks for the info and the link!
@all:
Update of the Start post
Changelog:
-
New:
- “Intel Chipset Device Software Set v10.1.18243.8188 WHQL” dated 12/22/2019 (original Set with installer)
Note: Only the latest Intel CPU chipsets from 100-Series up are supported by this Installer Set. -
“Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 01/08/2020
(= AIO package with the latest “pure” original Intel Chipset Device INF files for all Intel systems from 6-Series up, extracted from the related original Installer Sets
Both packages contain for the first time INF files for the CometLakePCH-V CPU series and updated INF files for the CometLakePCH-LP and IceLakePCH-LP CPU series.
No other INF files have been added/updated. - “Intel Chipset Device Software Set v10.1.18243.8188 WHQL” dated 12/22/2019 (original Set with installer)
Thanks to Pacman resp. Station-Drivers for Intel’s source package.
Regards
Dieter (alias Fernando)
@Fernando You’re welcome
What is .inf for Cascade Lake-X ? The same as for Skylake-X ?
I don’t have Cascade Lake-X yet, I can’t check
@tistou77 :
You should better ask Intel than me.
AFAIK the production of the CascadeLake-X CPUs is delayed and the production of the Skylake-X CPUs has been stopped by Intel.
Update of the Start post
Changelog:
-
New:
-
“Intel Chipset Device Software Set v10.1.18263.8193 WHQL” dated 01/22/2020 (original Set with installer)
Note: Only the latest Intel CPU chipsets from 100-Series up are supported by this Installer Set. -
“Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 01/23/2020
(= AIO package with the latest “pure” original Intel Chipset Device INF files for all Intel systems from 6-Series up, extracted from the related original Installer Sets
Both packages contain for the first time INF files for the CometLake and for the CometLakePCH-H CPU series and updated INF files for the CometLakePCH-V CPU series.
No other INF files have been added/updated. -
“Intel Chipset Device Software Set v10.1.18263.8193 WHQL” dated 01/22/2020 (original Set with installer)
Thanks to Station-Drivers for Intel’s source package.
Regards
Dieter (alias Fernando)
What about latest WinXP Chipset + AHCI Drivers for Z77 for example?
thanks!
Is there any package avaliable with haswell drivers? i have to manually install them with the current package
@GokuSS4 :
Welcome to the Win-RAID Forum!
Since the Intel Chipset Device INF files are simple text files, they can be installed while running any Windows Operating System, no matter which one and which architecture (32/64bit) it has.
Working Intel AHCI drivers for Windows XP can be found within the start post of >this< thread.
@noel_fs :
Welcome to the Win-RAID Forum!
The newest Intel Chipset Device INF Files Installer Sets do not support older Intel Chipset systems. The latest official Installer Set, which supports systems with a Haswell CPU, is v10.1.18010.8141 dated 04/30/2019.
Why don’t you just take the latest AIO package dated 01/23/2020, which I am offering within the start post of this thread? What is your problem to get the INF files installed manually?
Regards
Dieter (alias Fernando)
Update of the Start post
Changelog:
-
New:
-
“Intel Chipset Device Software Set v10.1.18295.8201 WHQL” dated 04/12/2020 (original Set with installer)
Note: Only the latest Intel CPU chipsets from 100-Series up are supported by this Installer Set. -
“Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed by me at 04/23/2020
(= AIO package with the latest “pure” original Intel Chipset Device INF files for all Intel systems from 6-Series up, extracted from the related original Installer Sets
Both packages contain for the first time INF files for the LakeField CPU series and updated INF files for the CoffeeLake, CometLake, KabyLake and SunrisePoint-LP CPU series.
No other INF files have been added/updated. -
“Intel Chipset Device Software Set v10.1.18295.8201 WHQL” dated 04/12/2020 (original Set with installer)
Thanks to Station-Drivers for Intel’s source package.
Regards
Dieter (alias Fernando)