All notable changes to Universal Intel Chipset Device Updater will be documented in this file.
The format is loosely based on Keep a Changelog.
v2026.08.0017 - 2026-08-01
- Fixed: FriendlyName keyword filter silently dropped legitimate Intel devices —
Get-IntelChipsetHWIDspre-filtered candidate devices by matching$device.FriendlyNameagainst a fixed keyword list (Chipset|LPC|PCI Express Root Port|PCI-to-PCI bridge|Motherboard Resources) before they were even checked against the HWID database. Any Intel System-class device whose FriendlyName didn't contain one of those words was silently excluded from detection — regardless of whether it was a real, live,Status -eq 'OK'device. Reported via a Station-Drivers user whose system had three live Skylake-family System Agent devices (1901– PCIe Controller (x16),1911– Gaussian Mixture Model,191F– Host Bridge/DRAM Registers) that were never detected or reported, while a third-party scanner (Driver Genius Free Edition) flagged all three as outdated. Live PnP enumeration confirmed all three devices were present withStatus: OK— the updater's own filter was excluding them, not a database or matching gap. See Issue #26.
- Detection:
Get-IntelChipsetHWIDsno longer pre-filters candidate devices by FriendlyName keyword matching. EveryVEN_8086System-class device withStatus -eq 'OK'is now collected unconditionally; the authoritative filter is the existing downstream lookup against the full INF/HWID database ($chipsetData.ContainsKey($hwId)). This removes an entire class of false negatives — the same keyword-filter gap also affected other device categories that don't use the recognized keywords in their FriendlyName across multiple platforms/generations (e.g.*SystemGMM.inf,*SystemThermal.inf,*SystemNorthpeak.inf,*SystemLPSS.inf,*DmaSecExtension.inffamilies), not only the originally reported Skylake devices. - Removed the now-obsolete
IsChipsetfield and the "fallback to first 5 non-chipset devices" branch inGet-IntelChipsetHWIDs, both made unnecessary by the fix above. - Performance:
Get-CurrentINFVersionpreviously re-enumerated every PnP device on the system (Get-PnpDevice | Where-Object {InstanceId -eq ...}) once per detected Intel device to resolve its installed driver version — an O(n²) cost that scales with the number of detected devices. It now accepts the PnpDevice object already held from the initial enumeration via a new-Deviceparameter, looking up properties directly without a full system re-scan. The previous-DeviceInstanceIdparameter is retained as a fallback for callers that only have an instance ID string. - Display:
Found compatible platform(s):list now wraps HWIDs at 12 per line (3-space indent) instead of a single unwrapped line — on systems with a large number of detected devices per platform (e.g. 47 HWIDs under one IvyTown platform), the old single-line format made console output unreadable. Platform name lines now use yellow instead of white for better scannability. - Merged the separate
Downloading latest INF information...andParsing INF information - it may take up to 30 seconds!messages into a single, more accurate status line, since the time estimate always covered the whole download+parse+match block rather than parsing alone. - Renamed
Found N Intel chipset device(s)→Found N Intel device(s)andNo Intel chipset devices found.→No Intel devices found., since this count is now taken before database matching and is no longer pre-filtered down to devices that merely look like chipset devices by name.
- On a triple-platform Intel X79 (IvyTown / Patsburg PCH / IvyTown CPU Root) test system, detected device count rose from 12 to 59 after this fix — confirming the FriendlyName filter gap was systemic across platforms and generations, not specific to the originally reported Skylake case.
- Impact scope: on systems where all detected platforms map to the same Intel installer package, this bug did not prevent installation —
SetupChipset.exe -OVERALLperforms its own independent hardware matching regardless of what the updater detected or reported, so previously-affected devices were likely still serviced correctly by the installer even though the updater's own report incorrectly showed them as absent. The bug's practical impact was primarily incorrect/incomplete reporting; on systems where a missed platform would have required a different installer package than the one otherwise selected, actual installation could have been affected. - No database format changes in this release.
v2026.07.0016 - 2026-07-12
- Fixed: Legitimate expired-certificate installers rejected — v2026.07.0015 introduced a certificate expiration check (
SignerCertificate.NotAfter -lt Get-Date) inVerify-FileSignaturethat rejected older Intel installers whose signing certificate has since expired, even when the Authenticode signature itself remains valid via RFC3161 timestamping.Get-AuthenticodeSignature's ownStatusfield already correctly accounts for timestamped signatures, making the extra check both redundant and harmful — it broke installation of older, still-authentic chipset installers that worked fine in v2026.05.0014.
- Removed manual
SignerCertificate.NotAfter -lt Get-Dateexpiration check fromVerify-FileSignature - Signature authenticity now validated solely via signer identity match (3 recognized Intel certificate patterns + FirstEver.tech exception), timestamp-aware
Get-AuthenticodeSignaturestatus, and algorithm check (SHA256 preferred, SHA1 accepted — warning only) - No other changes — EOL device handling, multi-signer support, credits/ads screen, and parser improvements from v2026.07.0015 are unchanged
- Recommended for everyone on v2026.07.0015 who saw
FAIL: Digital signature verification - Certificate expired.for installers that previously worked in v2026.05.0014 - No database changes in this release
v2026.07.0015 - 2026-07-01
-
EOL Device Support — Enhanced database parser now correctly detects End-of-Life (EOL) platforms from the new
#### Platform EOLsection headers. EOL packages are installed first (oldest versions), followed by the latest packages, preventing newer INF files from being overwritten by older ones. Legacy HWIDs that were removed from the latest packages are now properly handled. -
Multi-Signature Verification — Updated digital signature validation to recognize all Intel certificate variants used over the years:
Intel Corporation(latest)Intel(R) Software and Firmware Products(newer)Intel Corporation - Software and Firmware Products(oldest)
This ensures backward compatibility with older installer packages while maintaining strict security standards.
-
Configurable Credits Screen — The credits screen is now fully dynamic and loaded from external
intel-chipset-infs-credits.txtandintel-chipset-infs-ads.txtfiles. This allows easy customization of support links, career opportunities, and promotional content without modifying the core script. The screen supports interactive key shortcuts (1-5, A-E, L) that open configured URLs or exit the application. -
Improved Database Parsing — Fixed EOL detection logic to work with the new database format where EOL indicators are in section headers (
#### RaptorLake EOL) rather than in the Package column. Platform names are now normalized (e.g.,RaptorLakeinstead ofRaptorLake EOL) for cleaner display.
- EOL Detection: Dual-mode parsing supports both old format (
(EOL)in Package column) and new format (#### Platform EOLheaders) - Signature Validation: Enhanced with 3 Intel certificate patterns + expiration check + algorithm validation (SHA256/SHA1)
- Credits Screen: External configuration via
intel-chipset-infs-credits.txtandintel-chipset-infs-ads.txt - Parser Robustness: Fixed table separator detection (
---now works alongside:---) - Backward Compatibility: All changes maintain compatibility with existing database formats
- Added EOL sections for 16 platforms (RaptorLake, AlderLake, CoffeeLake, TigerLakePCH-H, etc.)
- EOL packages contain legacy HWIDs that were removed from the latest Intel Chipset Device Software packages
- Installation order: EOL (oldest) → Main (latest) ensures all detected HWIDs receive the correct driver
v2026.05.0014 - 2026-05-15
-
Intel Platform Scanner 7.1 – major database generation improvements:
- Fixed ArrowLake generation (
15th Gen Core/Core Ultra 200instead of14th Gen) - Added missing generic platform entries (
ArrowLake,RaptorLake,AlderLake,TigerLake,CometLake,IceLake,Lakefield,CoffeeLake,KabyLake,Skylake,Crystalwell) with correctOrdervalues - Reordered
PCH Family(oldest-to-newest) and fixed sorting forLynxPoint,PantherPoint,CougarPoint,Wellsburg,Patsburg,Lewisburg,Emmitsburg - Moved
MeteorLake PCH-N/H/SfromCLIENT - CoretoPCH Family - Moved six
*_Extension-Dmasecentries toPCH Familywith proper generation names - Moved
IceLakeXfromXEON / SERVERtoWORKSTATION / HEDT - Added asterisk
*to legend for platforms without dedicated INF (e.g.,Emerald Rapids,Ice Lake-SP,Cascade Lake-X) with explanatory footer note - Fixed duplicate
- Desktop/Mobilesuffix inGenerationfield - Added notes in MD footer about Wildcat Lake (shares HWIDs with Panther Lake), Panther Lake H/U (merged into single INF), and 16th generation (Lunar Lake classified under
ATOM / LOW POWER)
- Fixed ArrowLake generation (
-
Universal Intel Chipset Device Updater – Display Improvements:
- Grouped HWID display – platforms shown with HWID list instead of one line per device
- Compact platform information – each platform uses 3 lines (platform name, generation, installer version, status) – removed redundant
Generation:label to prevent line wrapping - Parsing hint –
Parsing INF information - it may take up to 30 seconds! - Simplified header banner – removed redundant separator and
Visit:row; author line now includes GitHub link - Better Windows Inbox handling – inbox platforms shown in compact grouped list, not mixed with regular updates
- Removed extra blank lines – no double empty lines before platform information section
- Scanner performance: better sorting and chronological order in all sections (Client, Workstation, Xeon, Atom, PCH Family)
- Updater UI: cleaner, more readable output in
[SCREEN 2/4]without information loss
- Updated
Intel-Platform-Scanner.ps1to v7.1 - Updated
universal-intel-chipset-device-updater.ps1to v2026.05.0014 - Updated
README.mdplatform support table up to 17th Gen - Updated
CHANGELOG.mdfor this release
- No changes to core detection/installation logic – the INF update process, Windows Inbox detection, and safety measures remain identical to previous versions
v2026.03.0013 - 2026-03-13
- Added multi-database support with
-betaand-developerflags for early testing of new Intel hardware platforms - Implemented automatic script update via PowerShell Gallery when new version is detected
- Improved console exit behavior: screen clears after credits, showing clean thank you message before returning to prompt
- Removed unnecessary 5-second wait at the end of
-auto/-quietruns for faster execution
- Added warning banner when running in non-default database modes
- Updated update detection logic to leverage native PowerShell Gallery commands
- Console output refinements for better user experience in different launch modes
- Internal cleanup of auto-mode exit routine
v2026.03.0012 - 2026-03-12
- Improved internal version handling and update detection logic
- Minor refinements in console output formatting
- General stability improvements
- Internal script cleanup
- Minor workflow optimizations
v2026.03.0011 - 2026-03-11
- Improved platform detection reliability
- Refined progress and status messages
- Code refactoring for maintainability
- Minor performance improvements in detection routines
v2026.03.0010 - 2026-03-10
- Improved INF database processing reliability
- Better handling of edge cases during chipset platform detection
- Script logic refinements for chipset platform mapping
- Minor logging improvements
v2026.02.0009 - 2026-02-17
- Database Scanner Fix – 300 Series (Cannon Lake PCH)
- Fixed missing Cannon Lake-H / Cannon Lake-LP chipsets in generated INF database
- Improved console output alignment
- Refined chipset platform status messages
- Intel Platform Scanner improvements
- Added missing platforms for Xeon E5 v1 – Jaketown
- Corrected key casing in internal platform definitions
- No changes to Intel INF packages
- Update focuses on database generation and detection logic
v2026.02.0008 - 2026-02-10
- Improved chipset detection reliability
- Minor refinements in update workflow
- Script cleanup and internal optimizations
v10.1-2026.02.2 - 2026-02-05
- Improved chipset detection stability
- Minor logging improvements
- Internal script optimizations
v10.1-2026.02.1 - 2026-02-01
- Improved hardware detection reliability
- Minor stability improvements
- Detection logic refinements
v10.1-2025.11.8 - 2025-11-27
- Enhanced platform detection including support for Windows 11 24H2 inbox drivers
- Automatic detection for platforms using Windows inbox chipset drivers
- Clear informational messages for inbox drivers
- Smart exclusion of platforms with
Package = None - Improved driver date handling using
.catsignature timestamps
- Updated parsing logic for platform detection
- Enhanced debug logging
- Improved console output structure
- Fixed potential false positives for unsupported platforms
- Improved handling of platforms without separate chipset packages
v10.1-2025.11.7 - 2025-11-25
- Improved chipset detection workflow
- Minor stability improvements
v10.1-2025.11.6 - 2025-11-24
- Stability improvements to chipset detection workflow
- Improved INF package verification logic
- Minor code refactoring
v10.1-2025.11.5 - 2025-11-21
- Improved INF package download reliability
- Enhanced update detection logic
- Script optimizations
- Improved logging consistency
v10.1-2025.11.0 - 2025-11-14
- First public version of Universal Intel Chipset Device Updater
- Automatic Intel chipset hardware detection
- Secure download and installation of latest Intel chipset INF packages
- Multi-layer security verification
- Automatic system restore point creation
- SHA256 hash verification
- Intel digital signature validation
- Support for Intel consumer and server platforms
- Portable architecture (no installation required)
- Automatic update detection
- Detailed logging and debug mode