v2026.09.0019 - Release Notes

🩹 Bugfix Release: v2026.09.0019 — Foreign/Unrecognized Version Detection

🆕 What's New

Fixed False "Update Available" Status Caused by a Different Intel Package Sharing the Same HWID

Problem: On MeteorLake PCH-S, the platform's chipset INF (MeteorLakePCH-SSystem.inf, version 10.1.51.10) covers HWIDs 7F00–7F69, including 7F04, 7F23, 7F24, and 7F2F. On some OEM systems, 7F23 specifically is instead serviced by an entirely different, unrelated driver — the Intel(R) Innovation Platform Framework (IPF) SMBUS Device — needed by Intel Dynamic Tuning Technology for platform telemetry. Because the updater aggregated and compared all detected versions for the platform together, this unrelated IPF version (2.3.20304.x / 2.3.20306.x) caused the entire platform to be incorrectly flagged Update available, even when the actual chipset INF (10.1.51.10) was already current on the other three devices.

How it was found: Reported in Issue #34 — "Similar Issue to Issue #11: 270K Plus reported as MeteorLake" — with a full detection log showing:

Platform: MeteorLake PCH-S / 14th Gen Core/Core Ultra 100 - Meteor Lake - Desktop PCH
Detected INF: 10.1.51.10, 2.3.20304.7 -> Latest INF: 10.1.51.10 -> Update available

The reporter asked for a note so users wouldn't think detection was broken, rather than a fix that changes what gets installed.

Investigation:

1. Initial hypothesis: the extra version came from Intel's own, generically-downloadable Intel Platform Performance Package / Dynamic Tuning Technology (DTT) installer, which bundles the Innovation Platform Framework (IPF).

2. Disproven by direct inspection: the actual DTT 9.1.10010.2297 package was obtained and its four .inf files (kpe_apo_ext.inf, kpe_apo_win.inf, dtt_ext.inf, dtt_sw.inf) were checked for PCI hardware IDs. None declare 7F23, or any 7F0x HWID at all — the generic Intel download's PCI-bound HWIDs are AD03, B01D, 461D, 3258, A71D, 7D03, 641D; the other two INFs bind only to software-enumerated (non-PCI) device IDs.

3. Actual source identified: a manual search of the Microsoft Update Catalog for PCI\VEN_8086&DEV_7F23 found a match distributed via Windows Update:

   Field	Value
   HWID	PCI\VEN_8086&DEV_7F23
   Driver Model	Intel(R) Innovation Platform Framework SMBUS Device
   Driver Provider	Intel
   Distributed by	Compal Electronics, Inc. (OEM)
   Versions seen	2.3.20304.7 → 2.3.20306.4

   This is an OEM-pushed IPF driver package, independent of Intel's generic DTT/IPF download, targeting 7F23 specifically because IPF needs SMBus access on that PCH-S block for telemetry.

4. Scope confirmed: searching the Update Catalog for "Intel(R) Innovation Platform Framework SMBUS Device" across all four platform HWIDs showed matches only for 7F23 — never 7F04, 7F24, or 7F2F — confirming this is a stable, repeatable pattern tied to that specific device function, not incidental noise.

5. Timeline reconciled: the chipset database's 10.1.51.10 entry for MeteorLake PCH-S carries a .cat signature date of 12/09/2025; the IPF SMBUS driver first appears in the Update Catalog from around April 2026. The January 2026 Chipset Device Software release simply predates Intel's decision to split this HWID out — not a contradiction, just a difference in release cadence between two independent teams.

Fix:

• Every Intel Chipset Device Software INF version present in the database — including every EOL entry, back to the oldest dated 2015 — uses major version 10 (10.0.x / 10.1.x). The updater now compares each detected version's major component against the platform's own latest known chipset major version (not a hardcoded literal), rather than comparing all detected versions as if they were all chipset INF versions.
• A detected version with a lower major number is now recognized as belonging to different, unrelated Intel software and is excluded from the Update available / Latest version calculation for that platform.
• It is still surfaced to the user, on its own line:

  Detected INF: 10.1.51.10 -> Latest INF: 10.1.51.10 -> Latest version
  Detected INF (unrecognized): 2.3.20304.7
    Note: an extra driver version was found for one of this device group's
    components - it belongs to different Intel software already installed on
    your PC. Installing this update is safe: even if it temporarily switches
    that component back, Windows will automatically reinstall the newer one
    on its own shortly after.
  

• The full technical explanation (specific HWID, source package, Windows PnP driver-ranking behavior, and the Microsoft Update Catalog evidence above) is written via Write-DebugMessage and only shown when running with -debug, so the default output stays approachable for non-technical users.
• Important limitation acknowledged in the note's wording: the updater has no way to selectively skip installing the chipset package on just the affected HWID — it operates at the platform/INF-file level, and the platform's other HWIDs genuinely need the chipset INF. Installing the chipset package may, but is not guaranteed to, cause Windows' own PnP driver ranking to temporarily replace the IPF driver on the shared device; this is a Windows-level decision, not something this updater controls. If it happens, Windows Update has been observed to reinstall the correct driver shortly after.

🔧 Full Changelog

Core Updater (universal-intel-chipset-device-updater.ps1)

Bugfix:

• New per-currentVersion split into "real" (matches the platform's chipset major-version scheme) vs. "foreign" (lower major version, belongs to different software) before update-status calculation
• Foreign versions no longer contribute to Update available / Inbox / newer detected status determination
• New separate Detected INF (unrecognized): <version> output line with a plain-language, non-technical safety note
• New -debug-only detailed technical explanation for foreign version detections, including the confirmed HWID 7F23 / IPF SMBUS Device case

Versioning:

• Script version bumped to 2026.09.0019

📊 Real-World Validation

• Confirmed via direct .inf file inspection (Intel DTT 9.1.10010.2297 package) and Microsoft Update Catalog lookups against the specific HWIDs reported in Issue #34, not simulated or assumed. No dedicated hardware reproduction was performed; the fix is validated against the reporter's own detection log and the two independent data sources above.

📋 Release Files

• universal-intel-chipset-device-updater.ps1 — Main updater script (v2026.09.0019)
• ChipsetUpdater-2026.09.0019-Win10-Win11.exe — Self-extracting package (includes updated script)
• intel-chipset-infs-latest.md — Unchanged from v2026.08.0018
• intel-chipset-infs-download.txt — Unchanged from v2026.08.0018

🔒 Security Notes

• No changes to signature verification, download integrity checks, or installer execution logic.
• No new INF packages, HWID mappings, or download sources introduced. The only behavioral change is in how detected version numbers are interpreted for status display and update decisions.

📝 Notes

• Impact scope: affects any platform where one of its HWIDs is, on some systems, serviced by non-chipset Intel software with a differently-scheme version number. Confirmed today for MeteorLake PCH-S / HWID 7F23, but the fix is a general heuristic and will also apply to any other, not-yet-discovered platform hitting the same pattern.
• Recommended for everyone, particularly systems with Intel Dynamic Tuning Technology / Innovation Platform Framework installed (common on OEM laptops and some desktops with Intel Core Ultra processors).
• Backward Compatibility: fully compatible with existing databases and installer packages; no database changes in this release, and no new exit codes.
• Known limitation: the updater still cannot skip installing the chipset package on just the specific affected HWID — the underlying Intel installer operates at the platform/package level and does its own system-wide hardware matching. Whether the chipset package or the OEM-pushed IPF driver ultimately stays bound to a shared HWID is decided by Windows' own PnP driver ranking, not by this updater.

---

Full changelog →