Plugging in headphones and hearing nothing — with the laptop speakers blaring on — means the headphone jack detection failed. On most laptops this detection is handled by the Realtek audio codec: a physical switch in the jack tells the codec something was plugged in, and the driver then reroutes audio. When any link in that chain breaks, Windows never learns the headphones exist.
The best-practice repair order matters here because the causes range from a simple disabled ‘front panel jack detection’ setting to a physically broken jack. Jumping straight to driver reinstalls wastes time when the fix was a checkbox, and fiddling with software wastes time when the jack itself is cracked. Diagnose in the order below.
If the headphones are USB or Bluetooth rather than 3.5mm, different guides apply — see our USB headset walkthrough or the Windows 11 headphone detection guide . For no-sound-at-all situations, start with the Realtek driver repair .
Why this happens
- Front panel jack detection disabled — The Realtek setting that enables plug detection gets turned off by updates or audio apps.
- Headphones disabled as a playback device — Windows can disable the headphone endpoint so it never appears.
- Corrupt Realtek audio driver — The codec driver handles jack sensing; corruption breaks detection while speakers keep working.
- Wrong default device stuck on speakers — Audio routes to speakers because the headphone device never registered.
- Physical jack damage or debris — Lint, bent contacts, or a cracked solder joint prevent the detection switch from triggering.
- Audio enhancements interfering — Third-party APOs can suppress the jack-detection event chain.
- BIOS audio setting disabled — Rare, but some BIOS setups allow disabling the audio codec’s jack detection.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Check for debris and test the headphones
The best first step is the simplest: rule out the headphones and the jack mechanically.
- Test the headphones on a phone or another device to confirm they work.
- Shine a light into the laptop’s jack and remove lint with a toothpick or compressed air — never metal tools.
- Plug in slowly and firmly; a partial insertion can miss the detection switch.
- If another pair of headphones is also not detected, the laptop side is at fault — continue.
Fix 2: Enable jack detection in Realtek Audio Console
This checkbox is the number-one software cause. Updates and audio apps silently disable it.
If the Realtek Audio Console is missing entirely, install it from the Microsoft Store — it only appears when a compatible Realtek driver is installed, so its absence is itself a diagnostic clue pointing at a generic or wrong audio driver. The legacy HD Audio Manager (RtkNGUI64) serves the same purpose on older driver packages.
- Open Realtek Audio Console (Microsoft Store) or the legacy Realtek HD Audio Manager.
- Go to Device advanced settings (often under the gear/wrench icon).
- Ensure ‘Enable auto popup dialog when device has been plugged in’ is checked, and that front/rear panel options treat the jack as headphones.
- Plug the headphones in — you should get a popup asking what you plugged in. Select Headphones.
Fix 3: Show disabled devices and set default
Windows may have the headphone endpoint disabled or simply not selected.
- Right-click the speaker icon > Sounds > Playback tab.
- Right-click empty space > Show Disabled Devices and Show Disconnected Devices.
- If Headphones appear, right-click > Enable, then Set as Default Device.
- Unplug and replug — Windows should now auto-switch.
Fix 4: Reinstall the Realtek audio driver
When the codec driver is corrupt, jack sensing dies while basic speaker output survives. A clean reinstall restores it.
Prefer the laptop maker’s driver over Windows Update’s: maker packages include the jack-detection configuration matched to your exact codec and jack wiring, while generic drivers sometimes misidentify the jack type. After reinstalling, recheck Fix 2’s checkbox — driver installs occasionally reset it to disabled.
- Download the audio driver for your exact laptop model from the manufacturer’s support site.
- In Device Manager > Sound, video and game controllers, right-click the Realtek device > Uninstall device, ticking ‘delete driver’.
- Install the downloaded driver and restart.
- Open Realtek Audio Console and confirm jack detection is enabled (Fix 2), then test.
Fix 5: Disable audio enhancements
Enhancement APOs from vendors can intercept and break the plug-detection event.
- In Sounds > Playback, double-click Speakers/Headphones > Enhancements tab.
- Tick Disable all enhancements and click OK.
- Unplug and replug the headphones.
- If detection now works, re-enable enhancements selectively — or leave them off, since they rarely improve laptop audio.
Fix 6: Update BIOS and check BIOS audio settings
The codec’s jack detection has firmware-level components; BIOS updates fix known sensing bugs.
- Check the laptop maker’s support site for BIOS updates mentioning audio fixes.
- Enter BIOS and verify onboard audio is enabled.
- Apply the BIOS update following the maker’s instructions exactly (plugged in, no interruptions).
- Retest headphone detection after the update.
Fix 7: Evaluate the jack hardware
If software is exhausted, the jack itself is suspect — especially on laptops where the plug takes sideways force.
- Wiggle the plug gently: intermittent detection means worn contacts or cracked solder.
- If one channel works or sound cuts when the cable moves, the jack or plug is damaged.
- External USB sound adapters cost little and bypass a broken jack entirely — the pragmatic fix for out-of-warranty machines.
- For in-warranty laptops with a dead jack, contact the maker; jack replacement requires board-level soldering. See Microsoft’s audio troubleshooting hub for the official diagnostic path.
Closing
Headphone detection failures reward the disciplined order: verify the headphones, clear the jack, enable jack detection in the Realtek console, then reinstall the codec driver. Most cases end at Fix 2 or Fix 4 — the checkbox or the driver. Only when software is fully exhausted should the jack hardware itself take the blame.
