Windows 11 Boot Failure: Fix Black Screens After Jan 2026 Update

Microsoft confirms KB5074109 is causing boot loops and crashes. Here is how to diagnose the "Improper State" error and recover your PC safely.

---

Hook & Who This Is For (Intro)

If you recently installed the January 2026 security update for Windows 11 and your PC is now stuck on a black screen or failing to boot, you are not alone ^[4][8]. Microsoft has confirmed that a specific update, identified as KB5074109, is causing boot failures on a limited number of devices ^[4][9]. Affected systems often display the error code UNMOUNTABLE_BOOT_VOLUME or simply refuse to start up, requiring manual intervention to recover ^[4][7].

This issue primarily impacts users running Windows 11 versions 24H2 and 25H2 on physical PCs ^[4][10]. While security updates are typically routine, this particular patch has disrupted workflows by rendering some machines unbootable shortly after installation ^[10].

This article is for you if:

• Your PC failed to boot after installing the January 2026 Windows 11 update ^[4].
• You are seeing a black screen of death (BSOD) or an UNMOUNTABLE_BOOT_VOLUME error ^[4][7].
• You want to understand why this is happening and review the manual recovery steps recommended by Microsoft ^[9][12].

This article is NOT for you if:

• You are running Windows 10 or older operating systems, as this issue is specific to Windows 11 24H2/25H2 ^[4].
• You are using a virtual machine (VM) or a Windows Server edition, which Microsoft reports are currently unaffected by this specific bug ^[10].

TL;DR / What This Means for You

• Secure Boot Changes: The January 2026 update (KB5074109) updates the Secure Boot signature database. It replaces the 2011 signed boot loader with a 2023 version ^[3]. If you reset the database or toggle Secure Boot settings improperly, this can trigger a "Secure Boot violation," preventing the device from booting ^[3][4].
• Out-of-Band Fixes: Microsoft released an out-of-band update (KB5077744) on January 17, 2026, to address specific issues, including Remote Desktop sign-in failures caused by the initial security patch ^[6].
• WDS & Deployment Impact: For IT administrators using Windows Deployment Services (WDS), insecure "hands-free" workflows are being phased out. Unattended imaging patterns may fail if they rely on legacy behaviors ^[2].
• Recommended Action: Before applying these updates, review Microsoft's hardening guidance for Secure Boot and deployment ^[1][2]. If you encounter boot violations, you may need to create Secure Boot recovery media ^[3].
• Risk Note: Resetting the Secure Boot database without preparation can render a device unbootable until recovery media is applied ^[3][4]. Ensure backups are current before updating.

Background / Basics

Before diving into fixes, it is helpful to understand what is happening under the hood of your operating system. This section clarifies the terminology and the specific updates causing these widespread problems.

The Affected Updates

The core of the issue lies with the January 2026 security update for Windows 11. Specifically, this involves the update identified as KB5074109 ^[1][8][9]. This patch was released on January 13, 2026, as part of Microsoft's regular "Patch Tuesday" cycle, intended to fix security vulnerabilities and bugs ^[1][14].

Reports indicate the problem primarily affects Windows 11 versions 24H2 and 25H2 ^[5][6]. It is important to note that these issues have been observed on physical PCs, while virtual machines and Server editions appear largely unaffected at this stage ^[5][14].

Key Technical Terms

To help you navigate the situation, here are a few terms you might encounter:

• Boot Loop / Boot Failure: This occurs when the computer turns on but cannot successfully load the Windows operating system. It may restart repeatedly or get stuck on a specific screen.
• BSOD (Blue Screen of Death): A crash screen displayed by Windows when it encounters a critical system error. In this specific incident, users are frequently seeing a Stop Code: UNMOUNTABLE_BOOT_VOLUME (Error 0xED) ^[8][9][14].
• Secure Boot: A security standard that ensures a device boots using only software that is trusted by the Original Equipment Manufacturer (OEM). Recent updates have made changes to the Secure Boot database, replacing older 2011 signatures with newer 2023 versions ^[3].
• Out-of-Band (OOB) Update: An update released outside the normal monthly schedule to fix a specific, urgent problem. Microsoft sometimes issues these to correct critical bugs introduced by previous patches ^[2][7].

Why "Patch Tuesday" Matters

Microsoft releases cumulative updates on the second Tuesday of every month. These updates are mandatory for most users to keep their systems secure. However, because they modify critical system files—including the Boot Manager and Secure Boot configurations—errors in these files can prevent the computer from starting up correctly ^[3][8].

Note: While updates are crucial for security, they rely on the computer being in a "clean" state before installation. If a previous update failed or was rolled back improperly, the new update might fail to apply correctly, leading to the current boot issues ^[9][10].

Problem Explanation (What's Going On?)

Following the release of the January 2026 updates for Windows 11 (including KB5074109 and KB5077744), users are reporting a wide range of stability issues. While these updates were intended to provide security patches and quality improvements, they have inadvertently introduced bugs that range from visual glitches to critical system failures ^[1][13].

The situation is currently fragmented, with different users experiencing vastly different symptoms depending on their specific hardware configuration and usage patterns.

Core Symptoms and Behaviors

The problems generally fall into three categories: severe system instability, application freezes, and interface glitches.

• Boot Failures and Crashes: Reports indicate that some devices are getting stuck in "endless startups" or experiencing black screens that appear repeatedly. In severe cases, these crashes occur during restarts, requiring users to hold down the physical power button to force a shutdown ^[13].
• Cloud Storage Freezes: A confirmed issue involves applications becoming unresponsive when opening or saving files to cloud-based storage services like OneDrive or Dropbox ^[7][15]. Specifically, Outlook configurations that store PST files on OneDrive may hang and fail to reopen unless the process is terminated ^[7].
• Invisible Sign-In Icons: After installing recent updates, the password icon on the lock screen may become invisible. While the button is still clickable if you hover over the correct spot, the visual indicator is missing ^[11][12].
• Gaming and Graphics Issues: Some users have reported that games cease to run or close immediately after launching. There are also indications of compatibility issues with graphics drivers, where applications like the NVIDIA control panel fail to start ^[13].

How Common Is This?

The scope of these issues varies by the specific bug:

• Enterprise Focus: Microsoft has stated that the "invisible password icon" issue primarily affects enterprise or managed IT environments. Individuals using Windows Home or Pro editions on personal devices are described as "very unlikely" to experience this specific visual glitch ^[1][2].
• General Performance: Conversely, reports regarding boot loops, black screens, and degraded performance suggest a broader impact on general users who rely on their devices for daily work or gaming ^[13].
• Cloud Users: The application freezing bugs are specific to workflows involving cloud storage synchronization, particularly affecting those integrating Outlook with OneDrive ^[15].

Root Causes / Analysis (Why Is This Happening?)

Understanding why the January 2026 update (specifically KB5074109) is causing boot failures requires looking back at the previous month's maintenance. According to official reports, this is rarely a random error hitting a perfectly healthy machine; rather, it is often a chain reaction triggered by previous incomplete installations.

Here are the primary root causes currently identified by Microsoft and industry analysts.

1. The "Improper State" from December

The most significant cause identified by Microsoft involves a lingering issue from the previous month. The company confirmed that the boot failures are frequently occurring on devices that failed to install the December 2025 security update ^[2][8].

When those December updates failed, many systems automatically rolled back the changes. While these PCs appeared to be working normally, the rollback left them in what Microsoft describes as an "improper state" ^[2][8].

• The Trigger: When the January update (KB5074109) attempted to install on these compromised systems, it encountered conflicting system files.
• The Result: This collision results in a critical boot failure, often displaying the UNMOUNTABLE_BOOT_VOLUME error ^[2].

2. Firmware and BIOS Conflicts

Beyond the Windows update files themselves, hardware compatibility appears to be a factor. Reports indicate that early versions of firmware and motherboard BIOS are contributing to the instability ^[4].

If a computer’s BIOS is outdated, it may not correctly handle the changes introduced in the latest Windows servicing stack. This is particularly relevant for users who rarely update their motherboard firmware.

3. Inconsistent System Metadata

For commercial devices in particular, the failure is linked to how Windows manages update data. When the December update was rolled back, it likely left behind:

• Half-applied servicing metadata: Instructions for the operating system that were neither fully implemented nor fully removed ^[2].
• Inconsistent Boot Configuration: Settings that do not match the currently installed system files ^[2].

Because these elements were "half-applied," the January update could not verify the system state correctly, leading to the crash ^[2].

4. Driver and Hardware Interaction (Suspected)

While Microsoft emphasizes the "improper state" of the OS, other technical factors may be exacerbating the issue.

• Secure Boot & NPU: Some reports link startup issues to updates involving NPU (Neural Processing Unit) drivers and expired Secure Boot certificates ^[13].
• Storage Drivers: There is ongoing community discussion suggesting that outdated chipset, SATA, or NVMe drivers may struggle with the new update protocols, although this is less officially confirmed than the "improper state" diagnosis ^[3][19].

Evidence & Reality Check

Official documentation and release logs from January 2026 confirm significant instability issues affecting Windows 11 devices, prompting urgent intervention from Microsoft.

Confirmed System Instability Microsoft’s official release notes for the January 13 update (KB5074109) explicitly list a known issue where applications may become unresponsive when saving files to cloud-based storage services ^[13]. Additionally, documentation for Build 26100.7701 (Release Preview) acknowledges a critical defect where the PC might freeze entirely when attempting to run Windows Terminal with elevated privileges (Administrator mode) ^[11].

Timeline of Urgent Releases The severity of these issues is underscored by the release cadence observed in official channels:

• January 13, 2026: Release of the standard security update KB5074109 ^[5].
• January 17, 2026: Deployment of an out-of-band update (KB5077744) ^[4][6]. Out-of-band releases are typically reserved for critical fixes that cannot wait for the standard monthly schedule.
• January 21 & 24, 2026: Updates to the "Known issues" logs adding resolutions for application unresponsiveness ^[13].

Note: While severe freezing and application lock-ups are officially confirmed in the provided logs ^[11][13], specific documentation regarding "boot loops" was not explicitly detailed in the available Release Preview or Beta Channel excerpts provided ^[1][3][11]. The confirmed "freezing" behaviors, however, present critical stability risks for affected users.

Self-Check / Diagnosis

If you suspect your system is impacted by the January Windows 11 updates, use the following steps to confirm the specific symptoms. These issues manifest differently depending on your device configuration and whether you are in a managed enterprise environment.

1. Identify Startup Failures

The most critical symptom prevents the operating system from loading correctly. You may be affected if:

• Secure Boot Violations: You see a "Secure Boot violation" error message during the boot process. This occurs because the update replaces the older 2011 signed bootmgfw.efi with a 2023 version, which can conflict with the Secure Boot Signature Database (DB) on some devices ^[7].
• Boot Loops: The device powers on, shows the manufacturer or Windows logo, and then restarts repeatedly or shuts down without reaching the login screen. This often requires entering the Windows Recovery Environment (WinRE) to resolve ^[5].

2. Inspect the Lock Screen (Post-Boot)

If your device boots but you cannot sign in easily, check for a user interface glitch affecting the password field:

• Missing Password Icon: On the lock screen, the password icon may be invisible or missing entirely ^[10][11].
• The "Hover" Test: Move your mouse cursor over the space where the password field usually appears. If the button or text box becomes selectable or visible upon hovering, you are experiencing this specific glitch ^[3][4].
• Target Audience: Be aware that this issue primarily affects enterprise-managed devices; personal devices running Home or Pro editions are unlikely to encounter this specific sign-in bug ^[3][4].

3. Test Cloud Storage Applications

Once logged in, the update may cause instability in applications interacting with cloud services:

• Unresponsive Apps: Applications may freeze or encounter errors when opening files from or saving files to cloud storage providers like OneDrive or Dropbox ^[6][12].
• Outlook Freezes: If you use Outlook and store PST files on OneDrive, the application may hang, fail to reopen, or re-download previously downloaded emails unexpectedly ^[6][12].

4. Verify Your Update Version

To confirm if the problematic update is installed on your system, check your Windows Update history for the following Knowledge Base (KB) numbers:

• KB5074109 (OS Builds 26200.7623 and 26100.7623) ^[1].
• KB5077744 (OS Builds 26200.7627 and 26100.7627) ^[2].

Note: If you are experiencing boot failures, you may not be able to check these build numbers until you access the Windows Recovery Environment.

Solutions / What to Do

Resolving update failures often requires a methodical approach, ranging from temporary workarounds to official patches. Below are the recommended steps based on the latest technical documentation.

Short-Term Options (Immediate Mitigation)

If you are currently experiencing issues or want to prevent them before a permanent fix is deployed, consider these immediate actions.

1. Pause or Uninstall the Problematic Update If your system is unstable or specific apps like Outlook are failing, removing the update is often the most direct fix.

• Identify the Update: The primary updates causing recent concern are KB5074109 and KB5077744 ^[3][4][5].
• Uninstall via Settings: Go to Settings > Windows Update > Update history > Uninstall updates. Locate the specific KB number and select uninstall.
• Outlook Specifics: Microsoft has advised users facing Outlook crashes to uninstall the January 2026 update (KB5074109) as a temporary measure ^[10]. Alternatively, using Outlook on the web is a viable workaround until a patch is released ^[10].

2. Use the Known Issue Rollback (KIR) For enterprise environments, Microsoft utilizes a feature called Known Issue Rollback (KIR) to reverse harmful changes without requiring a full manual uninstallation.

• How it works: This typically happens automatically for consumer devices (Home and Pro editions) ^[4][5].
• For IT Administrators: You may need to install and configure a specific Group Policy to deploy the KIR to managed devices. This policy can be found under Computer Configuration > Administrative Templates ^[6][7]. A restart is required to apply these policy settings ^[12].

Note: The Group Policy adjustment temporarily disables the specific change causing the issue while Microsoft develops a permanent resolution ^[12].

3. Address Sign-In Glitches If you encounter a lock screen where the password field is missing:

• Locate the Placeholder: Look for a placeholder or button where the password field should be.
• Click to Activate: Selecting this placeholder often forces the password text box to appear, allowing you to sign in normally ^[4][5].

Advanced & Long-Term Solutions

For users comfortable with command-line tools or those managing multiple machines, these methods ensure a cleaner update process or permanent resolution.

1. Install Out-of-Band Updates via DISM If the standard Windows Update process fails, manually installing the fix using Deployment Image Servicing and Management (DISM) is recommended ^[2][3].

• Download MSU Files: Obtain the relevant MSU files for KB5077744 or KB5074109 from the Microsoft Update Catalog ^[2][3].
• Run Command: Open an elevated Command Prompt and run: DISM /Online /Add-Package /PackagePath:c:\packages\Windows11.0-KB5077744-x64.msu (Ensure the file path matches where you saved the download) ^[2].

2. Secure Boot Recovery In rare cases involving "Secure Boot violation" errors after a database reset or update:

• Recovery Media: You may need to create Secure Boot recovery media to resolve boot issues ^[14].
• Caution: Be careful when resetting databases or toggling Secure Boot, as this can trigger boot failures ^[14].

3. Wait for Future Updates Microsoft has acknowledged these issues and confirmed that they are working on resolutions for future Windows updates ^[12]. If your system is currently stable, deferring optional updates until the next major patch cycle is a safer strategy.

Risks, Limits, and When to Stop

Before attempting any major repairs or rollbacks, it is critical to understand the potential consequences. While restoring functionality is the priority, the methods used to bypass boot failures can introduce new risks regarding data integrity and system security.

Data Loss and Software Removal

One of the most common solutions for boot loops involves resetting the PC or reverting to a system restore point. However, these actions often result in the loss of local data, custom settings, and installed software ^[5].

• System Restore: This reverts system files to a previous state but may uninstall recently added applications.
• System Reset: Depending on the option chosen, this can wipe all personal files. If recent backups are not available, there is a significant risk of losing important information permanently ^[5].

Security Vulnerabilities

Uninstalling the problematic update or pausing Windows Update prevents the crash, but it also creates a security gap.

Warning: Microsoft documentation warns that disabling updates leaves systems without critical fixes, increasing vulnerability to attacks and potentially leading to a loss of technical support ^[13].

For corporate or educational environments, this trade-off is particularly risky, as leaving a system unpatched can expose sensitive networks to threats ^[13].

Secure Boot Complications

In some scenarios, users attempt to modify BIOS settings to resolve boot issues. However, resetting the database (DB) or toggling Secure Boot incorrectly can lead to a Secure Boot violation error ^[6]. This can complicate the recovery process further, requiring the creation of specialized recovery media to fix ^[6].

When to Stop

It is advisable to pause your troubleshooting efforts and seek professional assistance if:

• The device contains critical data that has not been backed up externally.
• You are in a managed IT environment, such as a corporate office. In these cases, IT administrators often deploy specific Group Policy fixes ^[15], and manual intervention by the user can conflict with these protocols.
• The error persists after attempting standard rollbacks. Continued forced restarts or registry edits can corrupt the operating system beyond repair.

FAQ

Which specific update numbers are causing issues?

The primary update associated with the January 2026 cycle is KB5074109, released on January 13 ^[2][9]. Subsequent emergency "out-of-band" updates, specifically KB5077744 (January 17) and KB5078127 (January 24), were released to address instability and bugs discovered after the initial rollout ^[1][9].

What symptoms indicate my system is affected?

Reports confirm that users have experienced frequent application crashes ^[11][12] and specific instability with Microsoft Outlook ^[13]. In more severe cases, critical system errors—often referred to as the "Blue Screen of Death"—can occur, interrupting normal operation and potentially leading to boot loops ^[14][7].

Has Microsoft released a fix for these problems?

Yes. Microsoft deployed emergency updates to resolve these critical failures. KB5077744 was released on January 17 to fix crashing applications ^[6][12], and a second emergency update, KB5078127, followed on January 24 to address persistent issues like Outlook crashes ^[9][13].

Should I install the "Preview" updates listed in Windows Update?

It is generally advisable to exercise caution with preview updates, such as KB5074105 (released January 29, 2026) ^[5]. These are optional, non-security releases intended for testing upcoming changes and may not be as stable as the official monthly patches ^[9].

How can I check if I already have the fixes installed?

You can view your installation history by navigating to Settings > Windows Update > Update History. Look for KB5077744 or KB5078127 in the list of installed updates to confirm that the emergency patches have been applied ^[6][9].

Summary / Key Takeaways

As we close this report, here are the most critical points regarding the January 2026 Windows 11 updates and the issues reported.

• Recent Update Rollout: Microsoft released several updates in January 2026, including KB5074109 on January 13 ^[5][12] and an out-of-band update, KB5077744, on January 17 ^[6][13].
• Known Fixes: The updates address specific bugs, such as PC freezes when running Windows Terminal with elevated privileges from non-admin accounts and reversed labels in Bluetooth & Devices settings ^[9].
• Version Context: These updates apply to Windows 11 versions 24H2 and 25H2, specifically affecting builds like 26100.7623/26200.7623 and 26100.7627/26200.7627 ^[5][6].
• Stability is Key: While new features are exciting, stability remains the priority. If you encounter issues after an update, pausing updates or rolling back to a previous restore point is a standard troubleshooting step.
• Stay Informed: The situation with updates can evolve quickly. Keep an eye on official release notes for any new out-of-band patches that address emerging stability problems.

If you’re unsure about performing these steps yourself, it is usually cheaper to ask someone once than to fix a mistake later.

Quellen

^[1] Microsoft Support: January 13, 2026—KB5074109 (OS Builds 26200.7623 and 26100.7623)

^[2] Microsoft Support: January 17, 2026—KB5077744 (OS Builds 26200.7627 and 26100.7627) Out-of-band

^[3] Windows Insider Blog: Announcing Windows 11 Insider Preview Build 26220.7670 (Beta Channel)

^[4] Windows Insider Blog (Microsoft): Releasing Windows 11 Builds 26100.7701 and 26200.7701 to the Release Preview ...

^[5] BleepingComputer: Microsoft investigates Windows 11 boot failures after January updates

^[6] BleepingComputer: Microsoft links Windows 11 boot failures to failed December 2025 update

^[7] BleepingComputer: Microsoft releases OOB Windows updates to fix shutdown, Cloud PC bugs

^[8] BleepingComputer: Windows 11 KB5074105 update fixes boot, sign-in, and activation issues

^[9] The Register: Microsoft probes Windows 11 boot failures tied to January security updates

^[10] ZDNET: The first big Windows update of 2026 is a glitchy mess - here's the full list...

^[11] ITdaily: Windows 11 startup issues after January updates

^[12] Digital Trends: Microsoft has released an emergency Windows 11 update to fix crashing apps

^[13] ZDNET: Why you need Microsoft's new emergency Windows patch - and the black-screen b...

^[14] NT Compatible: Windows 11 KB5078127 (OS Builds 26200.7628 and 26100.7628) Out-of-band released

^[15] Digital Trends: Microsoft tells you to uninstall the latest Windows 11 update

^[19] Borns IT- und Windows-Blog: Windows 11 24H2/25H2: Januar 2026-Update KB5074109 verursacht Boot-BSOD-Problem