Windows bugs and fixes October 20 2026: what shipped
Chapters
TL;DR
Windows 11 black screens after sign-in and Explorer crashes followed updates released since August; gHacks, published October 15, 2026, says the October 13 cumulative updates fixed them. BleepingComputer, published October 14, says KB5127648 and KB5127646 fixed the Always On VPN connection failure. The permanent Remote Desktop fix has not shipped; Cyber Press, published October 15, 2026, says temporarily disabling Administrator protection restores connectivity.
- gHacks recommends installing the latest update to resolve the black screen and Explorer crashes.
- BleepingComputer says a single SSTP or IKEv2 protocol is the temporary VPN workaround.
- Cyber Press says the Remote Desktop failure still lacks a permanent fix.
- I recommend checking the installed KB before changing any security policy.
Has the black-screen fix shipped?
The black-screen and Explorer-crash fix has shipped in the cumulative updates released on October 13, according to gHacks. The Windows 11 bug could leave an affected user at a black screen after sign-in or prevent the desktop from loading automatically. That gHacks report says Windows Explorer could also crash, with failures appearing in the application event logs.
Cyber Press, already cited, identifies KB5127646 or a later Windows update as the resolution for affected systems running Windows 11 version 26H1 after the desktop loading failure occurs. That account says devices with the update installed no longer need the manual workaround. I would install the latest available cumulative update rather than rely on starting Explorer for every session.
A separate account from PCWorld, published October 16, identifies KB5127648 as the fix available for Windows 11 24H2, 25H2, and 26H2. PCWorld attributes the failure to Windows Explorer in multi-user environments such as Azure Virtual Desktop and FSLogix. The Windows update fix therefore depends on the Windows 11 version installed.
Is Always On VPN working again?
Always On VPN is fixed by KB5127648 and KB5127646, BleepingComputer says. The problem followed the September 2026 Windows 11 security updates and affected automatic protocol selection or protocol fallback on Windows 11 24H2 and later. That BleepingComputer report says a connection could remain stuck in a Connecting state or fail after its initial attempt failed.
The affected connection could also show the error "The specified port is already in use," according to TechRadar, published October 15. That TechRadar account also identifies KB5127646 and KB5127648 as the cumulative updates addressing the failure.
If the cumulative update cannot be installed yet, BleepingComputer says an administrator can change the Always On VPN profile from automatic selection to SSTP only or IKEv2 only. The cost is losing automatic protocol selection and fallback while that workaround remains configured. I recommend recording the original profile setting before making the change.
Which Windows problem remains unfixed?
The permanent Remote Desktop fix has not shipped, Cyber Press says. The failure affects non-administrator users connecting to Remote Desktop hosts when Administrator protection is enabled. That Cyber Press account lists Windows 11 versions 24H2, 25H2, 26H1, and 26H2 as affected and lists no Windows Server platforms.
Cyber Press says the temporary mitigation is to reset the User Account Control Type of Admin Approval Mode policy through Microsoft Intune or Group Policy. That policy change disables Administrator protection through the organization's existing management tools. The cost is clear: Administrator protection is unavailable while the mitigation remains active.
I would not make that security change merely because Remote Desktop is slow or unavailable. I would first confirm the Windows version, the installed update, the user's administrator status, and whether Administrator protection is enabled. If those details match the documented issue, apply the temporary policy change and record it for reversal when Microsoft publishes the permanent fix.
What do the published known issues establish?
Microsoft's public release information gives a person at the keyboard enough detail to identify the documented failures and choose a supported response. Windows known issues are not limited to private help-desk information. They carry affected versions, symptoms, mitigations, and shipped fixes through release health and KB articles.
Computerworld says Microsoft's mitigation is to turn off Administrator protection temporarily. Computerworld, published October 16, also says the Remote Desktop issue began with September's non-security preview update. That Computerworld account says a permanent fix will follow in a future update.
I read the two current outcomes differently. The black-screen and VPN cases now have named cumulative updates, so waiting adds no documented benefit for an affected device. Remote Desktop still requires a trade-off because its workaround disables a security feature. For continuity with the previous day, see my Windows bugs and fixes October 19 2026: status.
What can you do today?
Install the latest cumulative update on a device affected by black screens, Explorer crashes, or the Always On VPN failure. gHacks recommends installing the latest update for each affected device. I would open Settings, select Windows Update, check for updates, install the offered cumulative update, and then verify the installed KB in update history.
If the desktop does not load before the update can be installed, use the temporary procedure documented by gHacks. Press Ctrl+Shift+Esc to open Task Manager. Select Run new task, enter explorer.exe, and select OK. That gHacks procedure starts Windows Explorer only for the current session and does not remove the underlying cause.
For an Always On VPN device that cannot be updated, ask the administrator to select SSTP only or IKEv2 only, as BleepingComputer advises. Restore automatic protocol selection after the corrective cumulative update is installed. For the Remote Desktop failure, do not disable Administrator protection without confirming the documented conditions. The permanent fix has not shipped, so record every temporary policy change for later reversal.
Frequently asked questions
Which update fixes the Windows 11 black screen?
Cyber Press identifies KB5127646 or a later Windows update for Windows 11 version 26H1. PCWorld identifies KB5127648 for Windows 11 24H2, 25H2, and 26H2. I recommend matching the KB to the installed Windows version.
Can I recover the desktop without installing the update?
Yes, but only temporarily. gHacks says to open Task Manager with Ctrl+Shift+Esc, select Run new task, enter explorer.exe, and select OK. The procedure restores Explorer for the current session but does not fix the cause.
Does Remote Desktop have a permanent fix?
No. Cyber Press says the permanent fix has not shipped. The documented mitigation disables Administrator protection through Microsoft Intune or Group Policy, which removes that protection until the policy is restored.
What should I do if Always On VPN cannot be updated?
BleepingComputer says to change the Always On VPN profile from automatic protocol selection to SSTP only or IKEv2 only. The workaround sacrifices automatic protocol selection and fallback until KB5127648 or KB5127646 can be installed.