No Sound on Windows 11? Why Your Speakers Went Quiet — and How to Get It Back

It's a small thing that feels like a big thing: you press play, the video runs, the progress bar moves — and there's just silence. No sound from a YouTube clip, no audio on a Teams call, not even the little ding when you plug something in. The reassuring part, almost every time, is that the speakers themselves are perfectly fine. The sound is being sent to the wrong device, muted in a place you didn't think to look, switched off by an audio "enhancement," or knocked out by a driver a recent update changed. Every one of those you can fix yourself, usually in a couple of minutes.

This is the output-side companion to our guides on a microphone that goes silent on calls and a webcam that won't turn on — the three together cover most "my video call is broken" problems, and with so much remote-friendly work across Southern California and the Coachella Valley we get all three constantly. Here's the practical version: work through it in order, easiest and most likely first, and you'll fix the large majority of cases before you ever open Device Manager.

First, the 30-second stuff: volume, mute, and the right plug

Before changing any settings, rule out the things that silence a working speaker. Click the speaker icon at the bottom-right of the taskbar and make sure the volume slider isn't at zero and the icon doesn't have a little "no" symbol over it (that's muted). Many laptops also have a physical mute key or a volume wheel that's easy to bump — check the F-row for a speaker key with a line through it and tap it. If you use external speakers, confirm they're powered on and their own volume knob is up.

Then check what's plugged in. If you've got headphones or a headset in the jack or a USB port, Windows sends sound there and the built-in speakers go quiet by design — unplug them if you want the speakers back, or plug them in firmly if you actually want to use them (a half-seated plug is enough to lose audio entirely). One more easy win before the menus: if the sound cut out and nothing obvious changed, restart the PC. A reboot clears a surprising number of audio glitches on its own.

The #1 cause: Windows is sending the sound to the wrong place

This is the single most common fix, and it's sneaky because everything looks fine — the volume is up, nothing's muted, but you hear nothing. Windows can only play to one output at a time, and it loves to switch on its own: plug in an HDMI monitor or a TV, dock the laptop, or connect a Bluetooth speaker, and Windows may quietly make that the default — so your sound is "playing," just to a screen across the room or a speaker that's switched off. Click the speaker icon on the taskbar and click the little arrow (the ">") next to the volume slider to see every output device, then pick the one you actually want — "Speakers," your headset, whatever it is.

You can set it more permanently in Settings > System > Sound, under the Output section, by choosing your speakers as the default device. The usual culprits to watch for: a monitor or TV connected over HDMI or DisplayPort grabbing the audio (it shows up as something like "NVIDIA High Definition Audio" or your monitor's name), a docking station, or a Bluetooth device that auto-connected. If a particular app is the only thing that's silent while everything else plays, the problem is one level deeper — see the Volume Mixer next.

The Volume Mixer: one app muted while the rest play

If most sounds work but one program — your browser, a game, Spotify, a meeting app — is silent, Windows is almost certainly muting or misrouting just that app. Right-click the speaker icon and choose "Open volume mixer" (or Settings > System > Sound, then scroll to Volume mixer). You'll see a row for each app currently making sound, each with its own volume slider and mute button. Look for any with an "x" next to the speaker icon and click to unmute, and make sure no app's slider is dragged to the bottom.

The Volume Mixer can also send a single app to a different output than the rest of the system — handy on purpose, maddening by accident. If an app stays silent, check that its "Output device" in the mixer is set to your speakers (or to "Default") rather than some disconnected headset or monitor it remembers from last week. There's also a "Reset" button there that returns sound devices and per-app volumes to Windows' recommended defaults, which is a quick way to undo a tangle you can't track down.

Let Windows try, then restart the audio services

Windows has a built-in fixer for exactly this. Go to Settings > System > Troubleshoot > Other troubleshooters and run the one for "Audio" (on current builds it opens in the Get Help app and walks through the checks automatically). It isn't magic, but it catches the simple cases — a wrong default device, a muted level, a stopped service — without you digging through menus.

If sound is still dead, restart the services that actually produce it. Press Windows+R, type services.msc, and press Enter. Find "Windows Audio," right-click it and choose Restart; do the same for "Windows Audio Endpoint Builder." While you're there, double-click each and make sure the Startup type is "Automatic." (These two depend on "Remote Procedure Call (RPC)," which should already be running — leave that one set as it is; just don't disable it.) If a service was stopped, this is often the whole fix; restart the PC afterward so everything comes back cleanly.

Turn off audio "enhancements" — and try a different format

Windows and some sound-card drivers layer effects on top of your audio — spatial sound, bass boost, loudness equalization — and these "enhancements" occasionally fight with a particular device and produce crackling, dropouts, or silence. Turning them off is a safe, reversible test. Go to Settings > System > Sound, click your output device to open its page, scroll to Advanced settings (older builds: "More sound settings"), and set "Audio enhancements" to Off. Play something and see if the sound comes back.

One more setting in the same neighborhood is worth a try when audio is garbled or absent on a specific device: the default format (the sample rate). Open the classic Sound panel — Windows+R, type mmsys.cpl, Enter — go to the Playback tab, double-click your speakers, open the Advanced tab, and pick a different option under "Default Format" (something common like 24 bit, 48000 Hz). Test after each change. It's a small thing, but a format the hardware doesn't like is a real, if uncommon, cause of no sound.

When a Windows update broke it: the driver (and the "no audio device" case)

If the sound died right after a Windows update — and it's not muted, the right device is selected, and the services are running — suspect the audio driver. Right-click the Start button and open Device Manager, then expand "Sound, video and game controllers." Right-click your audio device (often "Realtek Audio" or "High Definition Audio Device") and choose Update driver > "Search automatically for drivers." If it broke immediately after an update, open the device's Properties, go to the Driver tab, and use "Roll Back Driver" to put back the version that was working. If neither helps, choose Uninstall device and restart the PC — Windows reinstalls a fresh copy on the way back up, which clears a lot of post-update trouble. It's the same family of update-broke-my-driver problem we cover when a corrupted network driver knocks out the internet.

A specific, scarier-looking version of this is when the speaker icon shows a red "x" and hovering over it says "No audio output device is installed," or your speakers have vanished from the list entirely. That almost always means the driver dropped out, not that the hardware died. The same Device Manager steps fix it — and the reliable backstop is to pick the generic driver Windows always has: in Device Manager, right-click the audio device, choose Update driver > "Browse my computer" > "Let me pick from a list," and select "High Definition Audio Device." For a laptop, grabbing the current audio driver from your computer maker's support page (Dell, HP, Lenovo, ASUS) using your exact model number is the most dependable fix when the generic one misbehaves.

If a USB headset or speaker went silent in September 2026, it's Microsoft's bug — not your hardware

There is a live example of this happening right now, and it is worth knowing about because the symptom looks exactly like a dead headset. On September 8, 2026, Microsoft shipped that month's security update — KB5124008 on Windows 11 24H2 and 25H2, with the equivalent update on the other versions — and it broke a specific family of USB audio devices. Microsoft's own known-issue entry says that afterwards "some USB Audio Class 1.0 devices might fail to start or produce audio," and lists the symptoms: the device shows "This device cannot start (Code 10)" in Device Manager, there is no audio output, the volume controls are unresponsive or stuck at zero, and the Sound settings themselves are unresponsive or unavailable. Microsoft is also clear about the limit: "This issue is limited to USB Audio Class 1.0 devices." One thing most of the news coverage got too narrow, though — Microsoft's own affected-platforms list is not just the newest Windows. It names Windows 11 versions 26H1, 25H2, 24H2 and 23H2, and Windows 10 versions 22H2 and 21H2 as well. So "I'm not on the latest Windows" is not a reason to rule this out.

The reason we are spending a section on one month's patch is that this is the exact scenario where people spend money they didn't need to spend. A USB headset that produces no sound, has a dead volume slider, and throws a hardware-sounding error in Device Manager reads as broken to anyone, and the obvious move is to order a replacement — which then works, which "proves" the old one had died. Before you do that, three checks take about two minutes. First, timing: open Settings > Windows Update > Update history and see whether an update landed on or just after September 8, 2026, right before the sound stopped. Second, the error: in Device Manager, is it specifically "This device cannot start (Code 10)"? Third, the device class, which is the one that actually settles it — in Device Manager, right-click the audio device, choose Properties > Driver > Driver Details, and look at the file name. Windows has shipped a separate USB Audio 2.0 driver since Windows 10 version 1703, so a device running on usbaudio2.sys is a Class 2.0 device and is not what Microsoft describes, while usbaudio.sys is the USB Audio 1.0 driver — the affected class. And if you want a decisive test with no menus at all: plug the same headset into another computer that hasn't taken the September update. If it plays there, the hardware is fine.

Now the part that matters most, because it is easy to get wrong in both directions. Microsoft released an out-of-band update on September 14, 2026 — KB5129195 for Windows 11 24H2 and 25H2 (builds 26100.9457 and 26200.9457), KB5129242 for 23H2, KB5129194 for 26H1 — and it only partially fixes this. In Microsoft's wording the issue is "partially resolved": the out-of-band update repairs the devices that worked in ordinary stereo but failed in multichannel modes such as 8-channel or 3D audio, and the update's own release notes add that "there are other audio symptoms not resolved in this OOB update." As of September 15, 2026 the Code 10 and no-output symptoms are still open on Microsoft's dashboard, marked as mitigated rather than resolved, with the note that Microsoft "is working on a resolution." So install it — but do not conclude your headset is dead if it doesn't help. The good news on getting it: unlike a lot of out-of-band releases, this one is not catalog-only. Microsoft says it "downloads and installs automatically from Windows Update and Microsoft Update," so Settings > Windows Update > Check for updates is all it takes, and you can confirm it landed by pressing Windows + R, typing winver, and looking for build 26100.9457 or 26200.9457.

If you are in the group that is still silent, the honest advice is to wait rather than to buy. Free stopgaps: use the laptop's built-in speakers, the 3.5 mm headphone jack if the machine has one, a Bluetooth headset, or a different USB audio adapter — since Microsoft says the problem is limited to Class 1.0 devices, one that reports usbaudio2.sys under Driver Details is a way around it rather than a second thing to troubleshoot. You can also uninstall the September update from Settings > Windows Update > Update history > Uninstall updates, but treat that as a genuine last resort for a headset you need for work today: it strips out that month's security fixes, and Windows will simply offer the update again, so it is not a state to leave the machine in. Pausing updates for a few weeks is the less bad version of that. And if you are reading this some months after September 2026, check Microsoft's Windows release health page for your version before assuming any of this still applies — a full fix is expected, and once it ships the answer becomes the ordinary one: install the latest update.

A note on Bluetooth speakers and headsets

Bluetooth adds its own twist to "connected but no sound." The first thing to check is that the headset or speaker is actually connected to this PC and not to your phone — most only hold one connection at a time, so the computer falls back to a speaker that isn't playing. The second is audio "profiles": many Bluetooth headsets show up in Windows twice — a "Stereo" version (full-quality sound for video and music) and a "Hands-Free" or "Headset" version (lower-quality, for two-way call audio). If music sounds tinny or silent, open the output picker and choose the Stereo entry, not the Hands-Free one. If your Bluetooth device won't connect at all or keeps dropping, our guide to Bluetooth that won't pair on Windows 11 walks through it in detail.

On a Mac

The logic is the same on a Mac, just in different menus. The most common cause is again the wrong output: go to Apple menu > System Settings > Sound > Output and make sure the right device is selected — your Mac's built-in speakers, your headphones, or an external speaker — and that the "Output volume" slider near the bottom is up and "Mute" isn't ticked. If you've plugged into an external monitor or a dock, the Mac may have switched output to it, exactly like Windows does. Also check that the balance slider is centered, since a balance dragged fully to one side can sound like dead speakers.

If the right device is selected and it's still silent, quit the app you're testing and reopen it, then — as ever — restart the Mac, which clears most audio gremlins. And remember that plugging headphones into the jack or connecting AirPods reroutes sound automatically, so unplug or disconnect them if you want the built-in speakers back.

How we can help

If you've checked the volume and mute, picked the right output device, unmuted the app in the Volume Mixer, restarted the audio services, turned off enhancements, and rolled back or reinstalled the driver and you still hear nothing, that's a fine point to hand it off. We fix sound problems on laptops and desktops all the time: the wrong-device and per-app routing tangles that aren't obvious, drivers a Windows update mangled, the "no audio device installed" disappearing-driver case, and the occasional genuinely failed speaker, jack, or sound chip (where an inexpensive USB sound adapter or a pair of USB/Bluetooth speakers is a fast, cheap cure). We work with homes and small businesses across Southern California and the Coachella Valley, in person or by remote support, and we'll get your sound back — usually quickly, and without replacing anything that doesn't need it.