Skip to content

WindowsPublished 4 min read

Windows bugs and fixes October 2 2026: status

Illustration for the article “Windows bugs and fixes October 2 2026: status”
Listen to this article · 7:30 · AI-generated narration
0:00 / 7:30
Chapters

Has the Windows 11 black-screen fix shipped?

Black screens remain mitigated, not fixed, according to gHacks on September 27, 2026.

The Windows 11 bug can leave a black screen after sign-in, prevent the desktop session from loading automatically and accompany Windows Explorer crashes, gHacks reported on September 27, 2026.

The problem began with August 2026 non-security preview update KB5120998 and continued through subsequent updates on Windows 11 versions 24H2, 25H2 and 26H1, according to gHacks on September 27, 2026.

Microsoft opened the known issue on September 24 and said it had primarily appeared on Azure Virtual Desktop hosts using FSLogix, especially with some existing user profiles, gHacks reported on September 27, 2026.

Microsoft marked the issue as mitigated but had not named a permanent correction, release date or future update that would contain one, according to gHacks on September 27, 2026. Mitigated therefore does not mean resolved.

TL;DR

Windows 11 desktops could fail to load after sign-in following August 2026 preview update KB5120998, gHacks reported on September 27, 2026. No permanent Windows update fix has shipped; Microsoft has mitigated the problem and provided manual recovery and Known Issue Rollback options, according to gHacks on September 27, 2026. Windows 11 version 26H2 also carries black-screen, domain-trust and USB Audio Class 1.0 issues, Microsoft Learn documented on September 29, 2026.

  • The black-screen problem affects Windows 11 versions 24H2, 25H2 and 26H1, gHacks reported on September 27, 2026.
  • Microsoft has not named the update or date for a permanent black-screen fix, gHacks reported on September 27, 2026.
  • Windows 11 version 26H2 has three carried-over known issues rather than three newly caused problems, PCWorld explained on September 30, 2026.
  • Reported KB5124010 game crashes have an uninstall workaround but no confirmed cause, TweakTown reported on September 25, 2026.

Which problems carried into Windows 11 26H2?

Windows 11 version 26H2 carries three known issues, PCWorld said on September 30, 2026.

The Windows known issues are USB Audio Class 1.0 devices failing with Code 10 or in multichannel audio modes, domain trust failures involving Credential Guard, and black screens after sign-in, Microsoft Learn listed on September 29, 2026.

PCWorld explained on September 30, 2026 that Windows 11 version 26H2 did not cause the carried-over problems, because Windows 11 versions 24H2 and 25H2 show the same issues on their release-health pages.

Microsoft Learn said on September 29, 2026 that previously cached credentials might still permit offline sign-in when a Credential Guard protected machine account loses its secure channel with an on-premises Active Directory domain.

Windows 11 version 26H2 reached general availability through a phased rollout, Elevenforum reported on September 29, 2026. BleepingComputer reported on September 30, 2026 that Windows 11 version 26H1 cannot upgrade directly to 26H2 because the releases use different Windows cores.

Is KB5124010 crashing games?

KB5124010 has reported game crashes but no confirmed cause, TweakTown said on September 25, 2026.

User reports named Battlefield 6, WARDOGS, Battlefield 2042 and Fallout New Vegas among the affected games after the Windows 11 preview update, according to TweakTown on September 25, 2026.

The reports associated the failures with games containing anti-cheat support, but TweakTown said on September 25, 2026 that anti-cheat had not been fully confirmed as the cause.

Several affected users reportedly stopped the crashes by uninstalling KB5124010, according to TweakTown on September 25, 2026, but that workaround removes the complete preview update rather than isolating the suspected change.

I would treat the KB5124010 crashes as a reported problem, not a Microsoft-confirmed known issue, because TweakTown described user complaints and an unconfirmed cause on September 25, 2026. No named replacement KB or shipped game-crash fix appears in that report.

What can you do today?

Personal-PC users can start Windows Explorer manually, gHacks said on September 27, 2026.

That manual recovery is temporary rather than a permanent correction, while Microsoft continues developing a resolution for a future Windows update without a named release date, according to gHacks on September 27, 2026.

Administrators can install and configure KB5124006 260924_20071 Known Issue Rollback for Windows 11 version 26H1 or KB5124010 260924_20021 Known Issue Rollback for versions 24H2 and 25H2, gHacks reported on September 27, 2026. A restart is required, and the rollback disables the responsible change only until a resolution ships.

If KB5124010 coincides with game crashes, uninstalling the preview update reportedly helped several users, but the cost is losing the entire preview update while the cause remains unconfirmed, TweakTown reported on September 25, 2026.

If Windows 11 version 26H2 is not installed and avoiding the carried-over issues matters more than receiving it immediately, PCWorld recommended waiting for Microsoft to report fixes on September 30, 2026. On a managed device, I would ask IT to apply the matching rollback policy rather than merely wait for its normal schedule.

For the preceding daily status, see my Windows bugs and fixes October 1 2026.

All articles