Microsoft’s January 2026 Windows 11 security update, KB5074109, is now being investigated after reports linked it to a far more alarming problem than the usual post-update glitches: some PCs can fail to boot altogether. Instead of reaching the sign-in screen, affected systems may crash into a blue screen with the UNMOUNTABLE_BOOT_VOLUME error and get stuck in a restart loop.
The issue appears to impact Windows 11 devices running version 24H2 and 25H2 after installing the January 13 Patch Tuesday security updates tied to KB5074109. While early chatter focused on crashes and app instability, this newer symptom is more disruptive because it can prevent Windows from loading in the first place. In these cases, recovery typically requires launching the Windows Recovery Environment (WinRE) or using external installation or recovery media to regain access to the machine.
Microsoft has acknowledged the reports and says it is actively investigating, but the company has not yet shared a confirmed root cause or released a dedicated fix specifically for the UNMOUNTABLE_BOOT_VOLUME boot failure. Public status information has largely centered on other known problems connected to the January update cycle, including Remote Desktop issues, black screens, and crashes tied to cloud-based apps.
What’s making this situation more frustrating for some users and IT admins is that the boot failure reports are arriving on top of an already messy update rollout. KB5074109 has been associated with black screen behavior and application crashes, along with instability that affected Outlook Classic and caused hanging or freezing in sync tools such as OneDrive and Dropbox. Those problems were serious enough to prompt emergency updates, including KB5077744 and KB5078127. Adding to the pressure, some users have also reported that attempting to uninstall KB5074109 doesn’t always work, sometimes failing with error 0x800f0905—leaving people stuck between a problematic update and a rollback process that won’t complete.
For anyone hit by the UNMOUNTABLE_BOOT_VOLUME error after installing the January 2026 update, Microsoft’s current guidance aligns with standard Windows boot-repair steps. That generally means entering WinRE and using built-in recovery tools to repair the file system, attempt startup repair, or remove the most recent update from recovery before Windows fully loads. When the PC can’t reach WinRE on its own, users may need to boot from Windows installation media or a recovery drive to access the same troubleshooting options.
If your Windows 11 PC installed KB5074109 and is still starting normally, there’s no need to assume you’re automatically at risk. Microsoft’s wording suggests the boot failures are limited to a small number of devices. Still, this developing stop-code problem highlights how unstable the January 2026 Windows 11 update cycle has become. Between emergency patches, persistent black-screen complaints, app crashes, uninstall errors, and now reports of full boot failures, many users and administrators are likely to approach KB5074109 with extra caution until Microsoft delivers a more reliably stabilized cumulative update.
