Solved Qualcomm NCM865 BlueTooth broken after Jan 2026 update (on MSI AMD X870 Motherboard)

Running onboard Qualcomm NCM865 for Wifi and Bluetooth, and it was all working fine until the updates last Tuesday, rebooted, the bluetooth devices are still there in settings, but they won't connect - checked the device manager, and no Bluetooth showing, just an "Unrecognized USB device"

When I try to install the driver, the MSI tool for installing just says there's no compatible driver found.

I downloaded the newest driver from Qualcomm, from MSI, and even updated the 5GB LAN driver, found newer Wifi 7 drivers for the same device, and those are fine, but it just doesn't believe the device has a bluetooth component.

I'd roll back from a backup the day prior to that update, but bluetooth functionality isn't mission critical, more nice to have (I do have a bluetooth headset, but it has it own dongle, and that's still working)

It's an MSI X870 Gaming Plus Wifi motherboard, using that Qualcomm NCM865 chipset for Wifi 7 and Bluetooth 5.4 - and it's been working great until that last update (also installed the "emergency" update they released since, no change)

Wifi works great, no issues with ethernet, just want to get the Bluetooth back online - if anyone knows anything about this chipset having issues since the January update, could use some insight (I've searched, spent 3-4 hours researching and trying different driver versions, even found mentions that this is a problem, but no mentions of any kind of successful fix)

2 things if you want to try:

1. Full power-cycle reset of the motherboard

This is not a normal reboot — it forces the USB/PCIe controller to re-enumerate the NCM865.
Steps:
- Shut down Windows completely (not restart).
- Flip the PSU switch off.
- Unplug the power cable.
- Press the case power button 3–5 times to discharge the board.
- Wait 30–60 seconds.
- Plug back in and boot.


2. Check the Microsoft Catalogue, search for Qualcomm FastConnect 7800 Bluetooth (latest is at bottom, I believe)

antspants said:

2 things if you want to try:

1. Full power-cycle reset of the motherboard

This is not a normal reboot — it forces the USB/PCIe controller to re-enumerate the NCM865.
Steps:
- Shut down Windows completely (not restart).
- Flip the PSU switch off.
- Unplug the power cable.
- Press the case power button 3–5 times to discharge the board.
- Wait 30–60 seconds.
- Plug back in and boot.


2. Check the Microsoft Catalogue, search for Qualcomm FastConnect 7800 Bluetooth (latest is at bottom, I believe)

Microsoft Update Catalog

Click to expand...

The only thing on your list (part 1) I hadn't done was unplug the power supply and hit the power button a few times to discharge, I did shut down and switch it off, but this time I switched it off, unplugged it, and did the power button thing - powered on, and Bluetooth is back - oddly using the new driver I'd installed the INF file for last night.

Thank you!

pgallagher72 said:

The only thing on your list (part 1) I hadn't done was unplug the power supply and hit the power button a few times to discharge, I did shut down and switch it off, but this time I switched it off, unplugged it, and did the power button thing - powered on, and Bluetooth is back - oddly using the new driver I'd installed the INF file for last night.

Thank you!

Click to expand...

All good, glad you’re up and running.

Click the Green resolved button, top right of thread so people know it’s resolved

Me too - it wasn’t mission critical issue, mostly use Bluetooth to connect a spare set of headphones if my mains run low on battery, but it irks me when something isn’t working. Appreciate your assistance!

antspants said:

All good, glad you’re up and running.

Click to expand...

I wanted to thank you and in case someone in a future search has a similar problem so they can fix it. I have the same hardware as the OP.

For the most part I could usually connect, but the sound on my Soundcore Liberty Pro bluetooth earbuds would cut in and out constantly and the Apple earbuds would not connect at all. At first I thought it was Windows 11 or the Qualcomm driver, but it did the same thing on Linux Mint.

The driver I used was 3.1.0.1262

I followed the same procedure you recommended and that fixed it.