Bluetooth Not Working on Windows 11? How to Fix

Your Bluetooth just quit. Maybe it happened after an update, maybe it happened at random while you were in the middle of a Zoom call with wireless earbuds. Either way, you’ve got a headset that won’t pair, a mouse that won’t reconnect, or an entire Bluetooth menu that straight up vanished from your Settings app.

I deal with this three or four times a week on remote sessions at RebootDoctor. The vast majority turn out to be driver conflicts that Windows Update created without telling you, or a power management setting that Windows flipped on behind your back, or WiFi and Bluetooth literally fighting each other on the same Intel chip. Actual dead hardware accounts for a tiny fraction — maybe one in twelve tickets. So the odds are strong that your Bluetooth adapter isn’t broken, Windows just lost track of it.

Is It a Hardware Problem or a Software Problem?

Takes 90 seconds to figure this out, and it’ll save you from wasting an hour on the wrong fixes.

Open Device Manager (Win+X, pick it from the list). Expand “Bluetooth” in the tree.

Bluetooth Diagnostic

Open Device Manager → expand "Bluetooth"

▼

Do you see a Bluetooth adapter listed?

YES — no yellow icon

Hardware is fine.

Software problem — try:

Driver update / rollback

Restart BT services

Power management fix

YES — yellow ⚠ triangle

Check Device Status code:

Code 10 → driver issue

Code 43 → driver or HW

Code 52 → signature issue

→ Reinstall / roll back driver

NO — category missing

View → Show hidden devices

Grayed out? Driver wiped

Still nothing?

Check BIOS settings

or USB header cable

If your Bluetooth adapter shows up with no yellow warnings — hardware is fine. The problem is on the software side, so everything below applies to you. If there’s a yellow triangle, double-click the adapter and read the Device Status box. Code 10 means the device can’t start, which is almost always a driver issue and not a dead chip. Code 43 is trickier — Windows stopped the device because it “reported problems,” and that could be driver corruption or genuine hardware failure. Code 52 means a driver signature issue, which happens after certain Windows Updates overwrite a working driver with one that isn’t properly signed for your adapter.

If the whole “Bluetooth” category is straight up missing from Device Manager, click View and check “Show hidden devices.” Grayed-out adapter means the driver got wiped or corrupted — reinstalling it usually brings everything back. If the adapter doesn’t appear at all even with hidden devices showing, either Bluetooth is disabled in your BIOS (more common than you’d think, especially on desktops after a BIOS update reset defaults) or the adapter itself is dead.

Here’s one that catches people on desktop builds. If you have a PCIe WiFi/Bluetooth combo card like the Intel AX210 — check the USB header cable. I know, sounds weird. But these cards route WiFi through the PCIe slot and Bluetooth through an internal USB 2.0 header cable that plugs into your motherboard. If that cable came loose or you forgot to plug it in when you built the machine, WiFi works perfectly but Bluetooth literally doesn’t exist. I see this at least twice a month with new builds. Guy came to us last month, brand new Corsair AX210 card, spent two days reinstalling drivers before he messaged us. Thirty seconds on a video call — “do you see a thin cable running from the card to a USB header?” He didn’t. Cable was sitting in the box the card came in. Plugged it in, Bluetooth appeared instantly.

Windows Update Broke Your Bluetooth (Probably)

This is where the majority of my Bluetooth tickets originate, and I’m going to be specific about which updates caused problems because nobody else on the internet seems to bother with this.

Microsoft rolled out 24H2 and things went sideways fast. Headsets that worked fine on 23H2 suddenly showed as “Connected” in Settings but played zero audio — the January 2025 cumulative patch did that, and Microsoft took weeks to push a fix even though 1,300-plus users were screaming about it on the Q&A forums. A few months later the visibility bug hit: your devices were paired and working but totally invisible in Quick Settings and the Settings app, like the UI forgot they existed. Microsoft actually pushed an emergency hotpatch outside the normal Patch Tuesday schedule for that one, which tells you how bad it was — they almost never do that.

On top of the Windows issues, Intel’s Bluetooth driver version 23.60 shipped alongside those same 24H2 updates and broke auto-reconnection on their whole AX200/AX210/AX211 adapter lineup. Instead of your headphones reconnecting when you flipped them on, you had to go into Settings every single time, remove the device, put the headphones back in pairing mode, re-pair, hope it took. I had a customer in Denver who did this ritual twice a day for three weeks before he called us.

If your Bluetooth died right after an update, go to Settings, Windows Update, Update history and check what installed recently. If the dates line up with what I described above, uninstall the offending patch — scroll down in Update history, “Uninstall updates,” find the KB number, rip it out, restart. If you aren’t sure which one did it, Settings, System, Recovery, “Go back” rolls your entire Windows build back to whatever was running before. That option vanishes after 10 days though, so don’t sit on it. And once you’ve fixed it, grab Microsoft’s “Show or Hide Updates” tool — search for wushowtroubleshoot.diagcab — to block the same update from sneaking back in. Microsoft pretends this tool doesn’t exist on Windows 11 but it works fine.

"If Bluetooth broke right after a Windows Update and rolling back the update fixes it, use Microsoft's 'Show or Hide Updates' tool to block that specific KB from reinstalling. Otherwise Windows Update will push the same broken patch again within a week."

The Dumb Stuff Worth Trying First

I feel slightly embarrassed listing these but they solve the problem often enough that I’d be doing you a disservice if I didn’t.

Toggle Bluetooth off and back on. Quick Settings (Win+A), click the Bluetooth icon off, wait a full five seconds, click it back on. If the icon is missing from Quick Settings entirely, go to Settings, Bluetooth & devices, and use the toggle there.

Check Airplane Mode. Three customers this year — three — had their Bluetooth “break” because they accidentally pressed the Fn+airplane key combo on their laptop keyboard. Win+A shows you if Airplane Mode is active.

Remove the device entirely and pair it again fresh. Settings, Bluetooth & devices, find the device, click the three dots, Remove device. Then put your headphones or mouse back into pairing mode and reconnect from zero. Stale pairing keys get corrupted during updates and the only way to clear them is to nuke the pairing and redo it.

Your Bluetooth Driver — Why the Chipset Matters

Every guide on the internet tells you to “update your Bluetooth driver.” None of them mention that Intel, Realtek, and Qualcomm drivers come from different places, break in different ways, and need different fixes. Here’s how to figure out what you’ve got and what to do about it.

Open Device Manager, expand Bluetooth, look at the adapter name. “Intel(R) Wireless Bluetooth” means Intel. “Realtek Bluetooth” or anything starting with RTL means Realtek. “Qualcomm” or “QCA” means Qualcomm.

Intel adapters — AX200, AX210, AX211, and the newer BE200 — are the most common in laptops and aftermarket PCIe cards. Go directly to Intel’s driver download page and run their Driver & Support Assistant tool. Do not use the driver that Windows Update pushes — Intel’s own driver is almost always a version or two ahead of what Microsoft distributes through Windows Update, and the Windows Update version has caused problems specifically with 24H2 on multiple occasions. If you installed Intel driver version 23.60.x and your devices won’t auto-reconnect, roll it back: Device Manager, right-click the adapter, Properties, Driver tab, Roll Back Driver. If Roll Back is grayed out, you’ll need to manually download the previous version (23.40 or 23.50) from Intel’s download center.

Realtek — common in budget and mid-range laptops. Realtek’s own driver website is a disorganized mess, so go to your laptop manufacturer’s support page (Dell, HP, Lenovo, ASUS) and search for your exact model number. There’s a specific Realtek quirk worth knowing: sometimes the generic Microsoft driver actually works better than the manufacturer’s driver. If you’ve been using the OEM driver and having issues, try ripping it out — Device Manager, right-click the adapter, Uninstall device, check “Attempt to remove the driver,” restart, and let Windows install its own generic driver. I’ve fixed a half-dozen Realtek Bluetooth problems this way this year alone.

Qualcomm shows up on Surface devices and some HP models. Go to your device manufacturer’s support page for drivers — Qualcomm doesn’t distribute consumer drivers directly. For Surface specifically, check the Microsoft Update Catalog and search for “Surface Bluetooth.”

Bluetooth Services — All Three of Them

Most guides tell you to restart “the Bluetooth service.” There are actually three separate services that have to be running, and killing one can take the others down with it.

Hit Win+R, type services.msc, Enter. The Bluetooth Support Service is the big one — set it to Automatic, and if it’s already showing “Running” but nothing works, restart it anyway because sometimes it gets wedged in a bad state where it’s technically alive but not actually processing connections. That specific move — restarting a service that’s already “running” — fixes maybe one in eight Bluetooth tickets I handle where everything else checks out. The Audio Gateway Service handles call routing for headsets (Zoom, Teams, Discord microphone stuff), and the User Support Service deals with pairing and visibility. If any of the three refuses to start, open its Dependencies tab — there’s usually a fourth service somewhere in the chain that failed first, and that’s the real culprit.

The Power Setting That Murders Bluetooth on Laptops

This is my single favorite Bluetooth fix because it’s so well-hidden that most people never find it, and it causes the most maddening symptom: Bluetooth works fine for a while, then randomly disappears, then comes back on its own, then disappears again.

Device Manager, find your Bluetooth adapter, right-click, Properties, Power Management tab. Uncheck “Allow the computer to turn off this device to save power.” Apply.

Now here’s the part that trips people up: do the same thing for every USB Root Hub listed under “Universal Serial Bus controllers” in Device Manager. On most laptops and many desktops, the Bluetooth adapter connects through an internal USB bus. When Windows puts the USB hub to sleep to conserve power — which it does aggressively on battery — it takes Bluetooth down with it.

A customer I worked with last month in Portland, graphic designer with an HP Envy 16, had her Logitech MX Master 3S mouse disconnecting every 15 to 20 minutes. No obvious pattern, nothing useful in Event Viewer. The USB Root Hub was going to sleep after 15 minutes of what it considered “inactivity” — which from the hub’s perspective means no bulk data transfers, even though the Bluetooth mouse was sending position data the whole time. Unchecked one box. Zero disconnects since.

WiFi and Bluetooth Interference

If your Bluetooth is flaky rather than dead — works sometimes, drops out during large downloads, audio stutters when you’re streaming video — the problem might not be Bluetooth at all. It might be WiFi stepping on it.

Most modern laptops use a combo WiFi/Bluetooth card where both radios share the same physical antenna and the same 2.4GHz frequency range. When WiFi is moving a lot of data on 2.4GHz, Bluetooth gets squeezed out. The fix is straightforward: force your WiFi to 5GHz. Log into your router and either split your 2.4GHz and 5GHz networks into separate SSIDs or disable 2.4GHz entirely if all your devices support 5GHz. Connect your laptop to the 5GHz network only, which frees the 2.4GHz band for Bluetooth.

Two other interference sources people miss: USB 3.0 devices generate radio noise right in the 2.4GHz sweet spot. If your Bluetooth cuts out whenever you plug in an external USB 3.0 drive, move that drive to a port on the opposite side of the laptop. And microwave ovens — yes, really — blast 2.4GHz while they’re running. If your home office desk is right next to the kitchen and your Bluetooth headphones drop every day at lunch, now you know why.

Connected But No Sound (The Audio Profile Mess)

The headset is paired. Windows says it’s connected. Volume isn’t muted. But no sound comes through, and you’ve checked everything three times.

Bluetooth headsets support two separate audio modes and this is where the confusion lives. A2DP handles stereo music — decent quality, no microphone. HSP/HFP handles calls — terrible quality, mono, but includes the microphone. When Windows switches your headset to HSP/HFP mode (which it does automatically when any app requests microphone access), stereo audio stops because the headset physically can’t do both simultaneously over classic Bluetooth.

Right-click the speaker icon in the taskbar, Sound Settings, scroll to output device. You’ll probably see two entries for the same headset — one labeled “Stereo” and one “Hands-free AG Audio.” Select Stereo for music and video. If Stereo isn’t listed, Windows has locked the headset into call mode and you need to close whatever app grabbed the microphone.

The LE Audio thing. Windows 11 24H2 introduced Low Energy Audio, which is supposed to be better — higher quality, lower latency, supports stereo and microphone simultaneously. But it breaks a lot of older headphones that don’t support it properly. A college student in Boulder called us last week with Sony WH-1000XM5 headphones that connected fine but played zero audio — they worked perfectly on his phone. He’d tried everything. The fix was one toggle: Settings, Bluetooth & devices, click the headphones, turn off “Use LE Audio when available.” Eight seconds, done. LE Audio was trying to negotiate a connection mode the headphones couldn’t handle, and instead of falling back to A2DP gracefully, it just failed silently.

When the Adapter Is Actually Dead

You’ve been through everything above and nothing sticks. Device Manager shows a persistent Code 43 that doesn’t clear after driver reinstalls. Or the adapter simply isn’t there, even though BIOS confirms Bluetooth is enabled and you’ve tried every driver version available for your chipset.

On a laptop made after 2020, the Bluetooth adapter is part of the WiFi card, and the WiFi card is usually soldered to the motherboard. You’re not replacing that without a board swap.

On a desktop, replacing the PCIe WiFi/Bluetooth card is easy — a TP-Link AX3000 with WiFi 6 and Bluetooth 5.2 runs about $30. Just remember that USB header cable for the Bluetooth side.

The universal workaround that works on anything: a USB Bluetooth dongle. TP-Link UB500 is about $13, ASUS USB-BT500 is about $15, both Bluetooth 5.0. Plug it in, let Windows install the generic driver, disable the built-in adapter in Device Manager so they don’t conflict, and pair your devices through the dongle. I keep two of these in my desk drawer at work because I recommend them to someone roughly once a week.

If you’ve spent an hour trying fixes and you’re going in circles, a $9.90 remote diagnosis takes about 15 minutes. We connect to your screen, check adapter status, driver versions, service configurations, event logs, and tell you exactly what’s broken. Software problem — we fix it in the same session. Dead hardware — we tell you exactly which dongle or card to order. Message us on WhatsApp, usually respond within five minutes.

---

Related guides: if your WiFi also keeps disconnecting, Bluetooth and WiFi share the same radio — fixing one often fixes both. If you’re getting no sound at all, the audio routing might be broken at a deeper level than Bluetooth. And if your Bluetooth issues started right after a Windows Update got stuck or failed mid-install, the update may have corrupted your driver stack.

Last verified: May 2026