Fixing a Windows 11 PC That Drops Bluetooth After a Driver Update

A driver update can leave Bluetooth in a restart loop or make the radio vanish from Settings and Device Manager entirely, and reinstalling the driver often does not help. This guide walks through the symptom, the safe diagnostic steps in the order that isolates the real cause, and what to try when each step fails.

Fixing a Windows 11 PC That Drops Bluetooth After a Driver Update
via YouTube

Bluetooth failures that begin right after a driver update are easy to misdiagnose because the obvious fix — reinstalling or updating the driver again — frequently does nothing. In a documented case on Microsoft's Q&A forum, a fleet of Windows 11 25H2 machines with Intel AX211 radios in Dell and HP hardware developed a Bluetooth restart loop: paired devices connected and disconnected repeatedly until Bluetooth disappeared from Quick Settings, Settings and Device Manager altogether. The report covers builds 26200.9168 and 26200.9278, and the author notes the fault returned after fixes that looked complete ¹.

That last detail matters. A Bluetooth problem that survives a driver reinstall and a normal restart is usually not a driver problem in the narrow sense. It is a device-enumeration problem, and the diagnostic path below is built around proving or disproving that before you touch anything.

First, pin down the symptom precisely, because the right fix depends on which of three states you are in. In state one, Bluetooth is on but accessories drop intermittently or a headset loses audio mid-call. In state two, Bluetooth has disappeared from Quick Settings and Settings but the adapter may still be listed under a hidden or problem category in Device Manager. In state three, the entire Bluetooth class is gone from Device Manager. The fleet report describes all three appearing in sequence on the same machines, with audio devices refusing to pair at all while mice and keyboards still paired but dropped out, including during sign-in. If your only symptom is periodic crackling and cutouts on earbuds after a few hours of use, that is a different, older pattern and the steps below are a reasonable starting point but not a guaranteed match.

Work through these in order.

1. Confirm whether the adapter is present at all. Open Device Manager and check for a Bluetooth category. If it is missing, switch to the View menu and enable Show hidden devices. Also check for an entry under Other devices or a device carrying a warning icon. This single check sorts your situation into one of the three states above and determines whether the later steps make sense.

2. Roll back the driver rather than updating it. In Device Manager, open the Bluetooth adapter's properties, go to the Driver tab, and use Roll Back Driver if the button is available. This is the standard first move recommended in Microsoft's community answers for Bluetooth trouble on Windows 11, alongside fetching the OEM driver from the laptop manufacturer's support page ². Rolling back targets the update that started the problem; updating again usually just reinstalls the same package.

3. If rollback is unavailable, install the manufacturer's driver directly. Download the Bluetooth and wireless driver package from your PC or motherboard maker's support site rather than relying on whatever Windows Update offers. Microsoft's answers thread on the 25H2 wireless-device problem specifically points to OEM drivers as the remedy when older drivers break after a major update ³. Install it, then do a full shutdown and power-on rather than a restart, so the adapter is re-enumerated from scratch.

4. Check for ghost devices before assuming the hardware is dead. This is the step most people skip, and in the documented fleet case it was the decisive finding. Using the Get-PnpDevice PowerShell command, affected machines showed more than 40 ghost Bluetooth devnodes and zero live nodes, while a healthy control machine showed no ghost nodes and roughly 28 live ones. A large ghost population with no live nodes means the Bluetooth class itself has collapsed, not that your headset is faulty. If you see that pattern, stop reinstalling drivers and move to step 5.

5. Reset the Bluetooth stack and the network configuration. Turn Bluetooth off and on in Settings as a quick check, then use the network reset option under Settings, Network & Internet, Advanced network settings, which Microsoft's community answer offers as a standard remedy after the 25H2 update disrupts wireless adapters. A network reset removes and reinstalls network adapters and returns networking components to their default settings, so note any custom configuration first.

6. Test with a clean external adapter. A cheap USB Bluetooth dongle tells you whether the problem lives in the onboard radio, its firmware or the Windows stack. If the dongle works reliably while the internal adapter stays missing, the fault is almost certainly in the internal hardware path or its driver binding, and the next stop is warranty service or a board-level repair rather than more software work.

When a step does not resolve the problem, the useful question is what the failure tells you. If rollback is greyed out and the OEM driver installs cleanly but Bluetooth vanishes again after the next restart, you are likely looking at the enumeration failure described in the fleet report, and the ghost-device check in step 4 is the evidence to gather before contacting support — it distinguishes a collapsed device class from a single bad accessory. If the adapter is present in Device Manager but accessories still drop, the problem is more likely pairing state or radio interference than the driver, and the ordered steps in our guide to Bluetooth headphones that keep disconnecting on Windows 11 are the better fit. If Bluetooth and Wi-Fi fail together after the update, treat it as a wireless-adapter problem and work the Windows 11 Wi-Fi drop after sleep sequence, since both radios often share a module and a driver package.

Two things remain genuinely unresolved in the public record. The fleet report does not identify a root cause or a confirmed permanent fix, only the ghost-devnode signature and the observation that the fault recurs after fixes that appeared complete. And the reports span different hardware and builds, so there is no single verified remedy that applies to every machine. What the sources do support is a decision rule: if a driver reinstall and a restart change nothing, stop treating it as a driver problem and start collecting device-enumeration evidence. That is the difference between a fix that holds and one that looks complete until the next reboot.

Sources

  1. ¹ Bluetooth stack fails to restart after driver-store cleanup — Windows 11 25H2 - Microsoft Q&A - Skip to main content learn.microsoft.com
  2. ² Why is Bluetooth still an issue with Windows 11? - Microsoft Q&A - Skip to main content learn.microsoft.com
  3. ³ How to fix windows update 25H2 that disabled my wireless devices. - Microsoft Q&A - Skip to main content learn.microsoft.com