Bluetooth Headphones Connected But No Sound on Windows

The headphones say connected. The battery indicator is there. Windows shows them in the Bluetooth device list with a reassuring tick. And there is no sound at all — or the sound is still coming out of the laptop speakers while the headphones sit silently on your head.

This is almost never a broken headset. It is a quirk of how Windows handles Bluetooth audio, and once you know about it the fix takes about fifteen seconds.

The two-device problem

Bluetooth audio does not have one mode. It has two, and they are mutually exclusive:

Windows exposes each of these as a separate audio output device with the same device name. So a single pair of Sony WH-1000XM5s appears in your output list twice:

Headphones (WH-1000XM5 Stereo)
Headset (WH-1000XM5 Hands-Free AG Audio)

If your output is set to the Headset entry while nothing is using the microphone, Windows may produce no audio at all, or audio so muffled it sounds broken. If the output is still on Speakers, you get nothing in the headphones at all.

That one mechanism accounts for the large majority of “connected but no sound” reports on Windows.

Fix 1 — Pick the right output device

Start here, because it is both the most likely cause and the fastest check.

1. Click the speaker icon in the system tray.
2. Click the arrow (>) beside the volume slider to expand the output list.
3. Select the entry with Stereo or Headphones in the name.

Play something. In most cases that is the whole fix.

If the Stereo entry is not listed, the headphones have connected using only the Hands-Free profile. Disconnect and reconnect them from Settings → Bluetooth & devices, and check whether a call app is holding the microphone open — Teams, Zoom, Discord and Slack all do this even when idle in the background.

Fix 2 — Check the per-app volume mixer

If some apps have sound and others do not, Windows is routing them to different devices. This happens silently when an app was open while you changed the default.

1. Settings → System → Sound.
2. Scroll to Advanced → Volume mixer.
3. Each running app has its own Output device dropdown.

Set any app pointing at the wrong device to Default, or directly to the headphones’ Stereo entry. Also confirm no app is muted, and that the headphones’ own master slider is not at zero.

Fix 3 — Enable the device in the Sound control panel

The legacy Sound panel still controls things the modern Settings app does not, including whether a device is enabled at all.

1. Press Win+R, type mmsys.cpl, press Enter.
2. The Playback tab lists your output devices.
3. Right-click an empty area and tick Show Disabled Devices and Show Disconnected Devices.

You will now see both headphone entries. If either is greyed out and marked Disabled, right-click → Enable.

Then right-click the Stereo entry → Set as Default Device. And separately, right-click it → Set as Default Communication Device only if you want calls routed there too.

Check the device is not muted at the driver level

With the Stereo entry selected, click Properties → Levels tab. Confirm the slider is not at zero and the speaker icon beside it does not show a mute symbol. A device muted here stays silent no matter what the system tray volume says.

Then go to the Advanced tab and untick Allow applications to take exclusive control of this device. An app holding exclusive control — often a DAW, a game, or a conferencing client — locks every other app out of the device, which presents as silence everywhere else.

Fix 4 — Restart the Bluetooth Support Service

Windows’ Bluetooth stack gets stuck. Restarting the service clears it without a reboot.

1. Press Win+R, type services.msc, press Enter.
2. Scroll to Bluetooth Support Service.
3. Right-click → Restart.
4. Double-click it and confirm Startup type is set to Automatic. If it is Manual, change it and click Apply.

Your Bluetooth devices will disconnect and reconnect within a few seconds. Also check Bluetooth Audio Gateway Service and Bluetooth User Support Service in the same list and make sure neither is stopped.

Then restart the audio stack too, since it often gets stuck alongside: find Windows Audio and Windows Audio Endpoint Builder in the same services list and restart Windows Audio Endpoint Builder — it restarts Windows Audio as a dependency.

Fix 5 — Remove the device and pair it again

A stale pairing record carries corrupted profile state, and re-pairing rebuilds it. Do this on both sides, because removing it from only Windows leaves the headphones still remembering the old link.

1. Settings → Bluetooth & devices → the ⋯ beside your headphones → Remove device.
2. Reset the headphones themselves. This is the step people skip and it is the one that matters — it clears the headphones’ own pairing list. The method is model-specific, commonly holding the power or pairing button for 10–30 seconds until the indicator flashes a different colour. Check the manual.
3. Restart the PC. This clears the in-memory Bluetooth state properly.
4. Pair again from scratch.

Fix 6 — Drivers and power management

Two settings on the adapter cause audio that works and then stops.

Disable adapter power saving:

1. Right-click Start → Device Manager.
2. Expand Bluetooth → your adapter (Intel Wireless Bluetooth, Realtek Bluetooth, or similar) → Properties.
3. Power Management tab → untick Allow the computer to turn off this device to save power.

Do this for every Bluetooth entry that offers the tab.

Update the driver properly. Get the Bluetooth driver from your laptop manufacturer’s support page for your exact model — Dell, HP, Lenovo, ASUS. Windows Update ships generic reference drivers that frequently lack the vendor’s audio fixes. On many laptops the Wi-Fi and Bluetooth share a combined module, so updating the wireless driver updates both.

If the problem started immediately after a Windows update, try the reverse: Device Manager → adapter → Properties → Driver tab → Roll Back Driver.

Run the troubleshooters. Settings → System → Troubleshoot → Other troubleshooters, then run both Bluetooth and Audio. They are better than their reputation for exactly this class of fault, because they reset endpoint state automatically.

What not to do

• Do not uninstall the Bluetooth adapter driver with “delete the driver software” ticked unless you already have the replacement downloaded. You can end up with no Bluetooth at all and no way to fix it without a USB drive.
• Do not buy a Bluetooth dongle before checking the output device. An external dongle alongside a built-in adapter creates two stacks competing, which is a worse problem than the one you started with.
• Do not use third-party “Bluetooth driver updater” tools. They install mismatched drivers and routinely make a working adapter unusable.
• Do not set the Headset / Hands-Free entry as your default playback device. It forces mono, low-bitrate audio for everything, including music. It should only ever be the Default Communication Device.
• Do not factory reset Windows for a headphone problem. Reset the headphones and the pairing first.

When quality is the problem rather than silence

If you now have sound but it is thin, muffled and obviously low quality — and it only happens on calls — that is not a fault. It is the Hands-Free profile doing exactly what it was designed to do. Why Bluetooth audio sounds terrible on calls explains the mechanism and the practical workarounds.

And if the headphones keep dropping the connection entirely rather than playing silently, why Bluetooth headphones keep disconnecting covers the interference and pairing causes behind that.

Realistic expectations

Selecting the Stereo output device fixes the majority of these cases immediately. Restarting the Bluetooth Support Service handles most of what is left, and a clean re-pair covers nearly all the remainder.

If the headphones produce no sound on every device you own — a phone, a tablet, another computer — the headset itself has failed, and that is a warranty conversation rather than a troubleshooting one.