- Status: Confirmed. Microsoft has acknowledged that its Windows 11 emergency update (KB5129195) still breaks audio on some PCs, with a possible fix arriving at the October 2026 Patch Tuesday (scheduled October 13).
- Affected builds: Windows 11 25H2 at Build 26200.9457 and 24H2 at Build 26100.9457, both shipped via KB5129195.
- Related issues: Domain-joined PCs losing their secure trust relationship; AMD Radeon GPU driver timeouts, black screens, and freezes.
- KB/error codes: KB5129195; Code 10 (“This device can’t start”) in Device Manager.
Microsoft’s Windows 11 emergency update was supposed to clean up the mess left by the September 2026 update. Instead, it’s leaving new bugs in its wake, and audio is still breaking on some machines. According to Windows Latest, a fix may not land until October.
The situation is awkward: the patch that was meant to fix the September update’s problems is now itself the source of a problem. Microsoft has confirmed that KB5129195, the out-of-band emergency update released on September 14, still breaks audio on some PCs. And the company says a proper fix may not arrive until the October 2026 Patch Tuesday, scheduled for October 13.
The audio bug the Windows 11 emergency update couldn’t fix
Here’s the timeline. On September 8, Microsoft shipped the September 2026 Patch Tuesday update (KB5124008). It broke Remote Desktop connections and cut off host folder shares in Linux virtual machines used by apps like Claude Cowork. Six days later, on September 14, Microsoft rolled out KB5129195 — an emergency (out-of-band) update. It’s cumulative, so it bundles changes from previous updates too. It advances Windows 11 25H2 to Build 26200.9457 and 24H2 to Build 26100.9457. You can check your build in Settings > System > About.
That patch fully resolved the RDP and Claude Cowork issues. But it hasn’t fixed audio. Microsoft’s updated support documentation now lists two audio bugs. The first shows “no audio output” and throws “This device can’t start (Code 10)” in Device Manager. The second is stranger: the volume stays stuck at zero, and toggling it does nothing — audio is entirely unresponsive.
In its investigation, Microsoft concluded that only USB audio devices are affected. But Windows Latest is seeing reports from more users than that, which raises doubts about how narrow the culprit actually is.
The domain trust bug hitting enterprise PCs
The audio bug is the consumer-facing headline, but there’s a second problem that could hit workplaces harder. Based on reports seen by Windows Latest, domain-joined PCs are losing their secure trust relationship with the domain. That breaks login using your usual workplace credentials — the exact scenario IT admins dread.
Microsoft hasn’t said how many users are affected, but it has quietly updated its support documentation to confirm both bugs. The entry for KB5129195 (Windows 11 24H2/25H2 Security Update) now names these issues that the update was supposed to address. For most home users, this is a secondary concern; for anyone on a managed fleet, it’s a real outage.
AMD GPU errors left unfixed
There’s a third problem that Microsoft hasn’t patched at all. We’re tracking reports of GPU issues on AMD PCs after the September update. Users have seen driver timeouts, black screens, missing displays, and system freezes — sometimes even while not playing games.
The affected hardware spans multiple Radeon cards: the RX 6600, RX 7700 XT, RX 7800 XT, RX 7900 GRE, RX 7900 XTX, and RX 9070 XT. So it isn’t limited to a single model. Some users told Windows Latest that rolling back to older GPU drivers didn’t help, but removing the September update appeared to fix things. That makes Windows Update a prime suspect, though the exact cause is still unclear.
The frustrating part: KB5129195 doesn’t list a fix for these GPU errors. So AMD gamers are stuck between a September update that broke their graphics and an emergency patch that skipped the problem entirely.
What This Means for You
For most consumers, the risk is intermittent audio loss. If you’re on a USB audio device and installed this month’s emergency update, you could end up with no working audio — regardless of which update you run. But there’s a wrinkle: Microsoft notes that Windows 11 features roll out gradually, so even if you haven’t hit the audio bug yet, there’s no guarantee you won’t in the coming days or weeks. The issue may be tied to one of the improvements shipped in the September updates, and it could activate later.
For enterprise users, the stakes are higher. A lost domain trust relationship locks you out of your own machine with your own credentials until the fix arrives. And AMD GPU owners have no clean solution yet — older drivers don’t help, and removing the September update is the only reported workaround.
How to Get It and What to Do
Right now, there’s no clean workaround. Microsoft says it’s looking into the root cause and will share more details when it can. If you haven’t updated yet, you can delay — but Microsoft’s been clear that the September update’s fixes were important, so waiting to see if audio breaks is a gamble.
If you’re already affected, check your build in Settings > System > About to confirm whether you’re on Build 26200.9457 (25H2) or 26100.9457 (24H2). Keep an eye on the Windows Release Health status page for updates, and watch Microsoft’s support documentation for the KB5129195 entry as it’s revised. For IT admins managing a fleet, monitor for domain trust failures and Code 10 errors in Device Manager before the issue spreads further.
The fix is slated for October 13. Until then, this is a case of a patch that fixed one thing and broke another.
Source: Windows Latest
Build details:
- kb5124008
- kb5129195
Over to you: If you’re on a USB audio device, will you hold off for the October fix, or accept the risk and keep updating?
