Microsoft has launched an urgent investigation into severe stability issues plaguing the January 2026 security update for Windows 11, following reports that the patch is causing critical boot failures on physical devices.

The update, identified as KB5074109, was intended to bring security enhancements to Windows 11 versions 25H2 and 24H2 but has instead triggered a wave of “UNMOUNTABLE_BOOT_VOLUME” errors that render affected systems unusable.

Critical Boot Failures Confirmed

The primary issue under investigation involves devices entering a boot loop or displaying a “Black Screen of Death” immediately after applying the January 13, 2026, Patch Tuesday update.

Affected users report seeing a stop code 0xED (UNMOUNTABLE_BOOT_VOLUME) accompanied by the message: “Your device ran into a problem and needs a restart.”.

Microsoft has acknowledged the problem, stating they have received “a limited number of reports” where devices cannot complete startup.

Notably, this regression appears to affect only physical hardware, with virtual machine environments currently showing no signs of the defect, Askwoody observed first.

For administrators and users struck by this bug, the operating system becomes inaccessible, requiring manual intervention via the Windows Recovery Environment (WinRE) to uninstall the faulty package.

While the boot failure represents the most severe regression, KB5074109 is also responsible for a broader array of system-breaking bugs. Reports confirm that users who successfully boot are encountering widespread stability problems, including total system lockups and graphics driver conflicts.

According to user documentation, the update has introduced significant regressions in the graphics stack, leading to freezes in GPU-intensive applications. Specific incidents have been recorded with BforArtists 5.0 (a Blender fork), where switching viewport shading modes causes the system to hang indefinitely without generating a blue screen.

These “silent” lockups are attributed to conflicts between the new kernel changes and existing DirectX/GPU drivers, with Nvidia and AMD systems also suffering from black screens where the Windows UI fails to render correctly.

The fallout from KB5074109 extends to enterprise connectivity and productivity apps. Microsoft confirmed that the update broke credential prompts for Azure Virtual Desktop (AVD) and Windows 365, preventing remote connections, a critical flaw that was subsequently patched via the out-of-band update KB5077744 on January 17.

Furthermore, Outlook Classic users have reported the application freezing on launch or failing to sync POP/SMTP accounts due to lingering processes.

Mitigation Strategy

For users experiencing the UNMOUNTABLE_BOOT_VOLUME error, the only current recourse is to enter WinRE and uninstall the latest quality update. For those with bootable but unstable systems, Microsoft and security experts recommend pausing updates or rolling back KB5074109 via:

Settings > Windows Update > Update history > Uninstall updates.

Enterprise administrators are advised to deploy Known Issue Rollback (KIR) policies where available, while consumers are urged to delay installation until Microsoft releases a comprehensive fix for version 25H2.

Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.

The post Microsoft Investigating Boot Failure Issues With Windows 11, version 25H2 Following January Update appeared first on Cyber Security News.