Intel® Wireless Bluetooth Drivers v24.xxx

Intel's dual‑INF packaging explained – my updater now shows the real driver version per device

Hi everyone,

Some of you may have noticed that my Universal Intel WiFi/BT Updater would sometimes report a version like 24.50.0.4 for your Bluetooth adapter, but after installation Windows showed a different version (e.g. 24.40.10.3 for AX201). This wasn't a bug in the updater itself – it was caused by the way Intel packages their Bluetooth drivers.

 

What Intel does:

Since around early 2025, Intel started bundling multiple Bluetooth controller families into a single CAB file, but with only one version number on the file name. Inside that CAB there are several INF files, each with its own DriverVer. For example, the CAB labelled 24.50.0.4 contains:

• One INF for newer controllers (FMP, GAP, MTP) with version 24.50.0.4
• Another INF for older controllers (GFP, HRP, JFP, TH – including AX201/AX200/AX210 etc.) with version 24.40.10.3

When Windows installs the CAB, it automatically picks the correct INF for your specific hardware and reports that INF's version. The updater, however, only saw the CAB filename and would keep offering the same CAB over and over – causing confusion and unnecessary "updates".

The fix:

I have completely rewritten the scanner that generates the intel-bt-driver-latest.md database (the updater script itself is unchanged). The new scanner (version 4.6) does this:

1. Downloads each USB CAB
2. Extracts the ibtusb.inf file using expand.exe
3. Parses the INF to find which DriverVer actually matches each PID (e.g. PID_0026 for AX201)
4. Creates per-PID entries in the MD file with the real installed version – not the CAB label

The result: the database now shows the correct version for every device. When you run the updater again, it will fetch the updated MD file and will only offer a true update if a newer real driver exists for your specific adapter.

Example: For AX201 (PID 0026), the updater will now show 24.40.10.3 instead of 24.50.0.4. No more false upgrade prompts.

Thanks to everyone who reported the confusion – this should finally clear it up.

Best regards,
Marcin