Universal Intel Chipset Drivers Updater​

FirstEver пишет:

This is the first bug that has been found.
 

The first ever bug from FirstEver! 

Don’t laugh, I had to fix the Scanner app (the brain of this project),
and it took about 100 code correction attempts! - 1559 lines of code 

Additionally, the 3 largest AI models were brainstorming together on how to fix
the historical naming of platforms. This dataset organizes the historical naming of platforms,
with a focus on technical rather than marketing aspects. It is based on:

• Detects all 5333 INF files
• Pulls 2996 unique HWID
• Creates 102435 entries

The new intel-chipset-infs-latest.md database has been uploaded to GitHub and Updater is already using it.

 
 

I think you have to be now very strong  , but I still find the following inconsistencies:
Yes, I assume, that Decice-ID 9D21 and 9D31 are correctly detected, but it's not listed as detected, similar like your screenshot, it shows 12 Intel chipset devices detected, but lists only 8.
And only writing that 10.1.5.3 is current and latest version, but no information which device is on the current and latest version.
I think it would be less confusing if all detected, matching devices are listed.




But, Device-ID 5914 is still not detected (or not listed)


And a small suggestion, if you are doing a bugfix, maybe you can increase the version number, because when I downloaded the file again, it shows already as downloaded.

Cheers
Tom

Yes, I found it in my full database (100,000 entries).

It also appears in the database used by Updater:

 


Now I see that it wasn't about 9D21 but about 5914...


It is in my full database, but this HWID is missing in the intel-chipset-infs-latest.md file.

Bug Summary and Fix:
The Markdown generation logic contained several mapping issues that caused certain client platforms (e.g., "Kabylake", "Skylake", "IvyBridge") to be omitted entirely from the final output.
These platforms were not listed in the $clientCoreList override and therefore fell back to their original category (Mainstream Desktop/Mobile), which no longer exists in the strict‑architecture category set. As a result, they were filtered out and never rendered. Several platforms marked as "Unknown" in the Generation field also lacked proper architectural descriptions.

Fix implemented:

• Added all missing client‑core platform names (including lowercase variants) to $clientCoreList and applied name normalization before category lookup.
• Expanded $archNameOverride with comprehensive architectural names for every previously "Unknown" platform, based on official Intel µarch and segment definitions.
• Updated $pchFamilyList and $xeonServerList to include additional variants, ensuring correct categorization of PCH and server chipsets.

These changes ensure that all detected Intel platforms appear in the correct strict‑architecture section with consistent, readable names and complete HWID listings.

---

IvyTown CPU Root is back on my platform - but it's the same installer.



Summary (pure logic):
Despite everything, I still believe the INF for 5914 should be installed, since it is included in the same Intel installer as the other INF files (e.g., 9D21).
If my updater were primitive and capable of detecting only a single chipset device, it would simply trigger the latest Intel installer — and that installer
would then install all INF files it contains that match your hardware—Intel installer has no idea what my updater detected.

Cheers
Marcin