Windows 11 January Update Nightmare: Boot Loops and Emergency Patch

Microsoft’s Windows 11 January 2026 security update (KB5074109) keeps on giving—and not in a good way. What started as a routine Patch Tuesday has morphed into a month‑long headache for users and IT admins, with new boot failure investigations, a second emergency out‑of‑band patch, and mounting evidence that this year’s update rollout is among Redmond’s messiest in recent memory.

Windows 11 January Update Problems Arise

The Windows 11 January Update problems first appeared shortly after the January 13, 2026 security update landed. Users reported broken shutdowns, Outlook freezes, File Explorer glitches, sleep mode failures, and Remote Desktop sign‑in problems—issues severe enough that Microsoft felt compelled to ship KB5077744, an emergency out‑of‑band update on January 17 specifically targeting the shutdown and Remote Desktop bugs.

But that emergency patch didn’t clean up the mess from the Windows 11 January update. Now Microsoft is investigating reports that its January updates are leaving some Windows 11 machines completely unbootable, trapping them in an infinite restart loop with the UNMOUNTABLE_BOOT_VOLUME stop error (0xED) and a black screen.

According to an advisory spotted by Ask Woody, affected “limited number” of physical Windows 11 devices fail to start after installing the January updates and later patches, instead displaying “Your device ran into a problem and needs a restart” over and over. At this stage, the system cannot complete startup and requires manual recovery steps to boot again.

The boot failure issue has been observed on Windows 11 versions 24H2 and 25H2, with no server editions affected and no reports of the same behavior on virtual machines so far. Only physical hardware appears vulnerable, which suggests something about how the January patch interacts with specific storage or firmware configurations might be triggering the corruption.

Microsoft says it has received only a “limited number of reports” but is actively investigating whether the failures are definitely caused by a regression introduced by the January updates. Those hit by the bug are being directed to contact business support or submit reports through the Feedback Hub while the investigation continues, which offers little immediate comfort when your PC simply won’t start.

This boot loop mess lands directly on top of an already rough January for Microsoft’s update machinery. Earlier this month, Redmond was already dealing with fallout from a Secure Launch bug that prevented systems from shutting down cleanly, separate Windows app credential failures that broke sign‑ins for some users, and the Outlook issue that causes the app to freeze when saving files to cloud storage services.

The Outlook cloud storage problem turned out to be broader than first thought. Microsoft initially believed it was limited to classic Outlook POP account profiles, but later acknowledged the bug was actually related to using cloud‑backed storage locations like OneDrive and Dropbox—and Outlook wasn’t the only affected application. Applications that open or save files stored in cloud‑backed locations could become unresponsive or display errors, including Outlook hanging when PST files are stored on OneDrive.

Second Windows 11 January Update 

That led to a second out‑of‑band update over the weekend—Microsoft dropped an emergency fix addressing the Outlook freezes and broken cloud storage issues in some applications after the January update. If you’re counting, that’s now two out‑of‑band updates in two weeks following the base security patch, which is a poor showing especially with another fortnight remaining before February’s Patch Tuesday arrives and potentially unearths more issues.

The Windows 11 Update problem is compounded by the fact that, as a Security Update, uninstalling KB5074109 while Microsoft addresses the bugs risks exposing systems to the vulnerabilities the patch was meant to fix. That leaves IT admins in a tough spot—leave the buggy update installed and deal with boot failures and app freezes, or roll it back and live with unpatched security holes until Microsoft ships a clean fix.

For those caught by the UNMOUNTABLE_BOOT_VOLUME boot loop, the only current recourse is booting into the Windows Recovery Environment (WinRE) and manually uninstalling the latest quality update from there. You’ll need your BitLocker recovery key handy if BitLocker is enabled, then locate the offline Windows installation, detect pending actions, and use DISM to remove the problematic KB.

Those with bootable but unstable systems should pause updates or roll back KB5074109 via Settings > Windows Update > Update history > Uninstall updates—but that rollback requires bootable access, which the unlucky users with boot failures don’t have.

KB5074109 is a mandatory security update that patches as many as a hundred known security issues, which explains why it shipped automatically to Windows 11 25H2/24H2 systems. You can check if you have it installed by going to Settings > System > About and looking at the build number—if it’s 26200.7623, you’ve got the January update installed.

The broader question now is what went wrong with Microsoft’s testing pipeline for the Windows 11 January Update. These Windows 11 January update patches ostensibly passed through the Insider ring validation process, yet managed to break boot processes, storage‑integrated apps, networked sign‑ins, PC shutdowns, and hibernation scenarios across physical devices—issues severe enough to require multiple emergency rollouts and unresolved investigations two weeks after Patch Tuesday.

For administrators fielding calls from users struggling with mysterious Outlook freezes, shutdown hangs, or worst‑case boot‑loop bricks, the message this Windows 11 January update is clear: pause automatic updates where you can, maintain good backups, keep recovery media handy, and watch Microsoft’s known issue documentation closely until Redmond confirms the boot failure investigation is closed and a comprehensive fix arrives.

The Windows 11 January update is shaping up to be a case study in patch management headaches exactly when Microsoft can least afford it—2026 was supposed to be the year Windows 11 settled into reliable, predictable updates, but the first Patch Tuesday of the year has delivered anything but.