Microsoft’s January 2026 Windows 11 security update KB5074109 is now facing fresh scrutiny after reports surfaced of a serious boot failure that can leave some PCs unable to start at all. The problem centers on the UNMOUNTABLE_BOOT_VOLUME blue screen error, a stop code typically tied to storage or file system access issues during startup. For affected users, the update doesn’t just cause glitches after logging in—it can prevent Windows 11 from reaching the sign-in screen entirely.
The reports point to Windows 11 systems running version 24H2 and 25H2 that installed the January 13, 2026 Patch Tuesday security updates based on KB5074109. In the cases being discussed, devices enter a blue screen loop with UNMOUNTABLE_BOOT_VOLUME and won’t boot normally, forcing recovery steps through the Windows Recovery Environment (WinRE) or external installation media.
Microsoft has acknowledged that it is investigating the boot failures. So far, the company describes the issue as affecting a limited number of devices, and there is no confirmed root cause or dedicated fix available yet. Public-facing update status communications have largely emphasized other high-profile problems connected to this update cycle, including Remote Desktop issues, black screens, and crashes involving cloud-based apps.
This new boot failure concern adds to what has already been a rocky Windows 11 update month. Alongside the UNMOUNTABLE_BOOT_VOLUME reports, users and administrators have been dealing with a mix of stability problems such as black screens and application crashes after installing KB5074109. There have also been complaints of Outlook Classic instability and file sync hangs involving services like OneDrive and Dropbox, serious enough to prompt emergency updates (KB5077744 and KB5078127). Even worse for some users, attempts to uninstall KB5074109 have reportedly failed with error 0x800f0905, creating a frustrating situation where the update causes problems but rolling back isn’t straightforward.
For anyone hit by the Windows 11 UNMOUNTABLE_BOOT_VOLUME boot loop after the January 2026 update, Microsoft’s current guidance aligns with standard Windows boot failure recovery. That generally means using WinRE to access repair tools, attempting file system repair, and if possible uninstalling the January security update from the recovery environment before Windows loads. In practical terms, users may need to boot into recovery options automatically triggered by repeated failed starts, or use Windows installation media to reach repair and uninstall features.
If your PC installed KB5074109 and is still starting normally, there’s no immediate reason to assume it will fail later, especially since Microsoft is currently labeling the reports as limited. Still, the appearance of a full boot-stopping issue highlights how fragile this month’s Windows 11 update situation has become. With emergency patches, reported rollback failures, and now boot errors, many IT admins and cautious home users may prefer to monitor Microsoft’s investigation closely and treat KB5074109 carefully until a more stable cumulative update arrives.
