Microsoft has launched an urgent investigation into severe stability issues plaguing the January 2026 security update for Windows 11 after the patch triggered critical boot failures on physical devices.
The update, identified as KB5074109, was intended to deliver security enhancements to Windows 11 versions 25H2 and 24H2 but instead caused widespread “UNMOUNTABLE_BOOT_VOLUME” errors that render affected systems unusable.
Critical Boot Failures Confirmed
The primary issue involves devices entering boot loops or displaying a black screen immediately after applying the January 13, 2026, Patch Tuesday update.
Affected users encounter stop code 0xED (UNMOUNTABLE_BOOT_VOLUME) with the error message: “Your device ran into a problem and needs a restart.”
Microsoft acknowledged receiving “a limited number of reports” where devices cannot complete startup, though the actual scope appears broader than initially disclosed.
The regression affects only physical hardware, with virtual machines currently showing no signs of the defect.
For administrators and users impacted 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 introduced multiple system-breaking bugs affecting users who successfully boot their devices.
Reports confirm widespread stability problems, including total system lockups and graphics driver conflicts across both Nvidia and AMD platforms.
The update introduced significant regressions in the graphics stack, causing freezes in GPU-intensive applications.
BforArtists 5.0 (a Blender fork) users reported that switching viewport shading modes causes indefinite system hangs without generating error screens.
These “silent” lockups stem from conflicts between new kernel changes and existing DirectX/GPU drivers, with Windows UI failing to render correctly on affected systems.
The fallout extends beyond consumer devices to enterprise environments. Microsoft confirmed that KB5074109 broke credential prompts for Azure Virtual Desktop (AVD) and Windows 365, preventing remote connections, a critical flaw subsequently addressed through out-of-band update KB5077744 released on January 17.
Outlook Classic users also reported application freezes on launch or sync failures with POP/SMTP accounts due to lingering background processes.
For users experiencing UNMOUNTABLE_BOOT_VOLUME errors, the only current recourse is entering WinRE and uninstalling the latest quality update.
Those with bootable but unstable systems should pause updates or roll back KB5074109 via Settings > Windows Update > Update history > Uninstall updates.
Enterprise administrators should deploy Known Issue Rollback (KIR) policies where available, while consumers are advised to delay installation until Microsoft releases a comprehensive fix.
This incident highlights the critical importance of staged rollout strategies and thorough pre-release testing for major security updates affecting millions of devices worldwide.
Follow us on Google News , LinkedIn and X to Get More Instant Updates. Set Cyberpress as a Preferred Source in Google.
%20(1).webp?fit=1600,900&ssl=1&description=The update, identified as KB5074109, was intended to deliver security enhancements to Windows 11 versions 25H2 and 24H2){kind=link}