Windows bugs and fixes October 17 2026: status
Chapters
What broke on Windows 11?
Windows Explorer failed after sign-in and could leave Windows 11 at a black screen, according to gHacks. Systems that installed updates released since August could show desktop loading failures and Windows Explorer crashes in application event logs for affected users, according to gHacks. Microsoft acknowledged the problem last month and said it mainly affected Azure Virtual Desktop hosts using FSLogix for user profile loading in virtual desktop environments, according to gHacks.
The Known Issue Rollback packages cover Windows 11 version 26H1, version 25H2 and version 24H2 on managed devices affected by the documented Explorer fault, according to gHacks. I would first match the symptom and environment. Check whether the screen turns black immediately after sign-in. Then check whether Windows Explorer fails to start or repeatedly crashes. A different black-screen pattern needs separate diagnosis.
I read the incident as one of Microsoft’s documented Windows known issues, not as proof that every black screen has the same cause. Release-health information can give the person at the keyboard a usable test and a published response. On a managed computer, follow the organization's approved change process without delaying the recording of symptoms and installed updates. It does not prevent the user from recording the Windows version, installed update and exact sign-in behaviour.
For the preceding status and progression of the Explorer fault, see my Windows bugs and fixes October 16 2026: status, published October 16 2026.
TL;DR
Windows 11 black screens after sign-in and Explorer crashes on systems updated since August were fixed by the cumulative updates, according to gHacks, published October 15, 2026. Remote Desktop failures on Windows 11 25H2 with Administrator Protection enabled still have no permanent fix, according to Finance Biggo, published October 15, 2026. I would install the latest cumulative update for the Explorer fault and use the Remote Desktop workaround only with a plan to restore the security setting.
- The Patch Tuesday cumulative updates contain the Explorer resolution, according to gHacks.
- KB5124006 and KB5124010 provide Known Issue Rollback options for managed devices, according to gHacks.
- The Remote Desktop failure affects Windows 11 25H2 with Administrator Protection enabled, according to Finance Biggo.
- Microsoft has not shipped a permanent Remote Desktop fix, according to Finance Biggo.
Has Microsoft shipped the black-screen fix?
The black-screen fix shipped on October 13, 2026, in KB5127648 for Windows 11 versions 24H2, 25H2 and 26H2, according to PCWorld, and in KB5127646 (OS Build 28000.3231) for Windows 11 version 26H1, according to Microsoft Support. The resolution is included in every update released after Patch Tuesday, and Microsoft recommends the latest update for each device because it contains other improvements, according to gHacks.
For managed devices, Microsoft provides KB5124006 Known Issue Rollback for Windows 11 version 26H1 and KB5124010 Known Issue Rollback for Windows 11 versions 25H2 and 24H2, according to gHacks. Administrators can deploy those packages as group policy when the cumulative update cannot be installed yet, according to the same detailed account from gHacks.
That Windows update fix replaces the manual Explorer launch as the durable response. I would check the installed update before repeating the workaround. If the latest cumulative update is present and the symptom continues, record the Windows version, update history and precise sign-in sequence. Do not assume the documented fault explains every black screen.
The distinction matters. Starting Explorer restores the desktop for one session. Installing the cumulative update removes the documented cause. A Known Issue Rollback gives a managed device another mitigation route. I would choose the cumulative update when it is available and approved, because it is the published resolution rather than a session-level recovery step.
Is the Remote Desktop failure fixed?
No permanent Remote Desktop fix has shipped for the October fault, according to Finance Biggo. Following the Windows Update distributed in October 2026, Remote Desktop connections can fail on Windows 11 25H2 when Administrator Protection is enabled, according to Finance Biggo.
Administrator Protection requires explicit user approval for tasks and is intended to protect against accidental configuration changes and malware tampering on affected systems, according to Finance Biggo. The feature is enabled by default on devices using Microsoft Security Compliance Toolkit, with enterprise-managed devices primarily affected by the documented fault, according to Finance Biggo.
Microsoft recommends temporarily disabling Administrator Protection until a resolution becomes available, but the change lowers the intended security baseline on affected devices during the workaround, according to Finance Biggo. I would make that trade-off explicit. Record who approved the change, why it was needed and when the setting must be restored. Do not attach an unsupported KB number to the current fault.
The earlier Remote Desktop failure received the out-of-band KB5129195 response, covered in my Emergency update KB5129195 fixes Remote Desktop but leaves Code 10 USB audio broken on Windows 11, published September 15 2026. The current October fault is believed to have a different cause from the previous Remote Desktop problem, according to Finance Biggo.
What can a Windows user do today?
Installing the latest cumulative update is Microsoft’s recommended path, according to gHacks. When the desktop does not load after sign-in, press Ctrl+Shift+Esc, select Run new task, enter explorer.exe, and select OK to start Windows Explorer manually, according to gHacks.
That action starts Explorer only for the current session and does not remove the cause, leaving the cumulative update as the actual fix, according to gHacks. The workaround therefore costs another manual launch whenever the desktop fails to load. I would use it only when the update must wait.
For Remote Desktop on Windows 11 25H2, Microsoft recommends temporarily disabling Administrator Protection until a permanent resolution becomes available for affected devices, according to Finance Biggo. The cost of that workaround is a lower intended security baseline until Administrator Protection is restored after the connection is established on the affected device, according to Finance Biggo. Ask the person responsible for the computer to approve the change. Re-enable the setting after the connection is established.
My order is simple. Check the Windows version and installed update. Install the current cumulative update for the Explorer fault. Use the session-only Explorer launch when updating must wait. For the Remote Desktop failure, use the temporary setting change only with approval and a written restoration step. Keep the two faults separate during diagnosis.