Windows 11 25H2 No Sound? The Speaker and Driver Fix List
Quick answer: The Windows 11 25H2 update has caused widespread audio problems — no sound, static, or the wrong output device selected — usually because it swapped your audio driver or reset the default output. Work the fixes in order and confirm each with the speaker test.
Check the output device and volume first
Updates often change the default playback device. Go to Settings, System, Sound, and make sure your speakers (not a disconnected HDMI display or headset) are selected under Output. Check the mute key and the app-level volume mixer too, since these are the fastest things to rule out.
Restart the audio service and run the troubleshooter
The built-in audio troubleshooter (Settings, System, Troubleshoot, Other troubleshooters) resets routing and the audio service automatically. If sound is frozen, restarting the "Windows Audio" service via services.msc revives it without a full reboot.
Fix the driver — the usual 25H2 culprit
If 25H2 replaced your working driver with a generic one, that alone can cause no sound or static. In Device Manager, under Sound, video and game controllers, you can Roll Back Driver (available for a short window after the update) or uninstall and restart for a clean reinstall. For laptops, the manufacturer's Realtek, Cirrus or Intel package usually behaves better than the generic one. A steady static — common after 25H2 — often clears once the correct driver is back.
Clear enhancements and sample-rate mismatches
In the speaker's Advanced properties, turn off audio enhancements and set a standard format like 24-bit, 48000 Hz — a mismatched rate or an aggressive enhancement can mute or distort output. Turning off "exclusive mode" stops one app from monopolizing the device.
Confirm the fix
Once sound returns, run the left/right sweep on the speaker test to be sure both channels work. Our guide on no sound from laptop speakers covers the hardware checks if software fixes don't do it.
Sources: MDN — Web Audio API · Microsoft — Fix sound problems in Windows
Frequently asked questions
Why did my sound stop working after a Windows update?
Updates often change the default playback device, so check that your speakers rather than a disconnected HDMI display or headset are selected under Output. If 25H2 replaced a working driver with a generic one, that alone can cause no sound or static.
How do I revive frozen audio without rebooting?
Restart the Windows Audio service via services.msc. The built-in audio troubleshooter also resets routing and the audio service automatically.
What causes steady static rather than silence?
Usually the wrong driver. On laptops the manufacturer's Realtek, Cirrus or Intel package behaves better than the generic one, and the static often clears once the correct driver is back.
Should I suspect the monthly cumulative update?
If sound broke immediately after one, yes — check Update history first. Rolling back the cumulative update is faster than a driver reinstall and tells you straight away whether the update is responsible.
Where 25H2 sits now, and what 26H2 changes
Windows 11 25H2 is no longer the newest branch. Version 26H1 shipped earlier in 2026 but is scoped to new hardware only — it is not offered as a feature update to existing PCs. Version 26H2 reached the Release Preview channel on 27 August 2026 as build 26300.9278 and is expected to reach general availability in October 2026.
For sound troubleshooting this matters in one practical way: the fixes below are written against the 25H2 audio stack, and 24H2 and 26H2 use the same Settings paths. If you are on 26H1 you are on a device-specific branch, so a driver your OEM has not yet published for that branch is a more likely cause than any of the software settings here.
The September 2026 cumulative update, KB5120998, is due on 8 September 2026 for both 25H2 and 24H2. If your sound broke immediately after a monthly update, check whether that KB is installed before you start reinstalling drivers — rolling back the cumulative update is faster than a driver reinstall and tells you straight away whether the update is responsible.