Windows bugs and fixes October 4 2026: current status
Chapters
TL;DR
USB audio, domain trust, desktop loading and AC-3 applications were listed as broken on Windows 11 26H2 on October 4, 2026, by Microsoft Learn. Microsoft has mitigated some failures, but the permanent black-screen fix has not shipped, according to gHacks on September 27, 2026.
- Microsoft Learn listed USB audio failures, lost domain trust, black screens and AC-3 application crashes on October 4, 2026.
- gHacks said on September 27, 2026, that Microsoft had not named the update containing the permanent black-screen fix.
- Techdows said on September 30, 2026, that out-of-band repairs shipped on September 14.
- Thepcenthusiast said on September 30, 2026, that Microsoft was distributing Windows 11 26H2 through a phased rollout.
What is broken on Windows 11 26H2?
Microsoft Learn listed Windows 11 26H2 problems on October 4, 2026.
Microsoft Learn's October 4, 2026 entry says USB audio devices can display Code 10 or fail in multichannel audio modes after the September 8 update. The same entry says Credential Guard protected machine accounts can lose their secure trust relationship with an on-premises Active Directory domain and reject valid domain credentials.
Microsoft Learn also says some virtual desktop environments can show a black screen or fail to load the desktop after sign-in, while applications using Windows built-in AC-3 decoding can close unexpectedly after KB5124010 and later updates. Games, media players and productivity applications can be affected, although Microsoft says many modern applications carry their own decoding components.
Those are the Windows known issues I would check before treating a help desk ticket as an unexplained failure. As of October 4, 2026, Microsoft Learn listed the USB audio, domain trust and desktop-loading entries as mitigated, but mitigation does not establish that a permanent repair has shipped.
Which Windows fixes have shipped?
Techdows said on September 30, 2026, that KB5129195, KB5129242 and KB5129194 shipped on September 14 as out-of-band fixes.
According to Techdows on September 30, 2026, those updates addressed Remote Desktop Services, Hyper-V Plan9 shares, multichannel USB audio and a power service vulnerability. Techdows also identifies KB5124010 as the optional non-security preview released on September 22 and KB5121794 as the Windows 11 26H2 enablement package released on September 29.
Those shipped updates matter, but they are not a Windows update fix for every open failure. Microsoft Learn still listed USB audio, domain trust, desktop loading and AC-3 decoding problems on October 4, 2026, and said the AC-3 resolution would arrive in a future Windows update.
I therefore separate installed repairs from open mitigations. The sequence in my previous Windows report provides continuity, while Microsoft Learn's October 4, 2026 status remains the controlling current record.
How can I recover from the black screen?
gHacks said on September 27, 2026, that Microsoft had mitigated the black-screen problem but had not shipped a permanent fix.
According to gHacks on September 27, 2026, the Windows 11 bug began with KB5120998 and affects versions 24H2, 25H2 and 26H1, primarily on Azure Virtual Desktop hosts using FSLogix profiles. Microsoft had observed the failure more often with some existing profiles, while Windows Server editions were not listed as affected.
For a personal PC, gHacks says the temporary workaround is to open Task Manager and start Windows Explorer manually. That restores the desktop session, but the cost is manual intervention whenever the failure returns because the underlying change remains unresolved.
For managed devices, gHacks names KB5124006 260924_20071 Known Issue Rollback for Windows 11 26H1 and KB5124010 260924_20021 Known Issue Rollback for versions 24H2 and 25H2. An administrator must install the applicable package, configure its Group Policy and restart the affected device, according to gHacks on September 27, 2026.
Should I install Windows 11 26H2 now?
Thepcenthusiast said on September 30, 2026, that Windows 11 26H2 began rolling out on September 29, 2026.
Thepcenthusiast's September 30, 2026 report says eligible Windows 11 24H2 and 25H2 computers receive version 26H2 as a lightweight enablement package because those versions share the same servicing branch and underlying system files. The prerequisite is KB5124010 from September 22, 2026, or a later cumulative update, and installation requires one restart.
The same report says Microsoft is using a phased rollout, so an eligible computer might not receive the offer immediately. I would not force the upgrade when Windows Update has not offered it, because Thepcenthusiast says there is little reason to bypass the phased release.
A computer running Windows 11 26H1 cannot upgrade directly to 26H2 because the versions use different Windows cores, according to Thepcenthusiast on September 30, 2026. Microsoft instead plans a path from 26H1 to a future Windows release, but the report does not name that release.
What can a Windows user do today?
Microsoft Learn's October 4, 2026 status means I would not treat mitigation as a completed repair.
If Windows Update has not offered Windows 11 26H2, I would leave the phased rollout alone because Thepcenthusiast said on September 30, 2026, that there was little reason to force it. If the desktop becomes black after sign-in, I would use Task Manager to start Windows Explorer, following the temporary method described by gHacks on September 27, 2026.
On a managed computer, I would send the exact Windows version to the IT provider so it can choose the applicable Known Issue Rollback package and accept the required restart described by gHacks on September 27, 2026. That route costs administrator time, a policy change and an interruption for the reboot, while the rollback lasts only until Microsoft ships a resolution.
If an older application closes while decoding AC-3 audio, I would avoid the affected feature or use an application with its own decoder, based on Microsoft Learn's October 4, 2026 explanation. That workaround costs access to the legacy application's affected audio feature, and Microsoft has not named the future update that will provide the permanent AC-3 repair.