Bluetooth connected but no sound? Connected is not selected

1. Check which device Windows is actually playing through

Start here, because it is the answer more often than everything else combined. Microsoft’s first real step is to click the sound icon in the taskbar and ensure the correct Bluetooth device is selected as the audio output. The fuller path is Start, then Settings, then System, then Sound, where you can confirm the Bluetooth device is set as the output device.

The reason this is so common is that connecting and selecting are genuinely separate operations in Windows. A device can pair, connect, appear in the device list and report itself as working while Windows continues sending audio somewhere else entirely — usually the built-in speakers, sometimes a monitor over HDMI that has speakers nobody has ever used.

It is also why the problem seems to come and go. Windows makes its own decisions about which output to use when devices appear and disappear, so headphones that were selected yesterday may not be today, with nothing having changed on your side.

While you are in Sound settings, check the volume for the device itself rather than only the master volume. A per-device or per-application level set to zero produces exactly this symptom and survives every other fix you might try.

If sound is coming out of the laptop speakers while the headphones show as connected, you have found it. Nothing further down this page applies.

2. A2DP, the profile that actually carries music

If the headphones are correctly selected and still produce nothing, the next question is what the Bluetooth link is doing. Microsoft’s step here is to verify A2DP support: check your device’s documentation or the manufacturer’s website to confirm it supports the A2DP protocol for audio streaming.

Bluetooth is not one thing. It carries different profiles for different jobs, and A2DP — the Advanced Audio Distribution Profile — is the one that carries stereo audio. A device connected on a different profile is genuinely connected, which is why Windows reports it that way, and still has no path for music to travel along.

This is worth checking for anything that is not straightforwardly a pair of headphones. Some headsets, adapters, car kits and older or unusual devices support hands-free calling profiles without full stereo audio, and behave exactly like this.

It also explains a related oddity worth recognising: a headset that works for calls and produces nothing for music is almost certainly running on the call profile. That is the profile system working as designed, not a fault, and the remedy is at the device end rather than in Windows.

3. The audio format setting, for silence and distortion alike

Microsoft documents a specific setting here, and it is one almost nobody finds on their own. Go to Start, then Settings, then Bluetooth & devices, then Devices. Select your Bluetooth device, then choose Advanced sound properties. Under Output settings, set the Format to 2 channels, 16 bit, 48000 Hz — labelled DVD Quality.

A format the device cannot actually handle produces failure rather than degradation. Depending on the device that can mean silence, distortion, stuttering, or audio that plays for a second and stops, which is why this setting is worth checking for several different-sounding symptoms.

The value Microsoft names is a deliberately safe one rather than the best available. If you have previously set something more ambitious to chase quality, this is the setting to put back, and the difference in practice over a Bluetooth link is small.

It is also worth revisiting after a Windows update or a driver change, either of which can leave a format selected that no longer matches what the device negotiates.

4. Removing and re-adding the device

If the settings are right and there is still nothing, Microsoft’s next step is to unpair and re-pair: Start, then Settings, then Bluetooth & devices, find the device, select More options — the three dots — then Remove device, then Add device and select it again.

This does more than it appears to. Re-pairing renegotiates which profiles the device and the computer agree to use, so a connection that came up on the wrong profile, or that carries a stale configuration from an earlier session, gets rebuilt from nothing.

Microsoft also lists toggling Bluetooth itself: Start, Settings, Bluetooth & devices, turn Bluetooth off, wait 10 seconds, then turn it back on. As with pairing problems, the ten seconds is specified, and toggling straight back on often restores the same state rather than resetting it.

Do these in that order — the toggle first, since it costs nothing, then the remove and re-add if the toggle changes nothing.

5. The Bluetooth driver, and when to suspect it

Microsoft’s driver step is to open Device Manager, select Bluetooth, right-click the adapter, choose Update driver, then Search automatically for updated driver software, and restart afterwards.

The time to reach for this is when the timing points at it. Audio that worked and stopped without any change to the headphones, particularly around a Windows update, is a driver story. Audio that has never worked with these headphones on this machine is more likely to be the output selection or the profile.

Microsoft pairs this with checking Windows Update — Start, then Settings, then Windows Update, then Check for updates — because Bluetooth driver revisions arrive through it. On a machine that is behind, that is often the same fix by an easier route.

Microsoft also offers the automated Bluetooth troubleshooter in the Get Help app for this problem, and it is worth running before manual driver work, since it diagnoses and attempts the repair itself.

6. Narrowing it down when none of that works

Two tests separate the remaining possibilities, and both are quick.

First, try the headphones on another device — a phone is ideal. Audio there means the headphones and their A2DP support are fine, and everything left to investigate is on the computer. Silence there too points at the headphones themselves, and no amount of Windows configuration will help.

Second, on the computer, try a different application. Sound in one app and not another is not a Bluetooth problem at all: it is that application’s own output device or volume, both of which are set independently of the system default in Windows. Media players, conferencing tools and browsers all commonly hold their own output setting.

Microsoft’s remaining general steps are the ordinary ones — install available Windows updates, and restart the PC through Start, then Power, then Restart. Worth doing, but after the two tests above rather than before, because the tests tell you where to look and the restart does not.

If you are still stuck, record which output device is selected, whether the headphones produce sound on a phone, whether the silence is in every application, whether the device is confirmed to support A2DP, and whether it ever worked on this machine. Those five answers will separate a selection problem from a profile limitation from a driver fault from a broken pair of headphones.

Frequently asked questions

Sources and review notes

Checked on September 24, 2026. Compiled by Glitchary from Microsoft’s guidance on fixing the Bluetooth connected but no sound issue on Windows. The output device check, the A2DP verification, the audio format value, the unpair and re-pair steps, the 10-second Bluetooth toggle, the driver procedure and the troubleshooter are Microsoft’s. The explanation of why connecting and selecting are separate, the note on call-only profiles, and the two isolating tests in the final section are editorial. Menu paths differ between Windows 10 and 11 — check Microsoft’s current article if yours does not match. Glitchary is independent of Microsoft.

• Microsoft: fix Bluetooth connected but no sound issue on Windows