Windows 11 KB5089549 Audio Bluetooth Not Working Fix

What is the KB5089549 Audio / Bluetooth Audio Issue?

After installing KB5089549 (released May 13, 2026 — OS Build 26100.8457 for 24H2 and 26200.8457 for 25H2), thousands of users on r/Windows11, Microsoft Answers, and Feedback Hub report that audio output disappears entirely or Bluetooth headphones connect but produce no sound. The taskbar volume icon shows a red X with the tooltip *"No audio output device is installed,"* or Bluetooth headsets appear paired but route to the Hands-Free (HFP) profile only — never Stereo (A2DP).

The root cause is twofold: KB5089549 resets audio defaults and overwrites OEM audio drivers with generic Microsoft High Definition Audio drivers, and the Bluetooth stack regression breaks the A2DP Sink/Source bind for Realtek, Intel, and MediaTek Bluetooth chipsets. Microsoft acknowledged "audio driver problems" in the May 17, 2026 release health dashboard and is preparing a Known Issue Rollback (KIR) through Windows Update.

When does it occur?

• Immediately after the first reboot following KB5089549 install
• Speakers/headphone jack output disappears — Sound Settings shows no output devices
• Bluetooth headphones connect but the device shows only "Headset (Hands-Free)" instead of "Stereo"
• Audio works for 5-10 minutes after login then cuts out until restart
• USB audio interfaces (Focusrite Scarlett, MOTU M2, Steinberg UR22) show distorted audio or no signal
• Realtek HD Audio Manager refuses to open or shows "device not found"
• Intel Smart Sound Technology (SST) driver crashes with Event ID 7000 in Event Viewer

Common causes

• Generic Microsoft HD Audio driver overwriting Realtek/Conexant/IDT OEM driver during update
• Bluetooth A2DP profile bind broken by the new Bluetooth LE Audio stack
• Audio Enhancements re-enabled by the update on previously-disabled outputs
• Windows Audio service (AudioSrv) and Audio Endpoint Builder (AudioEndpointBuilder) failing to start
• Bluetooth Support Service (bthserv) crash loop on Realtek/MediaTek chipsets
• Default device reset to "Speakers — Realtek" even when device is unplugged
• Corrupted audio device cache in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio

Step-by-step fixes

1. Restart Windows Audio and Endpoint Builder services first — Press Win+R, type services.msc, find Windows Audio and Windows Audio Endpoint Builder. Right-click each > Restart. Also check Bluetooth Support Service and Bluetooth Audio Gateway Service — both must show "Running." Set startup type to Automatic if not already. This fixes ~40% of cases without any driver work.

1. Roll back the audio driver to your OEM version — Open Device Manager > Sound, video and game controllers > right-click your audio device (Realtek/Conexant/Intel SST) > Properties > Driver tab > Roll Back Driver. Pick "An earlier version of the driver was working better." Reboot. If Roll Back is greyed out, download the latest from your laptop OEM (Dell, HP, Lenovo, ASUS) — not Microsoft Update.

1. Disable Audio Enhancements — Settings > System > Sound > pick your output device > scroll to Audio enhancements > set to Off. Also right-click the speaker icon in taskbar > Sound settings > device Properties > Spatial sound > Off. KB5089549 silently re-enables enhancements which crash certain Realtek codecs.

1. Fix Bluetooth A2DP (Stereo) profile — Open Settings > Bluetooth & devices > Devices > pick your headphones > three-dot menu > Remove device. Then Device Manager > View > Show hidden devices > expand Sound, video and game controllers and Bluetooth — right-click and uninstall every greyed-out "ghost" Hands-Free or A2DP entry. Re-pair the headphones. They should now register both "Headset" and "Stereo" outputs — set Stereo (A2DP) as default.

1. Force-reinstall the Bluetooth radio — Device Manager > Bluetooth > right-click your Intel/Realtek/MediaTek Bluetooth radio > Uninstall device > check "Attempt to remove the driver." Reboot. Windows reinstalls a clean stack. If WiFi-Bluetooth combo card, also reinstall the WiFi radio because both share the firmware blob.

1. Reset the MMDevices audio registry cache — Open Registry Editor (regedit), back up HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render, then right-click the Render key > Permissions > grant your user Full Control on every subkey ending in {guid}. Reboot. This rebuilds the audio endpoint enumeration that KB5089549 corrupted.

1. Install the KIR (Pro/Enterprise) or wait for Home rollout — On Pro/Enterprise, download KB5089549-AudioStack-KIR.msi from the Microsoft Update Catalog, then gpedit.msc > Computer Configuration > Administrative Templates > Microsoft KIR > Enabled > reboot. Home users receive the server-side KIR push automatically — full rollout completes around May 25-28, 2026 per Microsoft's release health page.

1. Uninstall KB5089549 as a last resort — Settings > Windows Update > Update history > Uninstall updates > select KB5089549 > Uninstall. Reboot. If that option fails or is missing, open an elevated Command Prompt and run: wusa /uninstall /kb:5089549 /quiet /norestart, then reboot. Pause updates for 7 days to prevent re-installation until the KIR ships.

If it still doesn't work

If neither rollback nor reinstall restores audio, run the built-in Audio troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Playing Audio > Run. It catches stale endpoint defaults the registry edit may have missed. For laptops with Realtek + Intel SST dual-codec setups (Dell XPS, ThinkPad X1, Surface Laptop), grab the OEM "Audio Driver Pack" — Microsoft's generic SST driver is incompatible with the partner BIOS on those models, and only the OEM bundle restores Dolby Atmos and Realtek HD audio together. For USB audio interfaces still misbehaving, the manufacturer (Focusrite, MOTU, Universal Audio) released firmware updates in late May 2026 specifically targeting the NDIS/audio stack ordering change in KB5089549 — check your interface's control panel app for a firmware update prompt. If Bluetooth audio still routes only as Hands-Free after every fix above, the BIOS-level Bluetooth radio firmware may need updating; check your laptop OEM's support site for a May 2026 BIOS update referencing Bluetooth LE Audio.