Fix KB5077181 Boot Loop Guide (2026)

Understanding the Windows 11 KB5077181 Boot Loop and Black Screen Problem

If your PC is stuck in a Windows 11 KB5077181 boot loop or you're staring at a black screen after installing the February 2026 Patch Tuesday update, take a deep breath — you're definitely not alone. Thousands of users have reported that KB5077181 (released February 10, 2026, for Windows 11 versions 24H2 Build 26100.7840 and 25H2 Build 26200.7840) is causing critical startup failures. This guide walks you through every proven method to apply the Windows 11 update black screen fix, recover from a restart loop, and deal with scenarios where KB5077181 is stuck during installation. We'll cover both home-user and enterprise recovery paths, including BitLocker considerations, DISM offline repair, and WSUS or Intune deferral strategies.

KB5077181 is a cumulative security update that patches 58 vulnerabilities across Windows components, including six actively exploited zero-day flaws. It also bundles the Servicing Stack Update (SSU), non-security quality improvements, and changes to Secure Boot certificate handling. The irony? This update was actually designed to fix boot failures introduced by the December 2025 and January 2026 update chain — yet it's introduced new critical issues for a subset of devices. Classic Patch Tuesday energy, honestly.

What Causes the KB5077181 Boot Loop?

Understanding the root cause helps you pick the right fix. Community reports and technical analysis point to several overlapping failure modes, so let's break them down.

System Event Notification Service (SENS) Failure

This is the most widely reported symptom. Your device reboots more than 15 times before finally limping to a broken login screen. When you try to sign in, you get hit with: "The System Event Notification Service service failed the sign-in. The specified procedure could not be found."

What's happening under the hood is that a binary replacement in the update changed or removed an exported procedure that SENS depends on during early service initialization. Since SENS sits in the critical sign-in path, this cascading failure prevents interactive logon entirely. It's about as fun as it sounds.

NVIDIA GPU Black Screen

A separate but related issue hits systems with NVIDIA GeForce RTX 30 and 40 series GPUs. These machines can show a persistent black screen during startup or gameplay. The root cause involves driver compatibility and GPU power-state management conflicts introduced by the January 2026 updates. KB5077181 was supposed to fix this — and for many users it actually does — but machines that fail to install the update correctly can end up in an even worse state with a completely black display.

Servicing Stack and Pre-Boot Certificate Conflicts

KB5077181 bundles the LCU (Latest Cumulative Update) together with the SSU. When this combined package runs into driver or OEM firmware incompatibilities during early boot, the update can fail mid-installation and leave your system in a half-baked state. Devices with BitLocker, third-party security suites, or complex storage configurations are disproportionately affected because these setups add extra checkpoints to the boot chain that can clash with the modified pre-boot certificates.

DHCP and Network Connectivity Loss

Here's an annoying bonus issue: after the update applies (or partially rolls back), some devices lose internet connectivity entirely. The NIC shows "Connected" but receives no IP address due to DHCP client errors. This prevents Windows from downloading repair components online and makes remote troubleshooting a nightmare for IT teams.

Symptoms at a Glance

Before diving into fixes, confirm you're actually dealing with a KB5077181-related issue. Look for one or more of these symptoms:

PC restarts repeatedly (15+ cycles) without reaching a usable desktop
Black screen after the Windows logo, with or without a cursor
SENS sign-in error: "The specified procedure could not be found"
KERNEL_SECURITY_CHECK_FAILURE blue screen (especially with NVIDIA GPUs)
Wi-Fi or Ethernet connected but no internet (DHCP failure)
Windows Update error codes 0x800f0983, 0x800f0991, 0x800f0922, 0x80073712, or 0x80096004
Explorer.exe crashes, frozen taskbar, or unresponsive Start menu after boot
BitLocker recovery screen triggered unexpectedly during restart

If any of those match, keep reading.

Fix 1: Uninstall KB5077181 from the Desktop

If your system boots far enough to reach the desktop — even intermittently — this is your fastest recovery path.

Via Windows Settings

Open Settings → Windows Update → Update History.
Scroll down and click Uninstall updates.
Locate KB5077181 in the list (build 26200.7840 or 26100.7840).
Click Uninstall and confirm when prompted.
Restart your PC.

Via Control Panel

Open Control Panel → Programs and Features.
Click View installed updates in the left pane.
Find KB5077181, select it, and click Uninstall.
Restart when the process completes.

Via Elevated Command Prompt

Open Command Prompt as Administrator and run:

wusa /uninstall /kb:5077181 /quiet /norestart

Restart manually after the command finishes. Then immediately pause updates so it doesn't just reinstall itself:

Go to Settings → Windows Update.
Click Pause updates for 1 week (you can extend up to 5 weeks if needed).

Fix 2: Uninstall via Windows Recovery Environment (WinRE)

If your PC can't boot to the desktop at all, you'll need to get into the Windows Recovery Environment. Don't worry — this is more straightforward than it sounds.

How to Enter WinRE

Automatic entry: After three consecutive failed boot attempts, Windows should launch WinRE automatically.
Manual entry: Power on the PC. As soon as you see the Windows logo or spinning dots, press and hold the power button to force a shutdown. Repeat this three times. On the fourth boot, WinRE should appear.
Recovery USB: Boot from a Windows 11 installation USB or recovery drive. Select your language, then click Repair your computer.

Method A: Uninstall Latest Quality Update (GUI)

In WinRE, select Troubleshoot → Advanced options → Uninstall Updates.
Click Uninstall latest quality update.
Confirm and wait for it to complete.
Restart your PC.

Method B: Command Prompt in WinRE (WUSA)

In WinRE, navigate to Troubleshoot → Advanced options → Command Prompt.
If BitLocker is enabled, enter your recovery key when prompted.
Identify your Windows drive letter. In WinRE, your system drive might not be C:. Run:

bcdedit
:: Look for the "osdevice" line to identify your Windows partition
:: Or list volumes with:
diskpart
list volume
exit

Run the uninstall command:

wusa /uninstall /kb:5077181 /quiet /norestart

Type exit and restart.

Fix 3: DISM Offline Package Removal

Sometimes the WUSA uninstall just won't work because KB5077181 bundles the LCU with the SSU as a combined package. When the SSU has already committed, WUSA can't remove the full bundle. DISM offline removal is the more reliable alternative in this situation.

Step-by-Step DISM Offline Removal

Boot into WinRE and open Command Prompt (as described in Fix 2).
Identify the correct Windows drive letter (it may be D:, E:, etc. in WinRE).
List installed packages to find the exact KB5077181 package name:

DISM /Image:D:\ /Get-Packages | findstr "5077181"

You'll get something like:

Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.7840.1.3

Remove the package using the full name:

DISM /Image:D:\ /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.7840.1.3

Run a health check to repair any remaining corruption:

DISM /Image:D:\ /Cleanup-Image /RestoreHealth
sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Close Command Prompt and restart.

Important: Replace D:\ with whatever drive letter actually corresponds to your Windows installation. Getting this wrong will give you "the image was not found" errors, which is just confusing when you're already troubleshooting.

Fix 4: Safe Mode Boot and Uninstall

If the boot loop is intermittent and you can occasionally reach the login screen, Safe Mode might give you a stable enough environment to remove the update.

Enter Safe Mode from WinRE

Enter WinRE using the methods described in Fix 2.
Navigate to Troubleshoot → Advanced options → Startup Settings → Restart.
After the reboot, press 4 or F4 for Safe Mode, or 5 / F5 for Safe Mode with Networking.

Uninstall the Update in Safe Mode

Once in Safe Mode, press Win + R, type control, and press Enter.
Go to Programs and Features → View installed updates.
Select KB5077181 and click Uninstall.
Restart normally and pause Windows Update right away.

Fix 5: Windows 11 "Fix Problems Using Windows Update" Tool

This relatively new recovery feature has honestly been the most effective solution I've seen for cases where KB5077181 fails to install (stuck at a certain percentage or throwing error codes) but the system can still boot.

Open Settings → System → Recovery.
Under Recovery options, click Fix problems using Windows Update.
Follow the on-screen prompts. This performs a repair reinstall that preserves your files, settings, and applications.
The process can take 30–60 minutes on an SSD. Don't interrupt it even if progress appears stalled — seriously, just let it do its thing.

This tool effectively reinstalls Windows core components without touching your data, resolving the underlying component mismatch (error 0x800f0983 / PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING) that prevents KB5077181 from installing correctly.

Fix 6: Resolve NVIDIA Black Screen After KB5077181

If your specific problem is a black screen related to an NVIDIA GPU rather than a general boot loop, these targeted steps may resolve it without having to remove the update entirely.

Update NVIDIA Drivers

Boot into Safe Mode with Networking (see Fix 4).
Download the latest Game Ready or Studio driver from the NVIDIA website — make sure it's explicitly marked compatible with February 2026 Windows 11 builds.
Run the installer and select Clean Installation to replace all existing driver components.
Restart normally.

Disable Hardware-Accelerated GPU Scheduling

If a clean driver install doesn't fix the black screen:

In Safe Mode, open Settings → System → Display → Graphics.
Click Change default graphics settings.
Toggle off Hardware-accelerated GPU scheduling.
Restart and test.

Check GPU Power Management via Registry

KB5077181 modifies how Windows handles GPU power states. If your GPU isn't waking from sleep correctly, this registry tweak can help:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000" /v "DisableDynamicPstate" /t REG_DWORD /d 1 /f

Restart after applying this change. To revert later, just change the value from 1 to 0.

Fix 7: Handle BitLocker Recovery During Boot Loop

BitLocker-encrypted devices are at higher risk of severe issues with KB5077181. When the update modifies boot-level components or Secure Boot certificates, BitLocker may detect what it thinks is an unauthorized change and demand the recovery key. This can be genuinely scary if you're not prepared for it.

Before You Begin Recovery

Retrieve your BitLocker recovery key from one of these locations: your Microsoft account at account.microsoft.com/devices/recoverykey, the Azure AD / Entra ID portal (for corporate devices), a printed copy you saved during BitLocker setup, or your organization's key escrow system (MBAM, Intune, SCCM).
If you can't locate the key, contact your IT administrator before attempting any further recovery. Proceeding without the key on an encrypted drive can result in permanent data loss.

Recovery Steps

When prompted for the BitLocker recovery key during boot, enter the 48-digit key.
Once Windows loads (even in a degraded state), immediately uninstall KB5077181 using one of the methods above.
After successful removal and reboot, open an elevated Command Prompt and suspend BitLocker protection temporarily:

manage-bde -protectors -disable C: -RebootCount 3

This suspends protection for three reboots, giving you time to verify system stability before BitLocker re-engages.

Fix 8: Reset Windows Update Components

For systems where KB5077181 is stuck during installation — downloading, installing, or rolling back in an endless cycle — resetting the update infrastructure can break the loop.

:: Stop Windows Update services
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

:: Rename the update cache folders
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

:: Restart the services
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Warning: Do not rename SoftwareDistribution on a BitLocker-encrypted system without first suspending BitLocker. Multiple users have reported that this triggers an immediate boot failure and BitLocker recovery lockout. Don't learn this the hard way.

After resetting, go to Settings → Windows Update and check for updates again. The update should download fresh and attempt a clean installation.

Fix 9: Manual Installation from Microsoft Update Catalog

If automatic installation keeps failing, downloading the standalone package can bypass corrupted update cache issues.

Visit the Microsoft Update Catalog at catalog.update.microsoft.com.
Search for KB5077181.
Download the version matching your architecture (x64 for most systems, ARM64 for Surface Pro X and similar devices).
Close all applications, temporarily disable third-party antivirus, and run the downloaded .msu file.
Restart when prompted.

Enterprise Remediation: WSUS, Intune, and SCCM

IT admins managing fleets of devices need a systematic approach to the KB5077181 crisis. Here's how to handle it at scale.

Immediate Containment

WSUS: Decline or expire KB5077181 from your WSUS console immediately. If you're using approval rules, verify the update hasn't been auto-approved for your production groups.
Intune / Windows Update for Business: Create a quality update deferral policy that delays feature and quality updates by at least 14 days. Move KB5077181 into a pilot ring only.
SCCM / ConfigMgr: If you've deployed the update via a Software Update Group, remove it from the deployment or set it to "Available" rather than "Required" until Microsoft issues a fix.

Remediation Script for Affected Endpoints

Deploy this PowerShell script via Intune, SCCM, or your RMM tool to automatically uninstall KB5077181 from endpoints that can still boot:

# KB5077181 Remediation Script
$KB = "KB5077181"
$Update = Get-HotFix -Id $KB -ErrorAction SilentlyContinue

if ($Update) {
    Write-Output "Found $KB installed on $(hostname). Attempting removal..."
    $result = Start-Process -FilePath "wusa.exe" -ArgumentList "/uninstall /kb:5077181 /quiet /norestart" -Wait -PassThru
    if ($result.ExitCode -eq 0 -or $result.ExitCode -eq 3010) {
        Write-Output "$KB removed successfully. Reboot required."
        # Pause updates for 7 days via registry
        $pauseDate = (Get-Date).AddDays(7).ToString("yyyy-MM-ddTHH:mm:ssZ")
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" -Name "PauseQualityUpdatesStartTime" -Value $pauseDate
        Write-Output "Quality updates paused until $pauseDate."
    } else {
        Write-Output "Failed to remove $KB. Exit code: $($result.ExitCode)"
    }
} else {
    Write-Output "$KB is not installed on $(hostname)."
}

Log Collection for Escalation

Before reimaging any endpoint, grab these diagnostic logs for escalation to Microsoft Support:

CBS log: C:\Windows\Logs\CBS\CBS.log
DISM log: C:\Windows\Logs\DISM\DISM.log
Windows Update log: Generate with Get-WindowsUpdateLog in PowerShell
Event Viewer: Export Application and System logs covering the 24 hours around the failure
Setup ETL logs: C:\Windows\Panther\

Watch for Known Issue Rollback (KIR)

Microsoft may deploy a Known Issue Rollback (KIR) that silently disables the problematic code path without requiring endpoints to install a new package. Keep an eye on the Windows Release Health dashboard and the KB5077181 article on Microsoft Support for KIR announcements. For managed devices, KIR policies can be deployed via Group Policy or Intune.

Preventing Future Update Boot Loops

Once you've recovered from KB5077181, take these proactive steps so you don't end up back here next month.

Create a System Restore Point Before Updates

Checkpoint-Computer -Description "Pre-Patch-Tuesday-Feb-2026" -RestorePointType MODIFY_SETTINGS

I know it feels tedious, but future-you will be grateful.

Enable Automatic Recovery

Verify that WinRE is properly configured on your system:

reagentc /info

If WinRE is disabled, enable it:

reagentc /enable

Test Updates in a Pilot Ring

Whether you're a home user or enterprise admin, consider delaying updates by 7–14 days. This gives the community time to identify problems before they hit your production machines. Configure this in Settings → Windows Update → Advanced options → Pause updates or via Group Policy deferral settings.

Escrow BitLocker Recovery Keys

Make sure all BitLocker recovery keys are backed up to Azure AD/Entra ID, your on-premises Active Directory, or a secure key management vault. You can verify this with:

manage-bde -protectors -get C:

Keep Firmware and Drivers Current

Many KB5077181 failures involve OEM firmware or driver incompatibilities. Check your manufacturer's support site for BIOS/UEFI updates released in early 2026, and keep GPU, storage, and network drivers updated independently of Windows Update. It's one of those things that's easy to forget until it bites you.

Common Error Codes and What They Mean

When you're troubleshooting KB5077181 issues, these error codes help pinpoint the specific failure:

0x800f0983 (PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING): A required component directory is missing — the update can't find a baseline file it needs. Fix: Use "Fix problems using Windows Update" in Settings → System → Recovery, or perform a repair reinstall.
0x800f0991: Package installation failure related to the servicing stack. The combined SSU+LCU package has a commit conflict. Fix: Reset Windows Update components and retry, or use the manual catalog download.
0x800f0922: Insufficient space in the System Reserved partition or a Secure Boot incompatibility. Fix: Extend the System Reserved partition or update your UEFI firmware.
0x80073712: Component store corruption. Fix: Run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.
0x80096004: Certificate trust issue — the update's digital signature can't be verified. Fix: Check your system date/time, reset cryptographic services, and verify root certificates are up to date.
UNMOUNTABLE_BOOT_VOLUME: The boot partition can't be accessed. Often caused by the December 2025 update leaving the system in an improper state. Fix: Boot from recovery media and run chkdsk /r on the system drive, then use DISM offline repair.
KERNEL_SECURITY_CHECK_FAILURE: GPU-related boot crash, commonly seen with certain NVIDIA configurations. Fix: Boot to Safe Mode and update or roll back your GPU drivers.

Frequently Asked Questions

How do I fix Windows 11 boot loop after KB5077181?

The most reliable method is to enter the Windows Recovery Environment (WinRE) by interrupting the boot process three times, then navigate to Troubleshoot → Advanced options → Uninstall Updates → Uninstall latest quality update. If that doesn't work, open Command Prompt from WinRE and run wusa /uninstall /kb:5077181 /quiet /norestart. For persistent cases where the SSU has committed, use DISM offline package removal as detailed in Fix 3 above. Always pause Windows Update immediately after recovery.

Why does my screen go black after installing the Windows 11 February 2026 update?

The black screen after KB5077181 typically has two causes. First, systems with NVIDIA GeForce RTX 30/40 series GPUs may experience a display driver conflict related to GPU power-state management changes introduced in the January 2026 updates. Successfully installing KB5077181 usually resolves this, but a failed or partial installation can actually make it worse. Second, the SENS service failure during login can leave you at a black screen with a cursor but no desktop. Boot into Safe Mode to update GPU drivers or uninstall the update.

Can I skip KB5077181 and wait for the next update?

You can pause KB5077181 for up to five weeks via Settings → Windows Update → Pause updates. However, this update patches six actively exploited zero-day vulnerabilities, so skipping it indefinitely is a real security risk. The recommended approach is to pause updates, wait for Microsoft to issue a corrected package or KIR (Known Issue Rollback), then install the replacement promptly. Keep an eye on the Windows Release Health dashboard for announcements.

What is error 0x800f0983 when installing KB5077181?

Error 0x800f0983 (PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING) means the update installer can't find a required component directory on your system. This usually indicates a baseline or component mismatch in the Windows servicing stack. Standard SFC and DISM repair commands often fail to fix it because the issue is structural. The most effective fix the community has found is using the "Fix problems using Windows Update" tool in Settings → System → Recovery, which performs a repair reinstall of core Windows components without touching your files.

Will uninstalling KB5077181 remove security patches and leave my PC vulnerable?

Yes, it will. Removing KB5077181 reverts all 58 security fixes it contains, including patches for six zero-day exploits. This is a temporary tradeoff for system stability, and it's worth it if your PC literally can't boot. After uninstalling, keep your antivirus updated, avoid untrusted websites and downloads, and reinstall the update as soon as Microsoft releases a corrected version. Enterprise environments should apply compensating controls — enhanced firewall rules and endpoint detection monitoring — while the update is deferred.