Microsoft has issued out-of-band emergency updates after its January 2026 security patch caused a string of serious problems for Windows users. In short: some machines couldn't shut down or hibernate, and a much wider set of systems experienced Remote Desktop sign-in failures. Microsoft shipped fixes over the weekend, but a few related issues remain under watch.
What broke and who was hit
The two headline problems were distinct but painful. The first—failure to shut down or enter hibernation—was narrow in scope: it affected devices still running Windows 11 version 23H2 that have Secure Launch enabled, and reports indicate the shutdown problem was largely limited to Enterprise and IoT editions of 23H2. Those devices could restart instead of powering off or hibernating after installing the January security update.
The second issue was broader. After installing the same January security update, some users found Remote Desktop connections failed during authentication. Microsoft says this affected multiple platforms, including newer Windows 11 releases and some Windows Server and extended-support Windows 10 builds—meaning businesses and remote workers were most exposed.
On top of those, Microsoft acknowledged an Outlook Classic problem affecting older POP account setups that can cause Outlook to hang in the background, interfering with clean shutdowns. Other user-reported glitches—like brief black screens before the desktop appears, desktop backgrounds resetting to black, and desktop.ini not behaving—have been reported but haven't all been formally acknowledged or patched yet.
The fixes Microsoft released
Microsoft released at least two out-of-band updates to address the most disruptive failures. The updates (identified by their KB numbers) aimed to restore Remote Desktop sign-ins and fix the shutdown/hibernate regression for affected 23H2 devices. These emergency patches have been made available through Windows Update and are also offered for manual download.
If you manage multiple machines—especially enterprise fleets or Windows Server instances—watch your update channels and deployment schedules closely. Out-of-band fixes are designed to move fast, but they can also complicate patch management if you had staged the January update across devices.
What you should do now
- Check Windows Update: Microsoft has pushed the emergency updates via Windows Update; install available security or OOB updates and reboot when prompted. The patches should restore normal Remote Desktop authentication and resolve shutdowns for affected 23H2 devices.
- Manual download: If your environment blocks automatic updates, consider obtaining the emergency packages for manual distribution from your usual enterprise update catalog or management tools.
- Be cautious with Outlook Classic: If you use legacy POP accounts and see Outlook freeze, avoid force-closing Outlook unless you’re comfortable with the potential risk to your local email database. Wait for Microsoft’s targeted fix or consult your mail backup before restarting the app.
- Monitor for follow-on issues: Some users are still reporting UI oddities and other residual glitches. If you see problems after applying the emergency patches, gather logs and escalate through your normal support channels—these reports help Microsoft triage lingering regressions.
Why this matters beyond the immediate fixes
Out-of-band updates used to be rare; increasingly they’re a part of the Windows update rhythm. When security updates introduce regressions that affect shutdown, authentication, or recovery, the impact is both technical and reputational. Businesses that rely on remote access and managed fleets are particularly sensitive to these hiccups—especially when variants of the bug touch servers, ESU-enabled Windows 10 builds, and multiple Windows 11 branches.
If you’ve been following how Windows updates have behaved over the last year, this is another data point in the conversation about update testing and release quality. For practical guidance on keeping a lean, manageable Windows 11 environment—especially on 25H2—see advice on decluttering Windows 11 25H2. And for a reminder of how disruptive a single update can be to enterprises, recall earlier incidents like the October patches that triggered BitLocker recovery prompts and caused a scramble for fixes documented in a previous report.
If you manage systems at scale, prioritize: confirm the emergency patches are applied to remote-access servers and endpoints used for critical work, and keep an eye on Microsoft’s health dashboard and support channels for any new advisories or follow-up fixes.
This story is unfolding—Microsoft moved quickly to patch the worst failures, but the ripple effects from rushed fixes and lingering bugs mean IT teams should stay alert for more updates in the coming days.