Windows 11 Audio Not Working After Update, Explained

Short answer: if your Windows 11 audio stopped working right after an update, it's almost always one of four things — the audio driver got replaced with an incompatible or generic version, the wrong output device got set as default, the Windows Audio service failed to restart cleanly, or (less often) a driver enhancement setting is silently muting output. Restarting the two audio services first takes thirty seconds and fixes more of these than people expect.

I've lost track of how many "no sound after update" tickets turn out to be the second one on that list — a monitor, a Bluetooth device, or a virtual meeting audio driver quietly became the default output during the update, and the PC is playing sound perfectly fine into a device nobody's listening to. Check that before you touch a single driver.

The default output device

Click the speaker icon in the taskbar, and look at what's selected as the output. Updates — especially ones that touch the display or Bluetooth stack — can reset this to a monitor's HDMI audio, a disconnected Bluetooth headset, or a virtual device left behind by conferencing software. If your actual speakers or headphones aren't the one with the dot next to it, that's your whole problem, and no driver reinstall will fix it.

Settings > System > Sound > Output > choose the correct device

While you're there, check the per-app volume mixer too (Settings > System > Sound > Volume mixer). It's common for one specific app to have been muted or set to a different output device independently of the system default, especially browsers.

Restarting the audio services

This is the step most guides bury near the bottom, and it's the one that fixes more post-update silence than anything else on this list, because it's specifically what Microsoft's own support documentation lists as a direct fix for audio that stops working after an update.

Win + R > services.msc > Enter

Find Windows Audio, right-click, Restart. Then find Windows Audio Endpoint Builder, right-click, Restart. Test sound before doing anything else. If either service was stopped and wouldn't restart, or restarts and immediately stops again, that's your confirming sign the update left something in a broken state rather than just resetting a setting — move on to the driver steps below.

Symptom, confirming check, and fix

What you're seeing	Confirming check	Fix
Speaker icon shows normal, volume moves, but nothing plays	Check Settings > System > Sound > Output for the wrong device selected	Manually select the correct output device
Speaker icon has a red X or says "no audio output device"	Device Manager > Sound, video and game controllers shows a warning icon or the device is missing entirely	Update or reinstall the audio driver from Device Manager, or the OEM's site if that fails
Sound worked yesterday, update installed overnight, silence today	Check Windows Update history for what installed; try Roll Back Driver in Device Manager first	Roll back the audio driver; if that's not available, uninstall the device and let Windows reinstall it
One specific app has no sound, everything else is fine	Check that app's own audio/output settings and Windows' per-app volume mixer	Fix the app-level output setting; consider Repair from Settings > Apps if it's a Store app
Audio crackles, stutters, or plays at the wrong pitch after the update	Sound settings > device properties > Advanced tab, check the sample rate/format	Change the format (commonly to 16-bit, 44100 Hz) and retest, or disable audio enhancements

Common mistakes people make chasing this down

Reinstalling the audio driver before checking the output device and restarting services wastes time — it's an invasive step for something that's frequently a one-click setting. Uninstalling the audio device and letting Windows reinstall a generic driver, then giving up when it doesn't sound as good as before, is another one: the generic Microsoft driver plays audio but usually skips vendor-specific enhancements, virtual surround, and sometimes even the correct number of output channels. If sound comes back after that step but quality is worse, go to the OEM's support page (Dell, HP, Lenovo, or the motherboard maker for a desktop) and install their specific Realtek, Conexant, or Cirrus Logic package rather than settling for generic.

Downloading a driver from a random "driver updater" utility instead of the manufacturer's own site is a mistake I see constantly, and it's worth avoiding — these tools frequently install mismatched or outdated packages that create new problems on top of the one you started with.

If audio disappeared the same day as a Windows Update and Roll Back Driver isn't available in Device Manager, don't assume you're stuck. Go to Settings > Windows Update > Update history > Uninstall updates, and remove the specific update that lines up with when sound stopped. This is more reliable than guessing at driver versions when the timing is that precise.

Driver-level checks, in order

1. Open Device Manager, expand Sound, video and game controllers, and look for a yellow warning icon or a missing device entirely.
2. Right-click the audio device, choose Update driver > Search automatically for drivers.
3. If that doesn't help, go back to Properties > Driver tab and try Roll Back Driver — only available if Windows kept a copy of the previous version.
4. If Roll Back isn't offered, uninstall the device entirely (check "Delete the driver software for this device" if you plan to install a fresh OEM package afterward), then reboot. Windows will reinstall a driver automatically; replace it with the manufacturer's specific package if quality or missing features are an issue.
5. Check Windows Update's optional driver updates too: Settings > Windows Update > Advanced options > Optional updates — audio driver updates sometimes sit there instead of installing automatically.

What I'd do differently next time

Before installing any feature update, I create a System Restore point on machines where I can't afford downtime, specifically because audio and Bluetooth stacks are two of the more fragile pieces of the update process. It costs nothing and takes thirty seconds, and it turns "roll back the driver and hope" into "restore to five minutes before the update ran," which is a much shorter troubleshooting session. It's not a step most people bother with until after the first time it saves them.

If you manage more than one PC, running Microsoft's Get Help audio troubleshooter first (search "audio troubleshooter" in Get Help, or Settings > System > Troubleshoot > Other troubleshooters > Playing Audio) is genuinely worth doing before the manual steps above — it checks default device, mute state, and driver status automatically and will sometimes catch the fix in under a minute.

Where to go from here

If sound is back but only through your speakers and not HDMI, or Bluetooth pairing itself is the actual problem rather than the driver, those are different failure modes with their own separate fixes — an HDMI audio dropout after an update usually isn't the same root cause as a missing sound device, and a Bluetooth device that won't connect at all needs a different checklist than one that connects but stays muted. Chase those down as their own separate problem rather than assuming it's the same driver issue you just fixed here.