Universal Intel Chipset Drivers Updater​

  • timse201
  • Portrait de timse201
  • Hors Ligne
  • Newbie
  • Newbie
    Enregistré
  • Messages : 2
  • Thanks: 1

Re: Universal Intel Chipset Drivers Updater​

il y a 2 heures 34 minutes
#
Right now, your tool scans HWIDs for Serial IO, Sensor Solution, GNA etc.

Found compatible device(s)
 - TigerLakePCH-H_Extension-Dmasec devices (HWID):
   4389, 43BE

 - TigerLakePCH-H devices (HWID):
   43A3, 43A4, 43E8, 43E9, 43EF, 43FC

 - TigerLake devices (HWID):
   9A01, 9A03, 9A07, 9A0D, 9A11, 9A2F, 9A31

 =============== Platform Information ===============

 Platform: TigerLakePCH-H_Extension-Dmasec / 500 Series - Tiger Lake PCH-H - DMA Security Ext. (IOMMU / BitLocker)
  Latest Intel Chipset INF Utility: 10.1.20658.8883 (12/09/2025*)
  Detected INF: 10.1.34.13 -> Latest INF: 10.1.34.13 -> Latest version

 Platform: TigerLakePCH-H / 500 Series - Tiger Lake PCH-H (Mobile High Performance)
  Latest Intel Chipset INF Utility: 10.1.20658.8883 (12/09/2025*)
  Detected INF: 10.1.34.13, 3.1.0.4477 -> Latest INF: 10.1.34.13 -> Update available

 Platform: TigerLakePCH-H [EOL] / 500 Series - Tiger Lake PCH-H (Mobile High Performance)
  Latest Intel Chipset INF Utility: 10.1.18698.8258 (06/01/2021*)
  Detected INF: 30.100.2413.49 -> Latest INF: 10.1.34.8 -> Inbox / newer detected

 Platform: TigerLake / 11th Gen Core - Tiger Lake - Mobile SoC / High Performance Mobile
  Latest Intel Chipset INF Utility: 10.1.20658.8883 (12/09/2025*)
  Detected INF: 10.0.26100.8972, 10.1.43.5, 3.5.0.1611, 8.7.10802.26924 -> Latest INF: 10.1.43.5 -> Update available

Connexion ou Créer un compte pour participer à la conversation.

  • FirstEver
  • Portrait de FirstEver Auteur du sujet
  • Absent
  • The Best Poster
  • The Best Poster
    Enregistré
  • Messages : 109
  • Thanks: 184

Re: Universal Intel Chipset Drivers Updater​

il y a 2 heures 19 minutes - il y a 2 heures 8 minutes
#
Right now, your tool scans HWIDs for Serial IO, Sensor Solution, GNA etc.

Found compatible device(s)
 - TigerLakePCH-H_Extension-Dmasec devices (HWID):
   4389, 43BE

 - TigerLakePCH-H devices (HWID):
   43A3, 43A4, 43E8, 43E9, 43EF, 43FC

 - TigerLake devices (HWID):
   9A01, 9A03, 9A07, 9A0D, 9A11, 9A2F, 9A31

 =============== Platform Information ===============

 Platform: TigerLakePCH-H_Extension-Dmasec / 500 Series - Tiger Lake PCH-H - DMA Security Ext. (IOMMU / BitLocker)
  Latest Intel Chipset INF Utility: 10.1.20658.8883 (12/09/2025*)
  Detected INF: 10.1.34.13 -> Latest INF: 10.1.34.13 -> Latest version

 Platform: TigerLakePCH-H / 500 Series - Tiger Lake PCH-H (Mobile High Performance)
  Latest Intel Chipset INF Utility: 10.1.20658.8883 (12/09/2025*)
  Detected INF: 10.1.34.13, 3.1.0.4477 -> Latest INF: 10.1.34.13 -> Update available

 Platform: TigerLakePCH-H [EOL] / 500 Series - Tiger Lake PCH-H (Mobile High Performance)
  Latest Intel Chipset INF Utility: 10.1.18698.8258 (06/01/2021*)
  Detected INF: 30.100.2413.49 -> Latest INF: 10.1.34.8 -> Inbox / newer detected

 Platform: TigerLake / 11th Gen Core - Tiger Lake - Mobile SoC / High Performance Mobile
  Latest Intel Chipset INF Utility: 10.1.20658.8883 (12/09/2025*)
  Detected INF: 10.0.26100.8972, 10.1.43.5, 3.5.0.1611, 8.7.10802.26924 -> Latest INF: 10.1.43.5 -> Update available
Thank you for this post – it's incredibly helpful and at the same time complicates things quite a bit.

It turns out that Intel doesn't just remove certain HWIDs from the chipset packages;
Later, some of them end up in a completely different installer – the Intel Serial IO Drivers . My head is starting to hurt from this.

For example:
  • Detected (EOL) TigerLakePCH-H devices (HWID): 43A3, 43A4, 43E8, 43E9, 43EF, 43FC
  • Two of them (43E8, 43E9) have been moved to the Intel Serial IO Drivers installer and already have new versions.

I think the best solution will be to give the user a choice when EOL (End-of-Life) INF files are detected:
  1. Install everything including EOL, then the rest
  2. Skip EOL and install all other INFs
Additionally, in silent mode, all EOL packages will be skipped by default.

What do you think about this approach?
Dernière édition: il y a 2 heures 8 minutes par FirstEver.

Connexion ou Créer un compte pour participer à la conversation.

Temps de génération de la page : 0.079 secondes
Propulsé par Kunena