Windows 11 January Update Causes Critical Boot Failures

Windows 11 January Update Causes Critical Boot Failures: What You Need to Know

Windows 11 January Update Causes Critical Boot Failures: What You Need to Know

Microsoft confirms cascading update failure leaves commercial PCs unable to boot, with manual recovery the only option

Microsoft has confirmed a serious issue affecting Windows 11 systems following the January 2026 security update, with affected devices unable to boot and displaying critical error messages.

The problem, which primarily impacts commercial PCs, stems from a cascading failure involving two separate monthly updates.

The Problem: A Chain Reaction of Failed Updates

After installing the January 2026 Patch Tuesday cumulative update KB5074109 on Windows 11 versions 25H2 and 24H2, impacted systems failed to start and displayed a BSOD crash screen with a stop error of “UNMOUNTABLE_BOOT_VOLUME” code. However, Microsoft’s investigation revealed that the January update wasn’t the sole culprit.

Microsoft’s investigation found that devices affected by recent boot errors were previously unable to install the December 2025 security update, and when the failed update was rolled back, Windows was left in an unstable state or “improper state”. When these compromised systems attempted to install the January update, the unstable foundation completely collapsed, rendering the machines unable to boot.

“Recent investigations have determined this issue can occur on devices that failed to install the December 2025 security update and were left in an improper state after rolling back the update,” Microsoft stated in an updated advisory. “Attempting to install Windows updates while in this improper state could result in the device being unable to boot.”

Windows 11 January Update Causes Critical Boot Failures: What You Need to Know

Who Is Affected?

The issue specifically impacts:

Physical commercial PCs running Windows 11 versions 24H2 and 25H2
Systems that previously failed to install December 2025 security updates
Devices that experienced update rollbacks leaving them in an “improper state”

Notably, Microsoft says the issue is currently limited to physical devices, with no reports of virtual machines being impacted. Consumer devices appear to be largely unaffected, as Microsoft has already deployed a fix that would prevent additional devices from crashing, meaning consumers will now never run into this specific issue.

Microsoft’s Response: Preventative, Not Curative

Microsoft has acknowledged the problem but admits its current solution is limited. The company states it is “working on a partial resolution that will prevent additional devices from resulting in a no-boot scenario if they try to install an update while in this improper state.”

However, Microsoft makes clear that “this partial resolution will not prevent devices from getting into the improper state in the first place, nor will it repair devices that are already unable to boot.”

For systems already affected, there is no automatic recovery solution. Users must manually intervene to restore their systems.

How to Recover an Affected System

If your Windows 11 PC is stuck with the “UNMOUNTABLE_BOOT_VOLUME” error, you’ll need to access the Windows Recovery Environment (WinRE) and manually uninstall the problematic update. Here’s how:

Method 1: Force Entry into WinRE

Turn on your computer and force shutdown by holding the power button after the Windows logo appears
Repeat this process 3-4 times until the Windows Recovery Environment appears automatically
Select your user account and enter your password
Click “Continue” to access advanced options
Navigate to “Troubleshoot” > “Advanced Options” > “Uninstall Updates”
Select “Uninstall latest quality update”
Confirm with administrator credentials
Allow the system to complete the uninstallation

Method 2: Boot from Installation Media

If the forced restart method doesn’t work:

Create or use a Windows 11 installation USB drive
Boot your PC from the installation media
Select “Repair your computer” instead of installing
Navigate to “Troubleshoot” > “Advanced Options” > “Uninstall Updates”
Follow the same steps as Method 1

Special Note for BitLocker Users

KB5074109 has introduced a regression affecting boot on BitLocker-protected systems, where the recovery screen accepts the key but fails to mount the OS volume. For these systems, you’ll need to:

Boot into WinRE from external media
Open Command Prompt from Advanced Options
Run: manage-bde -unlock C: -RecoveryPassword <your key>
Run: manage-bde -protectors -disable C:
Attempt to uninstall KB5074109 using DISM commands

Preventing Reinstallation

After successfully uninstalling the update, it’s crucial to prevent Windows from automatically reinstalling it:

Open Settings > Windows Update
Click “Pause updates” and select a pause period (1-4 weeks)
Wait for Microsoft to release a fixed version before resuming updates

Additional Issues with KB5074109

The boot failure isn’t the only problem reported with this update. Other issues include:

Outlook freezing: Users with POP accounts or PST files on cloud storage experienced application hangs (addressed in emergency update KB5078127)
Remote Desktop failures: Credential prompt failures during Remote Desktop connections (addressed in KB5077744)
Sleep mode issues: S3 sleep mode not working properly on some systems
Application unresponsiveness: Various applications becoming unresponsive when accessing cloud storage
Legacy modem driver removal: Four legacy modem drivers deliberately removed, breaking compatibility for some telephony and POS systems

Microsoft’s Ongoing Investigation

Microsoft states it continues to investigate “why these devices are failing to install Windows updates or potentially getting into this improper state.” However, the company has not provided:

Specific numbers of affected systems
Detailed hardware configurations most at risk
A clear technical definition of what constitutes an “improper state”
Root cause analysis of the December update failures

This lack of transparency has frustrated IT administrators managing enterprise environments, as there is no proactive detection method to identify vulnerable machines before deploying the update.

What Should Users Do?

If your system is working normally:

Ensure you’re keeping regular backups
Monitor Microsoft’s release health dashboard for updates
Consider pausing updates for a few weeks until Microsoft releases comprehensive fixes

If your system won’t boot:

Follow the WinRE recovery steps outlined above
Document any error codes you encounter
Pause updates after recovery to prevent reinstallation

For IT administrators:

Delay deployment of KB5074109 on commercial systems until Microsoft provides detailed guidance
Check systems for failed December 2025 update installations
Prepare recovery procedures and bootable media for affected endpoints

The Bigger Picture

This incident highlights ongoing concerns about Windows update quality and testing procedures. Coming just weeks after Windows 10 reached end-of-support in October 2025, the issue has reignited debates about Microsoft’s update deployment strategy and whether the rush to patch security vulnerabilities is compromising deployment stability.

Microsoft has recently acknowledged user frustration with Windows 11 and committed to “improving system performance, reliability, and the overall experience of Windows.” The company faces significant challenges in rebuilding trust with users who have experienced multiple problematic updates over the past year.

For now, affected users must rely on manual recovery methods while Microsoft works on a more comprehensive solution. The company has not provided a timeline for when devices already in an “improper state” might receive an automatic fix.

For the latest updates on this issue, visit Microsoft’s Windows release health dashboard or check the official support documentation for KB5074109.