Zurück zur Übersicht

TECHFIXBK BLOG

Windows 11 KB5077181: Resolving Boot Loops and Crashes

W

Windows 11 KB5077181: Resolving Boot Loops and Crashes

TechFixBK
||29 min read

Stuck in a Windows 11 boot loop after update KB5077181? Follow our guide to fix black screens, DHCP errors, and SENS login failures safely.

Discover why the February 2026 update is causing system failures and learn the verified steps to restore your PC's stability.

Windows 11 Update KB5077181: Resolving Boot Loops and System Crashes

Learn why the February 2026 security update is causing critical startup failures and follow these verified steps to restore your PC’s stability.

You just updated Windows, and now your PC is stuck in a never-ending cycle of restarts. For many users, the routine Patch Tuesday update has turned into a nightmare scenario where the computer fails to reach the desktop [15][18][21]. If you are seeing a spinning circle, a black screen, or repeated crashes, you are not alone in facing this widespread stability issue [3][4][8].

This guide is specifically for Windows 11 users running versions 24H2 or 25H2 who installed the KB5077181 update released on February 10, 2026 [3][5][13]. We will cover how to identify the symptoms, why this is happening, and the manual steps required to fix it. This article does not address hardware-related failures or issues with older Windows versions.

What This Means for You (TL;DR)

  • The Problem: The KB5077181 update is triggering infinite boot loops (up to 15+ restarts), black screens, and login failures [4][11][12].
  • Common Errors: Users report SENS service errors at login, DHCP network failures, and installation codes 0x800f0983 or 0x800f0991 [2][4][13].
  • Main Solution: You must manually uninstall the update via Control Panel or the Windows Recovery Environment (WinRE) [1][6][14].
  • Critical Step: After removal, you must Pause Updates in settings to prevent Windows from automatically reinstalling the faulty package [1][2][6].

Background: What is KB5077181?

Released as part of the February 2026 Patch Tuesday cycle, KB5077181 was designed to be a major security and reliability update [3][15]. It was intended to patch 58 vulnerabilities, including six actively exploited zero-day flaws [1][3][15].

The update also introduced new Secure Boot certificates to replace older ones set to expire in June 2026 [9][14][15]. While the update aimed to improve system integrity, it has instead caused severe regressions on specific hardware configurations, primarily affecting the boot sequence and core system services [4][12][13].

Problem Explanation: What’s Going On?

The update has transformed many functional PCs into "completely unusable devices" [8]. Instead of loading the desktop, affected systems enter a continuous cycle of reboots immediately after installation [5][8][12].

Commonly reported symptoms include:

  • Infinite Boot Loops: Systems restart repeatedly, sometimes more than 15 times, without intervention [4][11][12].
  • Login Failures: If the system reaches the login screen, users see a System Event Notification Service (SENS) error stating "the specified procedure could not be found" [6][9][16].
  • Connectivity Loss: A DHCP regression causes devices to show they are connected to Wi-Fi or Ethernet but with "no internet access" [2][4][13].
  • System Hangs: Some devices get stuck on a "black screen of death" or a spinning loading icon indefinitely [3][4][10].

Why This Happens

While Microsoft has not yet provided a definitive root cause for all users, technical analysis and reports from IT administrators point to several likely factors:

  • Service Stack Conflicts: Incompatibilities between the update and existing drivers or storage setups appear to be a primary trigger [10][15].
  • SENS and DHCP Regressions: Errors in how the update interacts with the System Event Notification Service and Dynamic Host Configuration Protocol prevent users from signing in or accessing the web [2][8][13].
  • Secure Boot Transitions: The rollout of 2023 Secure Boot certificates may be interacting poorly with certain older BIOS/UEFI configurations [9][15].
  • Corrupted Servicing: Installation failures (errors 0x800f0983 and 0x800f0991) suggest the update may not be applying correctly to the system files in some environments [2][12][14].

How to Check if You’re Affected

If your PC is behaving strangely but still boots, you can verify if this specific update is the cause:

  1. Open Settings and go to Windows Update.
  2. Click on Update History.
  3. Look under Quality Updates for Security Update for Microsoft Windows (KB5077181).
  4. Check for build numbers 26100.7840 (for 24H2) or 26200.7840 (for 25H2) [7][13][15].
  5. If you see these and are experiencing network drops, slow logins, or frequent restarts, the update is likely responsible [11][12][13].

How to Fix It (Step-by-Step)

Since Microsoft has not yet released an official automated fix as of mid-February 2026, manual intervention is required [2][5][8].

Option 1: If You Can Reach the Desktop

  1. Open Control Panel and navigate to Programs and Features.
  2. Click View installed updates on the left sidebar [6][12][13].
  3. Locate KB5077181 in the list.
  4. Right-click it and select Uninstall [6][14].
  5. Restart your computer.

Option 2: If You Are Stuck in a Boot Loop (Recovery Mode)

  1. Trigger the Windows Recovery Environment (WinRE) by turning your PC on and off three times during the boot sequence [14].
  2. Select Troubleshoot > Advanced options > Command Prompt [14][16].
  3. Type the following command and press Enter: wusa /uninstall /kb:5077181 /quiet /norestart [6][13][14]
  4. Restart the system.

Option 3: Preventive Measures

Once the update is removed, you must prevent Windows from immediately reinstalling it:

  1. Go to Settings > Windows Update.
  2. Select Pause updates and choose a duration (e.g., 1 week) [1][2][6].
  3. Wait for Microsoft to acknowledge the issue and release a revised patch [11][25].

Risks and Limitations

While uninstalling the update restores stability, it also removes critical security patches for 58 vulnerabilities [1][15]. This leaves your system potentially exposed to the six exploited zero-day flaws addressed in the February release [3][15].

Users should only roll back the update if their system is unstable or unusable. It is generally recommended to monitor the Windows Release Health dashboard for a replacement fix before unpausing updates [6][14].

FAQ

What if I can't uninstall the update? If the standard uninstall fails, you can try running sfc /scannow in the Command Prompt to repair system files before attempting the uninstallation again [6][12][14].

Does this affect all Windows 11 PCs? No. It appears to hit specific hardware models or configurations, particularly those with complex storage setups or certain third-party security tools [3][10][14].

When will Microsoft fix this officially? As of February 15-17, 2026, Microsoft has not yet listed this as a "known issue" on its official health dashboard, though some regional CERTs have begun issuing warnings [3][10][14].

Summary / Key Takeaways

  • The Cause: Windows 11 update KB5077181 is causing critical boot and network failures [11][12].
  • The Fix: Manually uninstall the update through Control Panel or WinRE using the wusa command [6][13][14].
  • Stay Safe: Pausing automatic updates is necessary to prevent the system from looping back into the same failure [1][2][6].
  • Expect Updates: A revised patch is expected once Microsoft analyzes the widespread failure reports [10].

If you’re unsure about performing these steps yourself, it is usually safer to consult a professional than to risk further system corruption.

Hook & Who This Is For

Imagine starting your computer after a routine Tuesday update, only to find it trapped in a cycle of endless restarts that never reach the desktop [1][8]. For many Windows 11 users, the February 2026 security update (designated as KB5077181) has transformed functional workstations into unresponsive machines [8][34]. If your system is currently displaying a spinning circle, a black screen, or frequent SENS error messages, you are likely part of a growing group of users facing these documented installation failures [1][13].

This article is designed to help those experiencing the specific fallout of the KB5077181 patch. We will cover:

  • Infinite boot loops where the PC restarts before the login screen appears [8][10].
  • Installation errors preventing the update from completing, often marked by codes such as 0x800f0983 or 0x800F0991 [3][10].
  • Post-update instability, including login failures and loss of internet connectivity due to DHCP errors [1][12].

This guide does not cover general hardware-related startup failures, such as power supply issues or physical disk damage, that are unrelated to the Windows 11 February update [1][3]. It is strictly focused on software-induced recovery and the specific regressions reported following the February 10, 2026, release [13][34].

TL;DR / What This Means for You

The February 2026 update for Windows 11, known as KB5077181, is currently causing significant stability issues for a subset of users [3][13]. While intended to resolve previous security vulnerabilities, it has introduced critical regressions affecting system startup and connectivity [1][18].

  • Critical Boot Failures: Affected devices may enter "endless" restart cycles or infinite boot loops [1][5][9]. Some reports indicate systems restarting more than 15 times before reaching a login screen that may be blocked by a System Event Notification Service (SENS) error [1][13][25].
  • Networking and Connectivity: Users are reporting DHCP errors where Wi-Fi displays as "Connected, no internet" [1][3][6]. This prevents access to online services despite an active hardware connection [9][16].
  • Mixed Results for Hardware: Although the update officially fixes specific Blue Screen of Death (BSOD) crashes and WPA3 Wi-Fi bugs found in earlier builds [8], it appears to introduce new gaming performance degradation and driver conflicts on certain hardware configurations [11][12][15].
  • Installation Roadblocks: The update often fails to install entirely, triggering error codes such as 0x800f0983, 0x800f0991, and 0x800f0922 [3][5][19]. Standard repair commands like DISM have reportedly been ineffective in resolving these specific installation failures [3][6].
  • Recommended Action: Experts currently recommend uninstalling KB5077181 via the Control Panel or Windows Recovery Environment to restore system functionality [5][10][19]. After removal, it is generally advised to pause automatic updates until Microsoft provides a verified resolution [11][16].

Any attempt to repair system files or modify the registry carries inherent risks to OS stability. If standard rollback methods fail, a full repair reinstall may be required to regain access to the desktop [3][6].

Background / Basics

Microsoft follows a standard monthly release schedule known as Patch Tuesday, which typically occurs on the second Tuesday of every month [7][12][15]. The KB5077181 update, released on February 10, 2026, is part of this regular security cycle [3][12][18]. These releases are mandatory cumulative updates designed to tighten system security and resolve known software bugs [14][18].

Updates in modern Windows versions are cumulative, meaning a single package consolidates all security patches, reliability fixes, and previous servicing improvements [1][15]. This approach ensures that a single installation brings a device to the most current state by replacing older patches rather than stacking them indefinitely [1]. This process is intended to simplify compliance and maintain consistency across different hardware configurations [1][15].

The core objective of KB5077181 is security hardening, specifically targeting the Windows kernel, Windows Hyper-V, and authentication flows [1][3]. This February 2026 release addresses 58 vulnerabilities, including six zero-day exploits—flaws that were already being actively exploited in the wild before a fix was available [12][14][18]. These patches are critical for closing gaps that could allow remote code execution or unauthorized privilege escalation [1].

In addition to security fixes, these packages often integrate Servicing Stack Updates (SSUs) [1][15]. The Servicing Stack is the underlying component that actually installs Windows updates. By bundling the SSU with the cumulative update, Microsoft aims to improve the reliability of the update process itself and reduce the risk of installation failures caused by outdated infrastructure [1].

Update Feature Purpose Target Versions
Security Hardening Addresses 58 flaws and 6 zero-days [12][18] 22H2, 23H2, 24H2, 25H2 [3][12]
Cumulative Logic Consolidates all previous fixes into one install [1] All supported Windows 11 builds [15]
Servicing Stack Improves future update reliability [1] Integrated into the KB5077181 package [15]

While cumulative updates like KB5077181 are essential for protecting against modern cyber threats, their impact often depends on the specific deployment context, such as hardware drivers and managed security policies [1][15]. Although these releases focus on system stability rather than new features, they can indirectly influence performance by correcting underlying code errors [1].

Problem Explanation: What is Going On?

The release of the KB5077181 update for Windows 11 (versions 24H2 and 25H2) has led to a surge of reports regarding severe system instability [5][16]. While intended to provide security patches, the update appears to cause critical failures that prevent many users from accessing their desktops or maintaining a stable connection [12][24].

Critical Startup and Login Failures

The most disruptive symptom is an infinite boot loop, where affected devices repeatedly restart during the final stages of installation or at the login screen [13][12]. Community reports indicate that systems may cycle through more than 15 consecutive restarts before a user can even attempt to sign in [13][16].

For users who manage to reach the login screen, a System Event Notification Service (SENS) error often blocks access [5][13]. The error message typically states, "The specified procedure could not be found," effectively locking users out of their Windows sessions [13][12].

Networking and Performance Issues

Beyond startup failures, the update has introduced significant regressions in hardware functionality and software performance:

  • Connectivity Breaches: Many users report that their Wi-Fi and Bluetooth stop functioning correctly [24][3]. Specifically, a DHCP error often results in a "Connected but no internet" status, preventing web access despite being linked to a router [13][5].
  • Gaming Instability: Gamers have identified a "rhythmic stuttering" or hitching pattern in various titles that was not present before the update [28]. This performance drop appears unrelated to low frame rates or network latency [28].
  • Installation Errors: In many cases, the update fails to install entirely, leaving the system in a vulnerable state [10][3]. Common error codes cited by users include 0x800f0983, 0x800f0991, and 0x800F0922 [5][3][24].

Summary of Reported Symptoms

Symptom Category Observed Effects
System Access Infinite restart loops (>15 cycles), SENS login failures [13][16].
Networking DHCP failures, Wi-Fi connectivity loss, "Connected but no internet" [5][24].
Performance Rhythmic gaming stutter, system freezes, audio glitches [28][24].
Installation Update failure with codes 0x800f0983 or 0x800f0991 [5][12].

These issues appear across a wide variety of hardware configurations, highlighting significant challenges with the reliability of this specific cumulative update [24]. Because some systems are rendered entirely inaccessible, the impact on user productivity is severe [12][14].

Root Causes: Why This Is Happening

The complications surrounding the KB5077181 update appear to stem from a combination of confirmed software bugs and reported hardware incompatibilities. While Microsoft has officially acknowledged certain triggers, other issues remain under investigation or are categorized as community-reported regressions.

Confirmed Technical Conflicts

Microsoft and industry analysts have identified specific system files and configurations that are directly linked to system instability [2][3].

  • DirectX Memory Management: A confirmed bug in the system file dxgmms2.sys has been linked to critical failures [3]. This file manages memory for DirectX, and its malfunction is a primary cause of the Black Screen of Death (BSOD) or the KERNEL_SECURITY_CHECK_FAILURE error [2][3].
  • Graphics Card Configurations: The update has shown specific instability when interacting with certain GPU setups [2][4]. These conflicts often result in the system failing to render the desktop or crashing during graphics-heavy tasks [10].
  • WPA3-Personal Protocol: A known bug in the networking stack prevents some devices from connecting to Wi-Fi networks using the WPA3-Personal security protocol [2][3]. While a fix was intended to be included in Build 26200.7840, users continue to report regressions [3][12].

Observed Networking and Sign-in Regressions

Beyond the confirmed bugs, several high-impact issues have been documented by technical outlets and user reports across multiple platforms [4][11].

  • DHCP Networking Errors: Many users report that after the restart, Wi-Fi remains "Connected" but provides no internet access [1][4]. This is typically attributed to a DHCP error where the system fails to obtain a valid IP address [7][12].
  • SENS Service Failures: Systems that manage to reach the login screen may be blocked by a System Event Notification Service (SENS) error [4][12]. This prevents users from signing in, often displaying a message that the "specified procedure could not be found" [4].
  • Boot-Loop Cycles: Some devices fall into "endless" restart cycles during the final stages of installation [4]. Reports indicate systems may restart more than 15 times before reaching a stable state or failing completely [4][12].

Hardware and Certificate Incompatibilities

The impact of KB5077181 is not uniform across all devices, suggesting that specific hardware builds may be more susceptible to failure.

  • Specific Laptop Models: Individual testing on hardware such as the Lenovo LOQ (specifically model 16IRH8) has shown unique instability, including Bluetooth disconnects and slow shutdowns not seen on other test systems [11].
  • Secure Boot Transitions: This update coincides with Microsoft’s transition from 2011-era Secure Boot certificates to 2023 versions [4]. Analysts suggest the timing of this certificate rollout may overlap with update failures, potentially leaving some systems in a degraded security state [4][11].
  • Missing Installation Files: Error codes such as 0x80073712 indicate that some update files are either missing or corrupted during the download process, which halts the installation before it can complete [1][5][7].

Note on Hypotheses: While the GPU and WPA3 issues are confirmed by Microsoft [2], the link between specific sign-in failures and a "DLL mismatch" remains an unverified community hypothesis [4]. Users should distinguish between these documented bugs and ongoing troubleshooting theories.

Evidence & Reality Check

The issues surrounding the Windows 11 KB5077181 update are not isolated incidents. Reports from major technology publications, independent hardware testers, and official support channels confirm a consistent pattern of system instability [3][7][13]. While Microsoft initially stated it was not aware of any issues at the time of publication, the timeline of user reports shifted rapidly as the update reached more devices [7].

Verified Industry Reports

Independent testing and media coverage have documented the following symptoms across various hardware configurations:

  • Boot Loop Confirmation: Systems have been observed falling into endless restart cycles, with some devices restarting more than 15 times before reaching a login screen [4][13].
  • Networking Regressions: Analysts have verified a DHCP error that leaves Wi-Fi status as "Connected, no internet" [3][7]. This specific regression was observed on test systems, such as the Lenovo LOQ 16IRH8, where it caused intermittent browsing stalls [8].
  • Hardware Stuttering: Media outlets have highlighted "rhythmic gaming stutter" and Bluetooth instability following the update [14]. Reports indicate these hitches are often independent of frame rates or network latency [8][14].

Official Acknowledgments

Microsoft has since confirmed specific critical bugs introduced in recent updates, though the rollout of fixes may vary by region [2][13].

Issue Confirmed Status Technical Identifier
Blue Screen of Death (BSOD) Confirmed [2] KERNEL_SECURITY_CHECK_FAILURE
Wi-Fi Connectivity Confirmed [13] WPA3-Personal Protocol Failure
DirectX Memory Bug Confirmed [13] dxgmms2.sys
Installation Errors Reported [3] 0x800F0991, 0x800F0983

Community Sentiment and Testing

Forums such as Reddit and Microsoft Q&A contain a growing number of reports regarding installation failures [3][5]. Users have documented cases where update progress reaches a late stage and then fails with error codes like 0x800F0922 or 0x80073712 [3][5]. In some instances, the only verified solution to bypass these installation loops has been a full repair reinstall of the operating system [3].

Warning: Reports suggest that some systems may fail to fully power down after the update, with some laptops remaining warm in carry cases after a "Shut down" command was issued [8].

While Microsoft reports that fixes are being rolled out in stages via Build 26200.7840, the stability of the update appears to remain inconsistent across different hardware vendors [2][7][10].

Self-Check: How to Check if You Are Affected

Identifying whether your system is impacted by the KB5077181 update involves verifying your current build version and cross-referencing specific error codes. If you are experiencing boot loops, connectivity drops, or system freezes, follow these steps to confirm if this specific update is the cause.

Step 1: Verify Your Installed Update Version

The primary way to confirm involvement is to check your Windows Update history for the specific patch identifier.

  1. Open Settings by pressing Windows Key + I.
  2. Navigate to Windows Update and then select Update history.
  3. Look under the Quality Updates section for KB5077181 [3][5][6].
  4. Alternatively, you can check your build number. This update is associated with Windows 11 Build 26200.7840 and later [1][2].

Step 2: Identify Critical Installation Error Codes

Many users have reported that the update fails during the installation phase. If your update process stops or rolls back, look for these specific hex codes in the Windows Update menu:

Error Type Common Error Codes
Failed Installation 0x800F0991, 0x800F0983, 0x800F0922 [3][6][13]
Missing Files 0x80073712, 0x80096004 [3][6]

Step 3: Check for "Black Screen" and Driver Failures

If the update installed successfully but the system remains unstable, it may be triggering a Black Screen of Death (BSOD). This often occurs during GPU-intensive tasks or gaming [36].

To confirm this specific bug, check the Windows Event Viewer for the following indicators:

  • Error Code: KERNEL_SECURITY_CHECK_FAILURE (Bug Check 0x139) [4][8][9].
  • Faulting Module: dxgmms2.sys (DirectX Graphics MMS) [2][36].
  • Stop Code: VIDEO_TDR_FAILURE [36].

Step 4: Monitor Network and Startup Behavior

Not all symptoms are fatal crashes; some manifest as service failures or connectivity issues. Indicators that the KB5077181 update is affecting your system include:

  • Boot Loops: The PC enters an endless cycle of restarts immediately after the update attempt [5][13].
  • SENS Error: A notification stating the system cannot connect to the System Event Notification Service [13].
  • DHCP/Wi-Fi Issues: The PC shows as "Connected, no internet" or fails to connect to WPA3-Personal networks due to valid IP address retrieval failures [1][2][3][13].

Warning: If your system is stuck in an endless boot loop, do not attempt to force-install further updates, as this may lead to potential data loss in unsaved work [36]. Check for the SENS or DHCP error messages during the login attempt to confirm the update's impact [13].

Solutions: What You Can Do

If your system is experiencing boot loops, login failures, or network issues after the February update, several manual recovery methods are available [2][5][17]. Because Microsoft has not yet released an automated fix, users must manually intervene to restore system stability [2][5][18].

Beginner Steps: Uninstalling via the Desktop

If you are still able to access your desktop or can boot into Safe Mode, use the standard Windows interface to remove the update. This is the safest method for most users [19][25].

  1. Open the Control Panel.
  2. Navigate to Programs and select Programs and Features.
  3. Click on View installed updates on the left-hand sidebar [5][17][25].
  4. Locate Security Update for Microsoft Windows (KB5077181) in the list.
  5. Select it and click Uninstall.
  6. Restart your computer when prompted [17][25].

Advanced Steps: Recovery via Command Prompt

If your PC is stuck in a boot loop and cannot reach the login screen, you must use the Windows Recovery Environment (WinRE). This method utilizes the Command Prompt to force an uninstallation [17][18][25].

  1. Enter WinRE by interrupting the boot process three times or using recovery media [17].
  2. Navigate to Troubleshoot > Advanced Options > Command Prompt.
  3. Type the following command exactly as shown: wusa /uninstall /kb:5077181 /quiet /norestart [17][19][25].
  4. Press Enter and wait for the process to complete.
  5. Restart your computer [17].

Some users have also reported success in resolving minor installation errors by running the System File Checker tool. To do this, type sfc /scannow into the Command Prompt and press Enter before attempting a restart [17][25].

Critical Maintenance: Preventing Reinstallation

Removing the update provides immediate relief, but Windows may attempt to reinstall the problematic patch automatically [5][25]. To prevent the boot loops from recurring, you must temporarily halt the update service [2][17].

  • Navigate to Settings > Windows Update.
  • Select the option to Pause updates for at least one week [2][5][19].
  • Monitor official channels, such as the Windows Release Health dashboard, for a permanent fix before resuming updates [18][25].
Action When to Use Primary Goal
Control Panel Uninstall System is bootable Simple removal of KB5077181 [5][17]
WinRE Command Prompt System is in a boot loop Forced removal without OS access [17][25]
Pause Updates After uninstallation Prevent automatic re-infection [2][5]
SFC Scan After removal Repair corrupted system files [17][25]

For IT administrators managing enterprise fleets, it is recommended to validate KB5077181 against a test group before a broad rollout. Testing should specifically focus on devices using BitLocker, third-party security suites, or complex storage configurations, as these setups appear more susceptible to failure [18].

Risks, Limits, and When to Stop

Attempting to resolve critical system failures like the KB5077181 boot loop involves inherent risks. While manual fixes such as using the Command Prompt or uninstalling updates via the Windows Recovery Environment (WinRE) are often effective [6][18], they require modifying core system behavior. If these processes are interrupted or performed incorrectly, the operating system may become further destabilized [2][11].

Potential Risks of Manual Intervention

Using recovery tools and commands like wusa /uninstall or sfc /scannow can potentially lead to the following issues:

  • Data Access Complications: Systems utilizing BitLocker or third-party security suites may face additional layers of complexity when attempting to bypass a boot loop [3][18].
  • Incomplete Rollbacks: In some instances, uninstalling the update may not fully restore system functionality, particularly if the initial installation corrupted secondary system files [2][11].
  • Persistent Errors: Users have reported that even after attempting manual repairs, error codes such as 0x800F0991 or 0x800F0983 may persist or change, indicating deep-seated registry or file-system issues [5][11].

When to Stop and Seek Professional Assistance

It is important to recognize when a software-based fix is no longer viable. It is generally recommended to stop manual troubleshooting if any of the following scenarios occur:

  1. Inaccessible Recovery Environment: If the PC is stuck in an endless restart cycle and cannot trigger the Automatic Repair screen or enter WinRE through manual interruptions, the system may require external bootable recovery media [3][6].
  2. Repeated Automated Repair Failures: If Windows enters a "loop of automated repair attempts" that never resolve the problem, the operating system's internal recovery tools are likely unable to fix the specific corruption caused by KB5077181 [3][5].
  3. Signs of Hardware Stress: While these issues are typically software-based, continuous boot loops can place unnecessary stress on mechanical hard drives or specific storage configurations [3].
  4. Network-Level Lockouts: In enterprise environments, if multiple devices across a specific hardware model or configuration fail simultaneously, it may indicate a driver or security tool conflict that requires a coordinated IT response rather than individual machine fixes [3][18].

Warning: Performing a "repair reinstall" using the Windows Update recovery option is considered a more reliable solution for persistent installation errors, but it can be time-consuming and carries a small risk of data loss if not handled correctly [11][14].

Limitations of Current Fixes

Current solutions are primarily reactive. Since there is no official, definitive fix from Microsoft for all affected users yet, the "safe play" for those who have not yet updated is to pause automatic updates entirely [2][3]. Relying on manual uninstallation is a temporary measure; without pausing updates, the system may attempt to reinstall the problematic KB5077181 patch, triggering the loop again [2][5].

FAQ

Can I skip or postpone the KB5077181 update?

Yes, users can and often should pause automatic updates if they are concerned about system stability. Because KB5077181 has been reported to cause critical boot loops and login failures immediately after installation, many experts suggest navigating to Settings > Windows Update > Pause Updates to prevent the patch from installing [5][13][21]. While Microsoft intended this update to deliver important security improvements, it is generally observed that pausing the update is a viable temporary measure until an official fix is released [5][8][25].

Will uninstalling this update leave my system vulnerable?

Uninstalling the update effectively restores system stability but does remove several critical security patches. KB5077181 was designed to address 58 vulnerabilities, including multiple actively exploited zero-day flaws such as CVE-2026-21533 (affecting Remote Desktop Services) and CVE-2026-20841 (affecting Notepad) [8][14][16]. Consequently, removing the patch potentially exposes the system to these specific risks [14][16]. Users must often balance the immediate need for a functional, bootable computer against the long-term requirement for these security fixes [8][16].

What should I do if I cannot reach the desktop to uninstall the update?

If a PC is stuck in an infinite restart loop, the update can be removed through the Windows Recovery Environment (WinRE) [12][21][25]. You can typically trigger this mode by interrupting the boot process three consecutive times—such as by holding the power button during startup—or by using external installation media [14][16]. Once in WinRE, follow these steps to manually remove the patch:

  • Navigate to Troubleshoot > Advanced options > Command Prompt [16][34].
  • Type the following command: wusa /uninstall /kb:5077181 /quiet /norestart [11][16][34].
  • Press Enter and restart the computer once the process finishes [11][25].

Are there specific error codes associated with this update failure?

Several specific error codes have been documented by users and technical analysts. The most frequent installation and startup errors include 0x800f0983, 0x800f0991, 0x800f0922, and 0x80073712 [5][13][14]. Additionally, some systems may display a System Event Notification Service (SENS) error at the login screen or encounter DHCP failures that disrupt internet connectivity even when a physical or Wi-Fi connection is active [5][16][25].

Is there an official fix from Microsoft for these boot loops?

As of mid-February 2026, Microsoft has not yet officially acknowledged the KB5077181 boot loop issues on its Windows Release Health dashboard [11][25]. While the company has released Insider Preview Build 26220.7859 for testing new features and reliability improvements, a specific "out-of-band" patch for the public version of the February update is still pending [1][15][18]. Monitoring official documentation for new updates is recommended, as Microsoft typically pushes emergency fixes for widespread recovery issues [18][25].

Summary / Key Takeaways

The KB5077181 update for Windows 11, released in February 2026, has introduced significant stability issues for a wide range of users [3][24][30]. While intended to provide critical security fixes, the deployment has frequently resulted in severe system disruptions [5][11][13].

  • Widespread Instability: The update is linked to infinite boot loops, sign-in failures involving the System Event Notification Service (SENS), and installation errors such as 0x800f0983 and 0x800f0991 [5][13][16].
  • Networking and Performance: Many users report "Connected but no internet" status due to DHCP errors, alongside degraded gaming performance and intermittent Bluetooth disconnections [11][14][24].
  • Effective Workarounds: The most reliable solution currently involves uninstalling the update via the Control Panel or Windows Recovery Environment and pausing automatic updates to prevent reinstallation [5][12][24].
  • Official Response Status: While some official documentation initially listed no known issues, newer reports indicate that Microsoft has begun acknowledging problems and is shipping fixes, particularly for enterprise environments [9][12][18].

If these issues persist after attempting a rollback, or if the system remains stuck in an automated repair loop, it is often more efficient to consult a technical professional than to risk further software corruption through repeated failed boot attempts.

Quellen

[1] Announcing Windows 11 Insider Preview Build 26220.7859 (Beta Channel)

[2] Windows 11 update causing BSODs and Wi-Fi issues, Microsoft confirms

[3] Users report install errors and system bugs after Windows 11’s Feb update

[4] Microsoft admits Windows 11 is crashing with some GPUs and says it

[5] February's Windows 11 update is causing startup problems for users

[6] 14 privacy tweaks every Windows 11 user should know about

[7] [Fixed] Blue Screen of Death on Windows 11

[8] How to Fix Blue Screen Windows 10: Easy troubleshooting steps - Solve Your Tech

[9] Microsoft says Windows 11 update causes BSOD on some GPU config, broke WPA3 W...

[10] Windows 11 KB5077181: Microsoft claims stability, my Lenovo LOQ proves otherwise

[11] KB5077181 February 2026 Windows 11 Update Causes Gaming Issues: Community Rep...

[12] Microsoft Windows 11 KB5077181 Update Triggers Infinite Restart Loop on Some ...

[13] Windows 11 KB5077181: Update causes boot loops, DHCP errors, and sign-in fail...

[14] Stop installing these Windows apps — you don’t need them anymore

[15] Windows 11 KB5077181 Update: What’s New, Critical Fixes, Known Issues & S...

[16] Windows 11 KB5077181 Security Update Causing Some Devices to Restart in an In...

[17] Windows 11 KB5077181 boot loop issues on 24H2 systems fix for login failures ...

[18] Windows 11 KB5077181 Is Causing Frustrating Boot Loops, But Microsoft Is Roll...

[19] How To Fix KB5077181 Update Triggering Restart Loops & Network Failures I...

[20] Windows 11 Update KB5077181 Traps Users in Boot Loops

[21] New Windows 11 Update KB5077181 Is Causing Boot Loops and System Crashes - Ha...

[22] Windows 11 boot problems can be fixed by KB5077181 update: Microsoft

[23] My Windows 11 PC will refuse to start unless this USB drive is plugged in

[24] Windows 11 Update KB5077181 Causes Issues for Some Users

[25] Windows 11 KB5077181 boot loop fix: uninstall guide | tbreak

[26] Windows 11 KB5077181 fixes Nvidia black screen bug | tbreak

[27] Windows 11 KB5077181 fixes gaming bugs, Nvidia black screen, and performance ...

[28] Reddit erupts over KB5077181: New update triggers rhythmic gaming stutter

[29] KB5077181 - Details, Issues, & Feedback - NinjaOne

[30] KB5077181 Windows 11 Update: February 2026 Patch Tuesday Analysis & User ...

[31] The fiasco Windows 11 continues with the February update that breaks everything

[32] How to check if Windows 11 has applied the new Secure Boot 2023 certificates ...

[33] Your Windows 11 PC could face boot issues in 2026 – here’s how to check and f...

[34] Windows 11 users report issues after Feb. 2026 update. How to fix error

[35] Reddit entra en erupción por KB5077181: Una nueva actualización provoca un ta...

[36] Windows 11 KB5077181 Fixes GPU Black Screen dxgmms2.sys Crash: Analysis &...

[37] Windows 11 KB5077181: Update causes boot loops, DHCP errors, and sign-in fail...

[38] Microsoft finally lets you disable this annoying Windows 11 security feature

[39] XFN 1.1 profile

[40] Windows Latest

[41] static0.makeuseofimages.com

[42] static0.makeuseofimages.com

[43] static0.makeuseofimages.com

[44] static0.makeuseofimages.com

[45] MakeUseOf

[46] MUO | LinkedIn

[47] MakeUseOf (@muo_official) on Flipboard

Relevant Services

More from the Blog

Brauchen Sie Hilfe?

Wir reparieren Ihren PC oder Laptop schnell und zuverlässig.

Jetzt Reparatur anfragen