Universal Intel Wi-Fi and Bluetooth Drivers Updater

  • FirstEver
  • FirstEver's Avatar Topic Author
  • Offline
  • Big Poster
  • Big Poster
    Enregistré
  • Posts: 59
  • Thanks: 112

Re: Universal Intel Wi-Fi and Bluetooth Drivers Updater

2 days 7 hours ago - 2 days 7 hours ago
#
Thanks to @ atplsx  for the link...

I've taken automation to the extreme. All I need to do is copy the new link to the CAB file, and my script automatically adds support for new drivers in my Universal Intel Wi-Fi and BT Drivers Updater – in just a few seconds.

Additionally, it detects whether new hardware has been added to the new drivers or support for previous models has been removed by Intel. The updater remembers the hardware that has been removed and still offers to download the latest available driver.
 

The latest Intel Wi-Fi database: intel-wifi-driver-latest.md

Intel will likely release the official installer on its website in a few days...
 
Last edit: 2 days 7 hours ago by FirstEver.
The following user(s) said Thank You: duttyend

Please Log in or Create an account to join the conversation.

  • FirstEver
  • FirstEver's Avatar Topic Author
  • Offline
  • Big Poster
  • Big Poster
    Enregistré
  • Posts: 59
  • Thanks: 112

Re: Universal Intel Wi-Fi and Bluetooth Drivers Updater

4 hours 22 minutes ago - 4 hours 19 minutes ago
#
Update: Added new Intel Bluetooth Driver 24.50.0.4

In the latest driver release I discovered that Intel has introduced a new Bluetooth device ID: USB\VID_8087&PID_0043.

Exciting, right? A brand new Bluetooth chipset?
- Nope.
It's actually just another variant of USB\VID_8087&PID_0033 (AX211), using exactly the same driver package.

What's interesting is that this is the first time I've seen Intel assign two different Bluetooth PIDs to a single CAB package.
Unfortunately, this also happened to break the automation logic in my Universal Intel Wi-Fi and Bluetooth Drivers Updater, which assumed Intel would continue following the pattern they've used for years.

A few minutes later, the driver scanner had already been updated to recognize this new exception. To keep the updater itself unchanged, I ended up adding a second AX211 entry and mapping both 0033 and 0043 separately. So if anyone is wondering why there are now two AX211 Bluetooth devices in the database:  intel-bt-driver-latest.md
Ask Intel. 🙂

Last edit: 4 hours 19 minutes ago by FirstEver.

Please Log in or Create an account to join the conversation.

Time to create page: 0.079 seconds
Powered by Kunena Forum