Windows bugs and fixes September 19 2026: update

What broke after the September security updates?

KB5124008 and KB5124012 broke USB Audio Class 1.0 devices on Windows 11 version 24H2 or later, BleepingComputer reported September 14, 2026.

BleepingComputer reported on September 14, 2026, that affected PCs could show “This device cannot start (Code 10),” no audio output, unresponsive volume controls or unavailable sound settings after the September 8, 2026 security update.

Some devices continued working in standard stereo but failed in 8-channel or 3D audio modes, while users sometimes restored sound by selecting 2-channel mode, according to BleepingComputer on September 14, 2026.

The same update cycle destabilized Remote Desktop Services, causing connection and sign-in failures while Microsoft Management Console, RDS Licensing Diagnoser, File Explorer and Windows Update could stop responding, TechSpot reported September 15, 2026. That cluster matters because a Windows 11 bug can look unrelated when audio, remote access and management tools fail on the same updated PC.

Which Windows update fixes have shipped?

KB5129195 shipped for Windows 11 24H2 and 25H2 on September 14, 2026, NeoTeo reported September 16, 2026.

Windows 11 26H1 received the separate KB5129194 package on September 14, 2026, so NeoTeo’s September 16, 2026 account says to check the installed Windows version before choosing a package.

NeoTeo reported on September 16, 2026, that the packages resolved Remote Desktop Services instability and the Hyper-V Plan 9 failure that denied Linux virtual machines access to folders shared from the Windows host.

The Windows update fix also restored 8-channel and 3D operation for USB devices that still worked in stereo, but TechSpot reported on September 15, 2026, that devices failing to start or produce any sound were not fully repaired. The September 15 report on KB5129195 covers the same split between shipped repairs and the remaining Code 10 failure described by TechSpot on September 15, 2026.

What remains unresolved on September 19, 2026?

AMD Radeon crashes remained unresolved, TechSpot reported September 15, 2026.

TechSpot reported on September 15, 2026, that complaints included driver timeouts, black screens, displays dropping out and complete system freezes across several Radeon generations, although not every Radeon PC was affected.

USB Audio Class 1.0 devices that failed to start, produced no output or left volume controls at zero also remained under investigation after the multichannel repair, NeoTeo reported September 16, 2026.

Cybersecuritynews reported on September 17, 2026, that Microsoft was investigating KB5124008 domain-trust failures apparently connected with Machine Identity Isolation, while the root cause remained unconfirmed and no official workaround had been published. The same report said the emergency packages did not list domain-trust failures among their known issues, so I would not describe that Windows KB update problem as fixed.

At publication on September 14, 2026, PCWorld said no known workaround existed for affected USB Audio Class 1.0 devices that could not start at all.

How can you identify the failure?

Code 10 identifies the USB startup failure, BleepingComputer reported September 14, 2026.

If Stereo works while 8-channel or 3D mode fails, NeoTeo’s September 16, 2026 account places the PC in the narrower multichannel case addressed by KB5129195 or KB5129194.

If Remote Desktop connections or sign-ins fail while Microsoft Management Console, RDS Licensing Diagnoser, File Explorer or Windows Update becomes unresponsive, TechSpot’s September 15, 2026 account matches the Remote Desktop Services regression repaired by the emergency update.

For the separate domain case, Cybersecuritynews reported on September 17, 2026, that affected users received “The user name or password is incorrect” despite valid credentials, while cached sign-in could work with the PC offline. Cybersecuritynews also reported on September 17, 2026, that Test-ComputerSecureChannel returned False and nltest /sc_query: returned ERROR_NO_TRUST_LSA_SECRET, error 1786, in the detailed administrator report.

What can a person at the keyboard do today?

Package choice depends on the Windows version, NeoTeo reported September 16, 2026.

I would open Windows Update and install KB5129195 on Windows 11 24H2 or 25H2, or KB5129194 on Windows 11 26H1, because NeoTeo reported on September 16, 2026, that Microsoft distributes both emergency packages through Windows Update.

If an affected USB device works in standard stereo but fails in a multichannel mode, I would switch it to Stereo because ZDNET reported on September 14, 2026, that the change can restore audio temporarily. The cost is losing the device’s multichannel, 8-channel or 3D output until a complete repair ships, as ZDNET and NeoTeo described on September 14 and September 16, 2026.

If Device Manager shows Code 10 or the device produces no sound in any mode, I would not call KB5129195 a complete fix because PCWorld reported no known workaround on September 14, 2026, and NeoTeo said the symptom remained under investigation on September 16, 2026.

I would not remove the September update casually because Windows Latest, published September 15, 2026, said KB5129195 is mandatory, cumulative and includes additional security protection. For a domain-trust failure, I would involve a local administrator because Cybersecuritynews reported on September 17, 2026, that recovery may require local administrator access.