Windows 11 Audio Not Working After KB5129195? Fix It

Last updated: October 31, 2026

Short answer: Your Windows 11 audio broke because the September 8 update broke audio on USB Audio Class 1.0 devices, and the September 14 emergency update KB5129195 fixed only the 8-channel and 3D audio symptoms. Work through the guide in order, starting with the troubleshooter, driver reinstall, and default playback check, as most users get sound back within the first three steps.

If your Windows 11 PC suddenly went silent — no sound from a USB audio device — and it started right after a Windows update in mid-September 2026, you are not imagining it. Microsoft has confirmed that the September 8, 2026 security update broke audio on some PCs with USB Audio Class 1.0 devices. The September 14 emergency update KB5129195 fixed only the 8-channel and 3D audio symptoms, and Microsoft still lists the remaining symptoms as an open known issue as of the October 13 update — but there are proven workarounds you can apply today.

This guide explains what happened and walks you through every fix, from the quickest check to the reliable rollback.

Update: October 28, 2026 — Microsoft's October 13 update (KB5127648) has arrived, but it does not fully fix this audio issue: Microsoft still lists "USB audio devices might fail to start or produce no sound" as a known issue, saying the September 14 out-of-band update (KB5129195) resolved only the 8-channel and 3D audio symptoms while the other symptoms remain under work. The audio problem itself began with the September 8 security update, not with KB5129195, and it is limited to USB Audio Class 1.0 devices — if your speakers, headphones, or Bluetooth audio fail, treat that as a separate driver problem. KB5127648 is still worth installing for its security fixes and other repairs, and switching an affected USB device to 2-channel stereo mode can restore sound in the multichannel cases. Microsoft's KB5127648 release notes

What Is KB5129195 and Why Did It Break Audio?

On 8 September 2026, Microsoft released the September Patch Tuesday update (KB5124008). It caused new problems of its own: Remote Desktop connections would fail after a few minutes, and host folder sharing stopped working in Linux virtual machines used by apps such as Claude Cowork and the Windows Subsystem for Linux.

Six days later, on 14 September 2026, Microsoft pushed an emergency out-of-band update — KB5129195 — to clean up that mess. It fixed the RDP and shared-folder issues, but introduced fresh ones:

• Broken audio on some PCs. Microsoft's September 8 update broke audio on USB Audio Class 1.0 devices; KB5129195 fixed only the multichannel (8-channel/3D) symptoms, and the October 13 update (KB5127648) still lists the remaining Code 10 / no-sound symptoms as an open known issue.
• Affected builds: Windows 11 25H2 (Build 26200.9457) and 24H2 (Build 26100.9457), both shipped via KB5129195. The audio issue itself is limited to USB Audio Class 1.0 devices.
• Related confirmed issues from the same updates include Code 10 errors on USB Audio Class 1.0 devices, domain-joined PCs losing their secure trust relationship (addressed by the September 22 update KB5124010), and black-screen/desktop-loading problems on some Azure Virtual Desktop hosts (fixed in the October 13 update).

In other words, the September 8 update introduced the audio issue, and the emergency patch that followed fixed only part of it — which is why confirming the exact update is always the first step. As we covered in our Pixel keyboard fix from this month's October update, it is not uncommon for a single update to fix one thing while breaking another — which is why confirming the exact update is always the first step.

Step 0: Confirm the Update Is Really the Cause

Before changing anything, check that KB5129195 is actually installed on your PC:

1. Press Windows key + R, type winver, and press Enter. Confirm you see 24H2 or 25H2.
2. Open Settings > System > About and check the build number: 26100.9457 (24H2) or 26200.9457 (25H2).
3. Open Device Manager (right-click Start > Device Manager), expand Sound, video and game controllers, and look for a yellow warning icon or a Code 10 error on your audio device.
4. Go to Settings > Windows Update > Update history and look for KB5129195.

If everything matches and the sound died right after the update, you have your culprit. If the update is not there, you likely have a different audio problem — skip to the driver step anyway, as it fixes most generic cases too. Recommended order first: the 2-channel stereo workaround + KB5127648 install come before any rollback.

How to Fix No Audio After KB5129195: Step by Step

Work through these in order. Most users get sound back within the first three steps.

Step 1: Run the Built-in Audio Troubleshooter

Windows has a troubleshooter that resets the audio pipeline automatically:

1. Open Settings > System > Sound.
2. Scroll to the Troubleshoot section and run the Output device troubleshooter (on some builds this is under Settings > System > Troubleshoot > Other troubleshooters > Audio).
3. Follow the prompts and apply any suggested fix, then test your audio.

This resolves the issue when the update only misconfigured the output device rather than the driver itself.

Step 2: Reinstall the Audio Driver

If the troubleshooter finds nothing, a corrupted or incompatible audio driver is the most common cause:

1. Right-click Start and open Device Manager.
2. Expand Sound, video and game controllers.
3. Right-click your audio device (e.g. Realtek, Intel Smart Sound) and select Uninstall device. Do not tick "Delete the driver software" unless you have the correct driver installer saved.
4. Restart your PC. Windows will reinstall a working driver automatically on boot.
5. Test the audio. If it works but sounds wrong, visit your PC or motherboard maker's support page and install the latest audio driver for your model.

This step can help when the driver itself is corrupted, but it does not fix Microsoft's documented USB Audio Class 1.0 known issue, which can persist with a correct driver.

Step 3: Check the Default Playback Device

After an update, Windows sometimes switches output to the wrong device (for example a monitor instead of your speakers):

1. Right-click the speaker icon in the taskbar and open Sound settings.
2. Under Choose your output device, select the correct speakers or headphones.
3. Run the Test under Format to confirm sound is flowing.

Step 4: Roll Back KB5129195

If the audio broke the same day the update installed and the steps above did not help, Uninstall KB5129195 only as last resort — may not undo fault that began Sept 8:

1. Open Settings > Windows Update > Update history > Uninstall updates.
2. Find KB5129195 (dated mid-September 2026) and select Uninstall.
3. Restart when prompted, then test your audio.

One caution: cumulative updates include security fixes, so rolling back leaves your PC without them until you reinstall a patched version. Treat the rollback as temporary: install the October 13 update (KB5127648) for its security fixes, but note it does not fully resolve the USB audio issue.

Step 5: Use System Restore

If the update does not appear in the uninstall list:

1. Press Windows key + R, type rstrui, and press Enter.
2. Pick a restore point dated before the September 8 update was installed.
3. Follow the wizard and let the PC restart.

Your files are preserved, but applications installed after that date will need reinstalling.

Step 6: Install the October 2026 Patch Tuesday Update

Install the October 13, 2026 update (KB5127648) regardless of whether sound is already back:

1. Open Settings > Windows Update and click Check for updates.
2. Install the October cumulative update and restart.
3. Confirm your audio still works afterwards.

This update restores the security patches lost by any rollback and fixes other issues (including AC-3 audio crashes and mouse stutter), but Microsoft still lists the USB Audio Class 1.0 problem as only partially resolved — if sound is still missing, try the 2-channel stereo workaround: in the Sound control panel, set the device's Default Format to a 2-channel option.

What NOT to Do

• Do not permanently disable your audio device or service to silence error messages — it masks the problem.
• Do not install "driver updater" tools from unfamiliar websites; get drivers only from your PC maker's site.
• Do not edit the registry based on random forum snippets. Nothing in this fix requires it.

Frequently Asked Questions

Why is there no sound after the Windows 11 September 2026 update?

The September 8, 2026 security update broke audio on USB Audio Class 1.0 devices on some PCs running Windows 11 24H2 (Build 26100.9457) or 25H2 (Build 26200.9457). Microsoft has acknowledged the issue; the September 14 update (KB5129195) fixed only multichannel symptoms, and the October 13 update still lists the remaining symptoms as an open known issue.

How do I know if KB5129195 caused my audio problem?

Check your build number (Settings > System > About) and your update history (Settings > Windows Update > Update history). If you have build 26100.9457 or 26200.9457, KB5129195 is installed, and the audio stopped working around mid-September 2026, KB5129195 builds confirm September patch line, but root cause was Sept 8 update; KB5129195 only partly fixed it.

Should I uninstall KB5129195 to fix the audio?

Yes, if the driver reinstall and troubleshooter did not work. Uninstall KB5129195 only as last resort — may not undo fault that began Sept 8. Just remember it is a temporary workaround — reinstall the October Patch Tuesday update when it arrives so you do not miss security fixes.

Will Microsoft fix the KB5129195 audio bug automatically?

Not yet, fully. Microsoft says it is working on the remaining USB Audio Class 1.0 symptoms and will update its documentation when more information is available. Keep Windows Update enabled and install KB5127648 for its other fixes.

Does 2-channel stereo restore sound?

Yes, in multichannel cases — via the Step 6 Default Format steps.

Are Bluetooth / built-in audio affected?

No — USB Audio Class 1.0 only; anything else is a separate driver problem.

Conclusion

This audio bug is confirmed by Microsoft but only partially fixed: KB5129195 resolved the multichannel symptoms and KB5127648 still lists the rest as an open known issue. Run the troubleshooter, reinstall your audio driver, try 2-channel stereo mode, and if all else fails, roll back the update — then install KB5127648 for its security fixes. Your speakers should be back in business.