Microsoft January 2026 Windows Updates Trigger Remote Desktop Credential Failures and Secure Launch Shutdown Bug
Microsoft’s January 2026 Windows security updates introduced regressions that disrupted enterprise endpoints, including Remote Desktop authentication failures affecting access to Azure Virtual Desktop and Windows 365. After installing KB5074109 on specific Windows client builds (noted as Builds 26200.7623 and 26100.7623), users reported repeated credential prompt/sign-in failures in the Windows App, preventing successful remote session establishment; Microsoft acknowledged the issue and issued an out-of-band update intended to restore normal Remote Desktop connectivity.
Separately, Microsoft confirmed another January patch-related issue on Windows 11 23H2 where some systems with Secure Launch enabled may fail to shut down, restart, or hibernate, leaving devices running and potentially draining batteries. As a workaround, Microsoft advised forcing shutdown via the command:
shutdown /s /t 0
Microsoft indicated a permanent fix would be delivered in a future update, but did not provide scope/impact metrics for affected devices.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
5 events from the most recent confirmed update back to the earliest known activity.
Microsoft provides manual deployment and KIR mitigations for affected enterprises
Microsoft said the out-of-band fixes would not be delivered automatically through Windows Update and must be manually installed from the Microsoft Update Catalog. For organizations unable to deploy the emergency updates immediately, Microsoft also provided Known Issue Rollback packages via Group Policy to mitigate the remote desktop and Cloud PC connectivity issue.
Microsoft releases emergency fix KB5077744 for Remote Desktop sign-in failures
Microsoft issued a standalone out-of-band update, KB5077744, to remediate credential prompt loops and authentication failures in the Windows App that disrupted access to Azure Virtual Desktop and Windows 365 Cloud PCs after KB5074109. Microsoft told administrators to deploy the fix through the Update Catalog or enterprise management tools without uninstalling the January security update.
Microsoft releases OOB update KB5077797 for Windows 11 23H2
On January 17, Microsoft published an out-of-band update, KB5077797, to fix the Windows 11 23H2 shutdown/hibernate bug introduced by January Patch Tuesday. The same emergency update also addressed Remote Desktop credential prompt and sign-in failures affecting some remote connection scenarios.
Microsoft confirms Windows 11 23H2 shutdown and hibernation regression
Microsoft acknowledged that some Windows 11 23H2 devices, especially those with Secure Launch enabled, could fail to shut down, restart, or hibernate properly after the January updates. The company advised a command-line shutdown workaround while saying a future update would provide a fix.
Microsoft releases January 2026 Patch Tuesday security updates
Microsoft issued its January 2026 Patch Tuesday updates for supported Windows versions. After deployment, the updates were found to introduce regressions affecting shutdown/hibernate behavior on some Windows 11 23H2 systems and Remote Desktop-related sign-in flows.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
5 references tracked. Mallory keeps watching after this page renders.
Windows 11 shutdown bug forces Microsoft into damage control • The Register
go.theregister.com
Open sourceThe Patch After the Patch: Microsoft Issues Emergency Fix for Remote Desktop and Shutdown Bugs
securityonline.info
Open sourceMicrosoft releases OOB Windows updates to fix shutdown, Cloud PC bugs
bleepingcomputer.com
Open sourceMicrosoft January 2026 Security Update Causes Credential Prompt Failures in Remote Desktop Connections
cybersecuritynews.com
Open sourcePatch Tuesday update makes Windows PCs refuse to shut down • The Register
go.theregister.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


