Microsoft‘s January 2026 security update for Windows 11, identified as KB5074109 and pushed on Patch Tuesday, has been tied to a wave of serious problems on physical PCs running versions 24H2 and 25H2, including black screens and “UNMOUNTABLE_BOOT_VOLUME” errors that leave machines unable to boot without manual intervention, prompting Microsoft to investigate the issue after receiving limited reports and to advise affected users to use recovery tools or uninstall the update while it works on a permanent fix.
Sources
https://www.theverge.com/news/869199/microsoft-windows-11-unmountable-boot-volume-issue-january-2026-update
https://www.windowscentral.com/microsoft/windows-11/how-to-fix-boot-issues-after-installing-the-january-2026-update-for-windows-11
https://www.tomshardware.com/software/windows/some-pcs-cant-boot-after-latest-windows-11-security-update-no-fix-in-sight-mostly-affects-24h2-and-25h2-versions
Key Takeaways
- The Windows 11 January 2026 security update KB5074109 has caused some physical PCs to display an “UNMOUNTABLE_BOOT_VOLUME” error and fail to boot, forcing users to rely on the Windows Recovery Environment to remove the update or perform repairs.
- Microsoft acknowledges the boot issue is under investigation and describes the number of reports as limited, but it has yet to provide a comprehensive fix, leaving IT admins and users to manage manual recovery steps while awaiting further updates.
- The boot failure problem adds to a broader pattern of instability tied to recent Windows 11 updates, which have already prompted emergency patches for other bugs but still left some machines at risk of startup failures and related disruptions.
In-Depth
The fallout from Microsoft’s January 2026 Windows 11 security update has escalated into a significant concern for businesses and individual PC users alike, especially those running the current 24H2 and 25H2 builds. The cumulative update, labeled KB5074109 and distributed as part of the monthly Patch Tuesday cycle, was intended to deliver routine security enhancements. Instead, on a subset of physical machines, it has caused a severe startup failure known as “UNMOUNTABLE_BOOT_VOLUME,” a stop code associated with inaccessible boot devices that typically halts the operating system before it can even load the login screen. This isn’t merely a cosmetic glitch; affected PCs show a black screen and refuse to boot into Windows, leaving users stuck at an error message and requiring a trip into the Windows Recovery Environment just to undo the update or attempt repairs.
Microsoft has acknowledged the issue publicly, describing it as affecting a “limited number” of devices and committing to investigate further, but for now customers are left with stops and starts as they grapple with the fallout. In a worst-case scenario, the only remedy for some users is to uninstall the update from WinRE, roll back changes, and then pause updates so that the problematic package does not reinstall automatically. For IT professionals managing larger fleets of computers, this situation has become an unwelcome distraction from routine security cycles, forcing manual intervention and adding operational overhead.
This problem didn’t occur in isolation. The entire January update cycle has drawn criticism for introducing multiple stability regressions, including issues that required out-of-band patches to fix broken cloud application interactions and other reliability concerns. Although emergency releases have addressed some of the less critical bugs, the core boot failure remains unresolved at the time of writing, leaving users to balance the need for applied security patches against the risk of being rendered unable to start their systems without technical workarounds.
For mainstream Windows users—especially those who rely on their devices for business or mission-critical applications—this episode underscores a broader issue with the reliability of Microsoft’s update process and testing regimen. When fundamental system updates cause machines to become unbootable on a widely deployed operating system like Windows 11, it highlights the tension between rapid security deployment and rigorous quality assurance. Until Microsoft delivers a comprehensive remedy that restores system integrity without compromising security, users and administrators alike will have to navigate a patchwork of temporary solutions while keeping a wary eye on future updates.