Microsoft probes Windows 11 boot failures tied to January security updates
- Reference: 1769429588
- News link: https://www.theregister.co.uk/2026/01/26/microsoft_probes_windows_11_boot/
- Source link:
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 [1]Ask Woody . At this stage, Microsoft says, the system cannot complete startup and needs manual recovery steps to get going again.
[2]
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.
[3]
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.
[4]UK trade department put civil servants' feelings first during Windows 11 migration
[5]Notepad will now tell you all the ways Microsoft has enshittified it
[6]Microsoft admits Outlook might freeze when saving files to OneDrive
[7]Windows 11, not AI, kick-started the PC upgrade cycle
[8]Windows 11 shutdown bug forces Microsoft into out-of-band damage control
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 [9]fallout from a Secure Launch bug that could prevent systems from shutting down cleanly, separate [10]Windows app credential failures that broke sign-ins for some users, and an [11]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. ®
Get our [12]Tech Resources
[1] https://www.askwoody.com/forums/topic/reports-of-boot-failures-with-the-january-2026-security-update-and-later-updates/
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aXedyP2A38S0UGJNH_mUeAAAA1A&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aXedyP2A38S0UGJNH_mUeAAAA1A&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://www.theregister.com/2026/01/23/uk_dbt_windows_11/
[5] https://www.theregister.com/2026/01/22/microsoft_notepad_update/
[6] https://www.theregister.com/2026/01/21/outlook_freeze_onedrive/
[7] https://www.theregister.com/2026/01/20/windows_11_pc_refresh/
[8] https://www.theregister.com/2026/01/19/windows_11_shutdown_bug/
[9] https://www.theregister.com/2026/01/16/patch_tuesday_secure_launch_bug_no_shutdown/
[10] https://www.theregister.com/2026/01/15/windows_app_credential_failures/
[11] https://www.theregister.com/2026/01/21/outlook_freeze_onedrive/
[12] https://whitepapers.theregister.com/
25H2 here
Zero problems.
"Microsoft is investigating reports"
Hey, Borkzilla, here's an idea : how's about you take your "investigation team", rename them "Quality Assurance" and have them investigate before you fuck up again ?
Just a suggestion . . .
Re: "Microsoft is investigating reports"
"Investigating" = re-writing the Crapilot prompts to try to get a slightly different result.
Prognosis?
Microsoft's whimper of dying has become tediously prolonged.
Limited Number...
Well I suppose we can count ourselves lucky that it's not an unlimited number of reports...!
Update Borkage Trifecta
Might not boot. Might not work if running. Might not shutdown. M$ have got it all covered!
"Microsoft says it has received only a small number of reports so far"
Personally, and given that we are dealing with Microsoft here, I would be inclined not to take that "only a small number" at face value. I strongly suspect that they have been inundated with complaints and are trying to play down this matter.
It could easily be a small number if you round it off and ignore zeros (after all, they're nothing)...
No problem here - but my Win11 is the 25H2 ARM version running as a VM via Parallels on a Mac (and I only run Windows to install updates or when I need to check a feature to fix a problem for someone else).
I have a couple of Linux VMs (Ubuntu and Fedora - two that have ARM versions) - I have them to maintain a degree of familiarity as I occasionally install Linux on old PCs for those who don't need to update their hardware (it's only failing being that it's become too old for Windows). I even have a macOS VM to occasionally try out software.
I could probably use Linux as my base but macOS is easier to keep up to date and does everything I need of a PC...
Meh. We all know the solution to the MicroSlop problem, but when you're a multi-billion dollar sunk-cost fallacy business...
Those 30% of slopcode sure is showing its worth, isn't it?