‘Laptop not detecting headphones’ is three different problems wearing one name: 3.5mm wired headphones the jack does not sense, USB headsets Windows does not enumerate, and Bluetooth headphones that will not pair or connect. Each rides a completely different hardware and driver path, so the first step is always identifying which kind you have — the fixes do not overlap.

This guide is the diagnostic hub: it walks each connection type through its own ordered repair sequence, with links to the deep-dive guides for each. Work the section matching your headphones; do not mix sequences.

Quick orientation: 3.5mm issues are jack-detection and codec-driver problems; USB issues are device-enumeration and power problems; Bluetooth issues are radio, service, and pairing problems. The deep dives: 3.5mm jack detection , USB headsets , Bluetooth on Windows 11 , and the post-update detection guide .

Why this happens

  • Wrong headphone type assumed — Troubleshooting the jack when the issue is Bluetooth pairing wastes the whole session.
  • Jack detection disabled (3.5mm) — Realtek’s plug-detection setting turned off by updates.
  • USB enumeration failure (USB) — Port power, hub, or driver state preventing the headset’s sound card from appearing.
  • Bluetooth radio/service down (Bluetooth) — Support service stopped or driver replaced — no radio, no headphones.
  • Wrong default device — All three types: audio routing to speakers because the headphone endpoint never became default.
  • Disabled device in Sound settings — Windows-level disable hides the endpoint from every app.
  • Hardware fault (any type) — Broken jack, dead USB DAC, or failed Bluetooth module — last resort after software.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Identify your headphone type and test basics

Diagnosis before treatment. Two minutes here picks the right repair path.

  1. Confirm the connection: 3.5mm plug, USB (wired/dongle), or Bluetooth.
  2. Test the headphones on another device (phone, tablet) to prove they work.
  3. For 3.5mm: inspect the jack for lint; for USB: try a different port directly on the laptop; for Bluetooth: confirm the headphones are in pairing mode.
  4. If they work elsewhere, the laptop side is at fault — continue in the matching section below.

Fix 2: Fix 3.5mm: jack detection and codec driver

The wired path: physical jack → Realtek codec → driver → Windows.

  1. Clean the jack with compressed air/a toothpick; test a second pair of headphones.
  2. Open Realtek Audio Console > Device advanced settings > enable the auto-popup on plug-in.
  3. In Sounds > Playback, show disabled/disconnected devices; enable Headphones and set as default.
  4. If still undetected, reinstall the Realtek driver from the laptop maker’s site (full details in the linked 3.5mm deep-dive).

Fix 3: Fix USB: enumeration and power

The USB path: port power → enumeration → usbaudio driver → default device.

  1. Plug directly into the laptop (no hub/dock); try ports on both sides.
  2. In Device Manager, uninstall the headset under Sound controllers and Audio inputs/outputs, then replug.
  3. Disable USB selective suspend (power plan + USB Root Hub power management).
  4. Install the vendor’s app/firmware for gaming headsets (full sequence in the linked USB deep-dive).

Fix 4: Fix Bluetooth: radio, service, pairing

The wireless path: radio → support service → pairing → audio profiles.

  1. Verify Bluetooth is on and the Support Service is running (services.msc).
  2. Remove the old pairing from both the laptop and the headphones, then re-pair from scratch.
  3. In Device Manager, reinstall the Bluetooth adapter driver if the radio misbehaves.
  4. Check the headphones connect with the A2DP (stereo audio) profile, not just Hands-Free (full details in the linked Bluetooth guides).

Fix 5: Set defaults and unmute everywhere

Applies to all three types — the universal ’no sound despite detection’ fix.

  1. Sound settings: set the headphones as default for both Output and Input.
  2. Check per-app volumes in the Volume Mixer (Win + G or Settings > Sound > Volume mixer).
  3. Inspect the headphones’ own controls: inline mute switches, volume wheels, and mic mutes.
  4. In Sounds > Playback > headset Properties, disable exclusive mode if one app hogs the device.

Fix 6: Check microphone permissions and app settings

‘Headphones work but mic does not’ is usually permissions, not detection.

  1. Settings > Privacy & security > Microphone: ensure access is on and your apps are allowed.
  2. In conferencing apps (Teams, Zoom, Discord), verify the input device is set to the headset mic — apps remember their own devices.
  3. For Bluetooth, confirm the Hands-Free/Headset profile is connected, not just A2DP stereo.
  4. Test the mic in Sound settings > Input with the live level meter. If the meter moves, the mic works and the app was misconfigured — see our microphone troubleshooting .

Fix 7: Rule out hardware failure

When every software path is exhausted, test the hardware decisively.

Keep a cheap USB sound adapter in your laptop bag if you depend on wired audio: it is a ten-dollar insurance policy that bypasses jack, codec, and driver problems alike. For a laptop with a flaky jack, it is often the permanent fix — more reliable than a board-level jack repair and instantly reversible.

  1. 3.5mm: wiggle the plug — intermittent sound means worn jack contacts; a cheap USB sound adapter bypasses a dead jack.
  2. USB: if the headset is invisible on multiple computers, its DAC/cable has failed.
  3. Bluetooth: if the headphones pair with a phone but never appear on the laptop, the laptop’s Bluetooth module/driver is suspect.
  4. Microsoft’s audio device support documents the official hardware-isolation steps.

Closing

Headphone detection is three separate problems — jack sensing, USB enumeration, Bluetooth pairing — and the fix is always in the section matching your connection type. Identify the type, prove the headphones work elsewhere, then walk that section’s ordered sequence: most cases resolve at the driver or default-device step without ever touching hardware.

Frequently asked questions

Why does Windows show my headphones as disconnected when they are plugged in?
For 3.5mm, the jack’s detection switch is not triggering — lint in the jack, a partially inserted plug, or Realtek’s jack detection being disabled. For USB, the headset failed to enumerate: try another port, reinstall its device entries, and disable USB selective suspend. For Bluetooth, ‘disconnected’ with a successful pairing usually means the audio profile (A2DP) did not connect — remove and re-pair the device.
Should headphones be set as both default device and default communications device?
Yes, ideally. ‘Default Device’ routes general audio (music, videos, games) and ‘Default Communications Device’ routes calls (Teams, Zoom, Discord). Setting the headphones as both ensures calls and media alike use them. If calls go to speakers while music plays in the headphones, the communications default is pointing at the wrong device — a two-second fix in Sounds > Playback.
Why do my Bluetooth headphones pair but produce no sound?
Pairing and audio are separate steps: the headphones may connect with only the Hands-Free profile (calls) while the A2DP stereo profile fails. In Settings > Bluetooth & devices, check the device shows as connected for audio. Also verify the headphones are the default output device and that their own volume is up — Bluetooth headphones have independent volume from Windows. Removing the pairing from both sides and re-pairing fresh resolves most profile issues.
Can a Windows update break headphone detection?
Yes, and it does so differently per type: updates disable Realtek jack detection or replace the codec driver (3.5mm), reset USB power management (USB), and replace Bluetooth drivers or stop the Bluetooth Support Service (Bluetooth). If detection broke right after an update, the fix is type-specific but the principle is shared: restore the working driver, re-enable the disabled setting, and block the bad update from recurring.