Universal Intel Chipset Drivers Updater​

Release: v2026.08.0017

🆕 What's New

Detection Fix — FriendlyName Keyword Filter Silently Dropped Legitimate Devices

The device detection step (Get-IntelChipsetHWIDs) used to pre-filter every candidate Intel device by checking whether its FriendlyName contained one of a handful of keywords: "Chipset", "LPC", "PCI Express Root Port", "PCI-to-PCI bridge", "Motherboard Resources". Any live, fully functioning Intel System-class device whose FriendlyName didn't happen to contain one of those words was silently dropped — before it was ever even checked against the HWID database.

This surfaced through a user report (thanks again to rvail for the detailed logs): Driver Genius Free Edition flagged three Intel System devices as outdated on a Z270 desktop — 1901 (PCIe Controller x16), 191F (Host Bridge/DRAM Registers), and 1911 (Gaussian Mixture Model) — while my updater reported the system as fully up to date. A full, unfiltered PnP device dump confirmed all three were live and functioning (Status: OK) — the updater's own name-based filter was the reason they never showed up, nothing else.
  

• Filter removed entirely — every Intel (VEN_8086) System-class device with Status: OK is now passed straight to database matching, no keyword pre-check
• Same class of gap affected other device-name families across multiple generations, not just this one case: the GMM (Gaussian Mixture Model), Thermal, Northpeak, LPSS, and DmaSecExtension device families — none of these FriendlyNames contain the old keyword list
• Tested on a triple-platform X79 system (IvyTown / Patsburg PCH / IvyTown CPU Root): detected device count went from 12 → 59, all correctly matched to the same three known platforms

Why this matters: the keyword list was a rough heuristic from before I had a complete HWID database — a leftover from when the tool had to guess which devices looked chipset-related. Now that detection is matched purely by hardware ID against the full database, that guesswork isn't needed anymore, and neither is a filter that can silently exclude real hardware.

Performance Improvement

Version-checking (Get-CurrentINFVersion) previously re-scanned every PnP device on the system, from scratch, for every single detected Intel device — an O(n²) cost. On the X79 system above, going from 12 to 59 correctly-detected devices meant this re-scan ran roughly 5x more often, and detection time went from ~30s to over 2 minutes. Fixed by reusing the device object already collected during initial enumeration instead of searching for it again — detection is now O(n).

Display Improvements
   

• HWID lists now wrap at 12 per line instead of one unreadable wall of text (some platforms report 40+ HWIDs now that detection is complete)
• Platform names highlighted in yellow for easier scanning
• Download/parsing status merged into a single, more accurate progress message

Release Changelog: here
Full Changelog: here



P.S.
The next release will include a `-download` parameter for downloading detected Intel Chipset Device Software installers.
This will be useful for legacy chipsets, as newer versions of the installers are no longer being produced.
 

Thanks much for the updated (August 2026) utility. 
Note: the Driver Genius (free version) includes a useful function that continues working even after the initial 5 day "trial period" after first software installation.
It can detect and optionally clean out "Older driver packages" & "Invalid device data". 
So: you may want to run the Driver Genius utility after having run the "Universal Intel Chipset Drivers Updater​" & rebooting the PC.
Another free driver updater tool "Driver Fusion" detects certain device drivers that Driver Genius doesn't.
But: Driver Genius includes a unique obsolete driver cleanup function, as described above.

 

An error was discovered running your Intel Chipset Driver updater utility.
This appeared when running on the Z270 chipset motherboard, where it appears to be looking for a 64-bit installer, but your program is only finding a 32-bit version (?)
See attached screen shots: 


 

Are you using a 32-bit system???

Windows 11 is now only available in 64-bit version, so I decided that the updater will only use the 64-bit Intel Chipset Device Software installer. Theoretically, I might start using only the 32-bit installer to ensure full compatibility for all systems.

In this case, the error is not related to the updater, but rather the version of the Intel MSI installer (64-bit only) I used. Earlier Intel EXE installers seemed to only be available in 32-bit versions.