Windows 11 KB5077181 Security Update Causing Some Devices to

Microsoft’s February 10, 2026, security update KB5077181 for Windows 11 versions 24H2 (build 26200.7840) and 25H2 (build 26100.7840) has triggered widespread reports of critical boot failures

Users describe devices entering infinite restart loops, often exceeding 15 cycles, preventing access to the desktop.

This cumulative update delivers essential security fixes alongside quality improvements from prior releases like KB5074109.

Microsoft security updates address 58 vulnerabilities across Windows components, including six zero-days actively exploited in the wild, as confirmed by CISA’s Known Exploited Vulnerabilities catalog.

Key patches target elevation of privilege flaws, remote code execution risks, and security bypasses in core systems.

The update also rolls out new Secure Boot certificates to preempt 2011 certificate expirations in June 2026, enhancing boot integrity while fixing gaming eligibility checks and WPA3 Wi-Fi connectivity.

Despite these benefits, Microsoft lists no known issues on its release page or health dashboard as of February 15.

Reported Boot Loops and Workarounds

Affected systems fail post-installation, displaying System Event Notification Service (SENS) errors like “a specified procedure could not be found” at login, alongside DHCP failures causing internet loss despite active connections.

Installation errors such as 0x800f0983 and 0x800f0991 compound the problems, primarily on select hardware configurations. Community forums like Reddit, Microsoft Answers, and ElevenForum document dozens of cases, with some users recovering partial access for repairs.

To resolve, uninstall KB5077181 immediately. From a working desktop, navigate to Control Panel > Programs and Features > View installed updates, select the KB, and uninstall before restarting; pause Windows Update afterward to block reinstallation.

If boot loops persist, enter Windows Recovery Environment (interrupt boot thrice or use media), select Troubleshoot > Advanced options > Command Prompt, and execute: wusa /uninstall /kb:5077181 /quiet /norestart.

Run sfc /scannow for file repairs if needed. Enterprises should deploy via WSUS with testing, monitoring, and release health for fixes.

While positive changes like Nvidia black screen resolutions and explorer.exe stability aid some users, the instability underscores Patch Tuesday risks. Microsoft has yet to acknowledge officially, but user reports urge caution on non-essential systems.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.