Sound suddenly not working on Windows 11 is usually fixable in under two minutes — but the fix depends entirely on which part of the audio chain is broken. There are four common patterns, and each points at a different cause:
No sound at all, speaker icon in taskbar has an X on it — Windows doesn’t see an audio device. Could be the audio service stopped, the driver failed, or the wrong device is selected. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
Sound works in some apps but not others — Volume Mixer has the muted application at zero, or the app has its own audio routing. Check Volume Mixer first.
This only helps when the mixer opens normally. If the volume mixer won’t open or respond at all, that is a separate fault with its own set of fixes.
Sound was working, stopped after update — Driver was replaced with an incompatible version. Roll back or reinstall the audio driver.
If keeping drivers current by hand gets tedious across a whole machine, the best driver updater software can automate the checks — though for a single audio driver, the manual roll-back above is usually quicker.
Can hear through headphones but not speakers (or vice versa) — Wrong output device selected. The fix is a single click in audio settings.
Start with the simplest check: right-click the speaker icon in the taskbar → Open Volume Mixer. Is the application you’re trying to hear muted or at zero? That’s the complete fix in a surprising number of cases — the app’s volume was accidentally dragged to zero.
Fix 1: Select the Correct Output Device
Windows often changes the default audio output device when new audio hardware is connected — plugging in headphones, connecting a monitor via HDMI, or adding a USB audio device can silently switch the active output. Switching back takes five seconds.
Click the speaker icon in the taskbar → click the arrow next to the speaker name to see all available output devices → select the correct one (your speakers, headphones, or headset). Test immediately.
If you want to confirm all available devices: right-click the speaker icon → Sound settings → More sound settings → Playback tab. This shows every audio device Windows knows about, including disabled ones. Right-click any grayed-out device → Enable to make it available. Right-click your preferred output → Set as Default Device.
Fix 2: Restart the Windows Audio Service
The Windows Audio service manages all sound output on the system. It occasionally stops — usually after a crash or an interrupted update — and when it stops, all audio stops. Restarting the service doesn’t require restarting the machine.
Press Win + R → type services.msc → press Enter. Find “Windows Audio” → right-click → Restart. Also find “Windows Audio Endpoint Builder” → right-click → Restart. Test audio immediately after restarting both services. If audio returns, the service had stopped and this is the complete fix.
If the services won’t start (greyed out or show errors when starting): right-click each → Properties → Startup type should be set to “Automatic.” If either is set to Disabled or Manual, change it to Automatic → click Start → OK. A service set to Disabled explains recurring audio failures — the service keeps stopping after restarts.
Fix 3: Update or Roll Back the Audio Driver
The audio driver is the most common cause of sound stopping suddenly, especially after Windows updates. Windows updates regularly replace working manufacturer audio drivers with generic Microsoft versions that don’t always perform as well. Realtek, Intel, and AMD audio drivers are particularly prone to this.
To update: Device Manager → Sound, video and game controllers → right-click your audio device (often “Realtek High Definition Audio” or “Intel Smart Sound Technology”) → Update driver → Search automatically.
Better approach — get the manufacturer driver: The generic Microsoft driver Windows Update installs is often not the best option. Go to your laptop or motherboard manufacturer’s support page and download the audio driver directly. Manufacturer audio drivers typically have better performance and fewer compatibility issues than the generic Windows version.
If audio stopped after a recent update — roll back: Device Manager → right-click audio device → Properties → Driver → Roll Back Driver. This restores the previous driver version that was working. If Roll Back Driver is greyed out (no previous version stored), download the previous driver version from the manufacturer’s archive.
Fix 4: HDMI Audio — The Output Nobody Remembers to Set
When using a monitor or TV connected via HDMI, the audio comes through HDMI as a separate output device. Windows sometimes switches to HDMI audio when a display is connected, sending audio to the monitor’s speakers (if it has them) or to the HDMI connection rather than the regular speakers. The speakers then appear silent even though audio is working.
Right-click the speaker icon → Sound settings → More sound settings → Playback tab. Look for an entry that says “HDMI” or contains your monitor’s model name. If this is set as the default instead of your regular speakers, right-click your actual speakers → Set as Default Device. Test.
If you want to hear audio through the HDMI-connected screen rather than your PC speakers, do the opposite — set the HDMI audio device as default. Just make sure the monitor has built-in speakers and they’re not muted at the hardware level.
Fix 5: Check Audio Enhancements and Exclusive Mode
Audio enhancements (bass boost, virtual surround, equalisers built into Windows) sometimes conflict with specific applications or audio hardware and cause no sound or distorted sound. Disabling them takes 30 seconds and occasionally resolves audio failures that seem to have no other cause.
Right-click speaker icon → Sound settings → More sound settings → Playback → right-click active output device → Properties → Enhancements tab → tick “Disable all enhancements” → OK. Test audio.
Also check the Advanced tab in the same Properties dialog. If “Allow applications to take exclusive control of this device” is checked and an application has claimed exclusive access, other applications can’t produce sound. Unchecking this prevents exclusive mode conflicts. Also try changing the Default Format (sample rate and bit depth) — some hardware reacts better to 24-bit, 48000 Hz than to 16-bit, 44100 Hz or vice versa.
Bluetooth Audio: HFP vs A2DP
Bluetooth headphones connecting with poor audio quality, or connecting successfully but producing no sound, are often using the wrong Bluetooth profile. Bluetooth audio devices support two profiles: HFP (Hands-Free Profile, for phone calls — poor quality but includes microphone) and A2DP (Advanced Audio Distribution Profile — high quality stereo).
Right-click speaker icon → Sound settings → More sound settings → Playback. For Bluetooth headphones, you’ll see two entries — one labelled “Headset” (HFP) and one “Headphones” (A2DP). The Headset entry is for calls; the Headphones entry is for music. Set Headphones as the default for better quality audio. If only the Headset entry appears, the device is stuck in HFP mode — close any communication apps (Teams, Discord, Zoom) that may have claimed the microphone in HFP mode, then check again.
Fix 6: Run the Audio Troubleshooter
The Windows audio troubleshooter catches a specific set of common issues automatically — wrong output device, stopped audio service, basic driver problems — and is worth running before more involved fixes. Settings → System → Troubleshoot → Other troubleshooters → Playing Audio → Run. Apply any recommended fixes, restart if prompted, and test.
The troubleshooter isn’t a miracle fix, but it handles the most common causes automatically and takes two minutes. Run it early, not as a last resort.
Fix 7: Reinstall the Audio Device
When driver updates and rollbacks don’t resolve the issue, reinstalling the audio device from scratch removes all driver state and starts fresh. Device Manager → Sound, video and game controllers → right-click audio device → Uninstall device → tick “Delete the driver software for this device” → Uninstall → restart. Windows reinstalls the audio driver automatically on boot. This clears corrupted driver state that update and rollback operations don’t always fix.
App-Specific Audio Issues
When audio works in Windows but not in a specific application — a game, a video call platform, or a media player — the issue is almost never the Windows audio system. Check:
- The application’s own audio settings and which output device it’s configured to use
- Windows Privacy settings: Settings → Privacy and security → Microphone (for call apps that need microphone access alongside speakers)
- For browser-based audio: check the padlock icon in the browser address bar for site-specific sound permissions
- Volume Mixer (right-click speaker icon): ensure the specific app isn’t muted in the mixer even if system volume is at full
Our guide on microphone not working on Windows 11 covers the input side of audio problems that often appear alongside output failures when the audio driver is the issue. For audio in Discord specifically, our Discord audio troubleshooting covers the Discord-specific voice settings. Microsoft’s Windows 11 audio troubleshooting covers the exclusive mode configuration for professional audio setups and the spatial audio features that occasionally interfere with standard stereo output.
No Sound After Windows Update: What Changed
Windows updates replace audio drivers more frequently than most people realise. When audio stops immediately after an update, one of three things happened: the update installed a new generic audio driver over the manufacturer driver, the update changed Windows audio policies or service configuration, or the update introduced a compatibility issue with the audio hardware.
Check Windows Update history (Settings → Windows Update → Update history) to see what installed on the day audio stopped working. If a driver update is listed alongside a system update, the driver update is the likely cause. In Device Manager, the Driver tab for the audio device shows the driver date — if it matches the update date and the audio stopped the same day, rolling back that driver (Driver → Roll Back) is the most direct fix.
For the cases where Roll Back Driver isn’t available: download the previous audio driver version from the PC manufacturer’s support page. Most manufacturers maintain driver archives, and going back one or two versions often resolves the regression introduced by the Windows-supplied generic driver. After installing the manufacturer’s driver, prevent Windows Update from replacing it again by using the “Show or hide updates” troubleshooter (available from Microsoft’s website) to hide the specific driver update.
Realtek Audio Console vs Realtek Manager
Machines with Realtek audio chips have two potential audio management applications: the Realtek HD Audio Manager (the older one, installed with the driver) and the Realtek Audio Console (available from the Microsoft Store). These two applications sometimes conflict when both are installed, causing the audio configuration to behave unexpectedly or for settings changes in one app not to take effect.
Check which one is installed and running: search “Realtek” in Start. If both appear, choose one to be the primary management tool and uninstall the other. The Realtek Audio Console (Store version) is the more modern option and better maintained for Windows 11. The classic HD Audio Manager is fine if it’s already working. Having both installed simultaneously is the cause of the audio configuration conflicts, not a feature.
Sound Bar and External Speaker Issues
Sound bars and active speaker systems connected to a PC add an additional potential failure point outside Windows — the external audio hardware itself. Before working through Windows audio fixes for external speakers, check the speakers directly:
- Is the speaker system powered on and its own volume not muted?
- Is the cable firmly connected at both ends — the speaker end sometimes works loose
- Try a different cable if audio was working through a 3.5mm or optical cable that may have failed
- Test the speakers with a phone or another audio source to confirm the speakers themselves work
External speakers with their own DSP processing (most modern sound bars) have their own firmware and settings that can cause audio issues. A factory reset on the sound bar itself occasionally resolves situations where Windows audio is confirmed working but no sound comes from the external system.
Spatial Audio and Windows Sonic
Windows 11 includes spatial audio features (Windows Sonic for Headphones, Dolby Atmos, DTS:X) that convert standard stereo audio to simulated surround sound. When enabled for a device that doesn’t support the spatial audio format being used, audio either stops or becomes heavily distorted. This is a common cause of audio problems after Windows updates that enable spatial audio features by default.
Disable spatial audio: right-click the speaker icon → Sound settings → More sound settings → Playback → right-click the active output device → Properties → Spatial sound tab → Spatial sound format → Off. Test audio immediately after changing this. If sound returns, spatial audio was causing the issue. The feature can be re-enabled later with a different format if the hardware supports it, or left off if standard stereo is preferred.
USB Audio Devices and Class Compliance
USB headsets, DACs (digital-to-analogue converters), and external audio interfaces appear as separate audio devices in Windows rather than using the system audio driver. When these devices show up but produce no sound, the cause is usually one of three things: the wrong output device is selected in Windows (the main speakers are still default), the device needs its own driver installed (some USB audio devices require manufacturer drivers for full functionality), or the USB port has a power or bandwidth issue.
For USB audio devices: always check Sound settings → Playback and confirm the USB device is set as the default. Many users plug in a USB headset and then can’t understand why there’s no sound — the computer is sending audio to the built-in speakers because nothing changed the default output. Selecting the USB device as default is the complete fix in the majority of these cases. If the USB audio device doesn’t appear in the Playback list at all, it’s not being detected — try a different USB port, check Device Manager for the device with any error codes, and check whether manufacturer drivers are available. You might also run into HDMI Audio Not Working on Windows 11.
Sound that works at startup but then cuts out
A distinctive variation is sound that is present for the first minute or two after you log in and then disappears, often returning if you replug a device or restart the audio service. That pattern almost always points to power management rather than a broken driver: Windows is allowed to switch the audio device off to save energy, and on some systems it does so too aggressively and fails to wake it cleanly. Open Device Manager, expand Sound, video and game controllers, right-click your audio device, choose Properties, and on the Power Management tab clear Allow the computer to turn off this device to save power. On a laptop this single change resolves the “sound stops after a while” symptom more often than any driver step.
If power management is not the cause, the other common culprit is an application that grabs exclusive control of the audio device shortly after startup — a conferencing app, a sound-effects or equaliser utility, or a driver control panel launching with Windows. Temporarily disabling startup apps in Task Manager’s Startup tab, then reintroducing them one at a time, isolates the one taking over the device.
Reading the Windows audio event logs
When the cause is genuinely unclear, the Windows event logs will often name it. Open Event Viewer (right-click Start and choose it from the menu), expand Windows Logs → System, and look at the entries around the time the sound failed. Errors from the Windows Audio service (it appears as Audiosrv) point to a service that stopped or failed to start, while warnings from the audio driver — frequently shown with a source beginning “HDAudio” or naming the Realtek or Intel audio component — point to a driver fault instead. Knowing which of the two it is tells you whether to focus on restarting and re-enabling the audio service or on reinstalling the driver, rather than working through every fix blindly.
