Universal Intel Wi-Fi and Bluetooth Drivers Updater

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...
 

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. 🙂

Update: 10/06/2026

v2026.06.0006 → Release Notes

 

🆕 Highlights

• New Hardware Support — Added full support for Intel Bluetooth PCI Enumerator devices (`PCI\VEN_8086&DEV_A876`, `4D76`, `E476`, `E376`), also known as Intel(R) Bluetooth(R) PCI Enumerator
• Unified Driver Management — The updater now detects both USB Bluetooth (via `VID_8087&PID_xxxx`) and PCI Bluetooth (via `VEN_8086&DEV_xxxx`) and fetches the appropriate CAB package
• Shared PCI CAB — All PCI devices share a single CAB file (`intel-bt-<version>_pci.cab`), greatly reducing download size and simplifying maintenance
• Updated Banner — New tool version, revised author line, removed redundant GitHub link, improved layout
• Code Cleanup — All comments are now in English, version bumped to `2026.06.0006`

🐛 Bug Fixes

• Missing PID `0043` — Intel AX211 USB Bluetooth (PID `0043`) was absent from the supported device list; affected users received no update offer despite the driver being present in the database
• False Legacy flag for PCI Bluetooth — PCI devices such as `DEV_A876/4D76/E476/E376` were incorrectly shown as `[LEGACY]` when the USB Bluetooth version was newer; PCI and USB now use independent version tracks
• Scanner dead code (v4.5) — PCI legacy fallback in `BT-Platform-Scanner` was unreachable; known PCI DEVs absent from the current leak file now correctly fall back to the last known version from the previous MD

🔧 Compatibility

• Fully backward compatible with older `intel-bt-driver-latest.md` that only contains USB devices
• Existing USB Bluetooth devices continue to work without any changes

Update: 11/06/2026

v2026.06.0007 → Release Notes

🆕 Highlights

I have aligned the self-update mechanism with the Universal Intel Chipset Device Updater:

- When the updater is installed from the PowerShell Gallery (Install-Script) it will now update itself in-place using Update-Script.
- If the user accepts the update, the existing PSGallery installation gets upgraded automatically - no manual download required.

Additionally, I fixed an issue with dual driver updates (Wi-Fi + Bluetooth):

- Previously, the Wi-Fi driver was installed first, which often disconnects the network for 1-3 seconds. The subsequent Bluetooth CAB download would then fail.
- In v2026.06.0007 the order is swapped: Bluetooth first (does not affect network), Wi-Fi second (may disconnect, but no further downloads are needed).

Both changes are fully backward compatible.

Regards,
Marcin