Windows 11 Sound Not Working After Sleep? 12 Fixes That Work
You turn on your PC , you hit the play buttons to listen a song, and there’s just… nothing. No error, no muted icon, no obvious reason. Your Windows laptop or pc sound not working after sleep is one of the most annoying bugs out there because it’s never consistent. It’ll behave for two weeks, then die every single time you wake the machine for three days straight. I’ve fixed this on more machines than I can count, and it almost always comes down to one of twelve things.
Table Of Content
- What’s Actually Causing This
- 1. Restart the Windows Audio Service
- 2. Let the Audio Troubleshooter Actually Finish
- 3. Make Sure the Right Device Is Actually Set as Default
- 4. Stop Windows From Powering Down the Audio Driver
- 5. Update the Driver, or Just Reinstall It
- 6. Turn Off Fast Startup
- 7. See If Windows Update Has Already Fixed It
- 8. Don’t Forget USB Power Settings
- 9. Kill the Audio Enhancements
- 10. Check if It’s Just One App
- 11. Look for a Fighting Audio App
- 12. Run a Clean Boot
- Match the Symptom to the Fix
- When It’s Actually Hardware
- FAQ
- Still Not Working?
What’s Actually Causing This
Sleep mode kills power to most of your laptop or pc hardware, audio included. When your PC or Laptop wakes up, Windows has to bring that hardware back online and hand control back to the driver, and that handoff is where things fall apart. Sometimes the driver doesn’t reload right.
Sometimes the audio service quietly crashes. Sometimes a power setting shut the device off and nobody told it to turn back on. What it’s basically never: In most cases, this is a Windows, driver, or power-management problem not a sign that your speakers suddenly died. That’s the part worth holding onto while you work through this, because it means you’re chasing a setting, not paying for a repair.
1. Restart the Windows Audio Service
You can skip the full reboot for now and just restart the service. You think sounds too easy, works more often than it should.
- First press Win + R buttons, than type
services.msc, and hit Enter - Find Windows Audio, than right-click, and hit Restart
- You can do the same for Windows Audio Endpoint Builder and Remote Procedure Call (RPC)
If you sea Windows Audio was already stopped when you got there, that’s your answer. The service is crashing on wake, not going quiet on its own.
2. Let the Audio Troubleshooter Actually Finish
People close this the second something happens on screen. Don’t. Go to Settings > System > Sound > Troubleshoot common sound problems and let it run all the way through. It checks default device selection, muted channels, and disabled devices, and every once in a while it finds a second problem right after fixing the first one.
3. Make Sure the Right Device Is Actually Set as Default
Feels almost too obvious to mention, but this trips up a lot of people, especially anyone with more than one output device. A monitor with HDMI audio, a Bluetooth headset that reconnects on its own, whatever. Sleep can reset which one Windows thinks is active.
Right-click the speaker icon in your taskbar, open Sound settings, and check that your actual speakers or headphones are the ones selected, not some monitor you forgot was even an audio device.
4. Stop Windows From Powering Down the Audio Driver
This one gets skipped in most guides and it shouldn’t be, because it’s the biggest single cause I run into.
Open your Windows Device Manager, expand Sound, video and game controllers, right-click your audio device, go to Properties, then Power Management. Uncheck “Allow the computer to turn off this device to save power.”
Laptops hit this way more than desktops. Makes sense, since laptops are built to squeeze every bit of battery life they can, and aggressive power management is part of that.
5. Update the Driver, or Just Reinstall It
Old drivers can work fine 95% of the time and still choke specifically on the sleep-wake handoff. It’s a real bug category, and newer driver versions usually patch it.
In Device Manager, right-click your audio device, Update driver, then Search automatically. Nothing found? Try Uninstall device instead and restart. Windows will put a fresh copy back on its own.
Quick tip if your laptop uses Realtek (a lot do): check the manufacturer’s site directly instead of relying only on Windows Update. OEM versions are usually better tuned for exactly this kind of sleep-wake issue.
6. Turn Off Fast Startup
Fast Startup shaves seconds off your boot time by hibernating core drivers instead of fully shutting them down, and audio drivers get caught in that more than you’d think.
Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable, then uncheck Turn on fast startup. Doesn’t slow down waking from sleep at all, this only touches full shutdowns.
7. See If Windows Update Has Already Fixed It
Microsoft’s shipped more than one patch specifically for sleep and wake audio bugs. If you’re a few updates behind, there’s a decent chance the fix already exists and you just haven’t installed it yet.
Settings > Windows Update > Check for updates. Install what’s there, restart, test again. If you’re already current, this one’s not going to help, move on.
8. Don’t Forget USB Power Settings
Using USB headphones, a USB DAC, or a soundbar over USB? Windows can apply the exact same power-saving behavior to the USB port itself, separate from whatever you did to the audio device in step 4.
In Device Manager, expand Universal Serial Bus controllers, right-click each USB Root Hub, go to Power Management, uncheck the power-saving box. A lot of people stop after fixing the audio device and can’t figure out why the problem’s still happening. This is usually why.
9. Kill the Audio Enhancements
Bass boost, virtual surround, loudness leveling, all of that runs as an extra layer sitting on top of your actual driver, and that layer is exactly the kind of thing that doesn’t reload cleanly after sleep.
Right-click the speaker icon, Sound settings, pick your output device, Properties, then find Enhancements or Spatial audio and switch it off. If sound comes back right when you do this, that’s your culprit. You can turn things back on one at a time later to figure out which specific effect was the actual problem.
10. Check if It’s Just One App
Sometimes it’s not really Windows 11 speakers not working after sleep at all, it’s one app that grabbed the audio device and never let go properly after wake.
Test with a second app. Windows’ own sound test works (speaker icon, Sound settings, Test) but Chrome or Spotify stays dead silent? Just restart that one app. No need to touch the rest of the system.
11. Look for a Fighting Audio App
Realtek Audio Console, a Dolby Atmos app, whatever companion software came with your gaming headset. These are known for fighting Windows over who actually controls the audio device right after wake.
Close it, test sound again. If that clears things up, check for an update before you reinstall or reopen it.
12. Run a Clean Boot
If you’re still stuck after all that, something running at startup is probably the real problem. A clean boot disables non-Microsoft startup services temporarily so you can test in a stripped-down environment.
Press Win + R, type msconfig, hit Enter. Under Services, check “Hide all Microsoft services,” then click Disable all. Restart and see if the issue still happens after sleep.
Gone? Turn services back on in small batches until it comes back. Whatever you just re-enabled, that’s your culprit.
Match the Symptom to the Fix
| What’s happening | Try this first |
|---|---|
| Worked fine yesterday, dead today, nothing’s changed | Restart Windows Audio (#1) |
| Almost always happens, and it’s a laptop | Turn off power saving on the driver (#4) |
| Started right after a Windows or driver update | Reinstall the driver (#5) or update Windows (#7) |
| Only happens with USB headphones or a DAC | Fix USB Root Hub power settings (#8) |
| Sound test in Settings works, one app stays silent | Restart that app (#10) |
| None of it works, timing feels totally random | Clean boot (#12) |
When It’s Actually Hardware
Made it through all twelve and nothing’s changed? Try a different set of headphones or speakers on the same port. A dying audio jack or a loose connection inside a laptop can fake a software bug pretty convincingly. This isn’t common. Most people never need to get here. But if the exact same thing happens every single time no matter what you try, it’s worth ruling out before you sink more time into driver settings that were never the problem.
FAQ
Why does my Windows 11 sound stop working every time my PC wakes up? Almost always the audio driver or an audio service fails to fully reload after sleep, usually because a power-saving setting shut the audio controller off and it never came back up properly.
Does restarting my PC fix sound problems after sleep? For a while, yes. A restart forces the driver to reload from scratch. But if you never fix the actual cause, whether that’s a power setting or an old driver, the problem tends to show up again the next time the PC sleeps.
Is this a hardware problem? Rarely. It’s almost always software or driver related, not a failing component. Hardware only becomes a real suspect if the exact same fault happens on different devices plugged into the same port.
Will a Windows update fix this? Sometimes. Microsoft’s targeted sleep-and-wake audio bugs before in past updates, so it’s worth checking even if it isn’t the first thing you try.
Why does this happen more on laptops? Laptops default to more aggressive power management to protect battery life, which makes them more likely to shut the audio controller down during sleep and then fail to bring it back correctly.
Can another audio app cause this? Yes. Things like Realtek Audio Console or a headset’s companion software can end up competing with Windows for control of the audio device right after wake. Closing or updating it is worth testing before anything more involved.
Still Not Working?
If you’ve gone through everything and it’s still dead silent after sleep, start with the clean boot in step 12. It takes longer than the rest, but it finds the actual cause almost every time. Everything else on this list is worth doing first, that one’s just the tiebreaker when nothing else has worked.



