Microsoft probes Windows 11 boot failures tied to January security updates

Some machines are failing to start after security updates, prompting yet another Microsoft investigation

Microsoft is investigating reports that its January 2026 security updates are leaving some Windows 11 machines stuck in a boot loop, adding another entry to this month's bumper post–Patch Tuesday borkage list.

The issue affects a "limited number" of physical Windows 11 devices that fail to start after installing the January security updates and later patches, instead showing an "UNMOUNTABLE_BOOT_VOLUME" stop code and a black screen offering little more than a restart prompt.

"Your device ran into a problem and needs a restart. You can restart," the message reads, according to a Microsoft advisory spotted by Ask Woody. At this stage, Microsoft says, the system cannot complete startup and needs manual recovery steps to get going again.

According to Redmond's own incident note, the problem 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. 

The first signs of trouble appeared in user forums, where people reported that machines which had been working fine suddenly wouldn't boot after the January updates were installed. Security-focused updates are supposed to be among the least exciting parts of Windows maintenance, but for those hit by the bug, they have resulted in downtime and hands-on repair work rather than a quiet reboot.

Microsoft says it has received only a small number of reports so far and is still trying to determine whether the failures are definitely caused by a regression introduced by the January updates. Customers experiencing the issue are being told to contact business support or submit reports through the Feedback Hub while the investigation continues. The company says it will update its documentation once more details are confirmed.

While this particular problem appears limited in scope, it lands in the middle of a rough January for Microsoft's update machinery. Earlier this month, Redmond was already dealing with fallout from a Secure Launch bug that could prevent systems from shutting down cleanly, separate Windows app credential failures that broke sign-ins for some users, and an Outlook issue that causes the app freeze when saving files to cloud storage services.

The boot failure issue is the latest reminder that January's patches have been unusually good at introducing new headaches alongside their promised security fixes. ®