Microsoft’s February 10, 2026, Patch Tuesday cumulative update KB5077181 for Windows 11 is being linked to severe boot failures on some devices, with users reporting systems that restart repeatedly and never reach the desktop.
The issue is primarily discussed across community threads, including a Reddit post describing more than 15 reboot cycles after installation, effectively locking users out of Windows sessions.
The update targets Windows 11 version 24H2 (OS build 26200.7840) and 25H2 (OS build 26100.7840) and includes both security fixes and quality improvements carried forward from earlier releases such as KB5074109.
Update Triggers Infinite Restart Loop
Cybersecuriynews reports indicate affected machines fail shortly after the update completes, then enter an “infinite restart loop.”
Some users who briefly regain access describe login-time errors tied to System Event Notification Service (SENS), including messages like “a specified procedure could not be found,” plus DHCP-related failures that can break internet connectivity even when the network appears connected.
Other cases mention installation failures with error codes 0x800f0983 and 0x800f0991, suggesting the problem may vary by hardware, drivers, or servicing stack conditions.
KB5077181 arrives as part of Microsoft’s broader February 2026 security release, which reportedly addresses 58 vulnerabilities across Windows components, including six zero-days described as actively exploited and referenced by CISA’s Known Exploited Vulnerabilities catalog.
While Microsoft’s release notes emphasize security hardening, users say the stability impact is immediate and disruptive.
The update also introduces new Secure Boot certificates ahead of older 2011 certificate expirations expected in June 2026, a change intended to strengthen boot integrity, alongside fixes for gaming eligibility checks and WPA3 Wi‑Fi connectivity.
| CVE ID | CVSS Score | Description |
|---|---|---|
| CVE-2026-21510 | Not provided | Windows Shell security feature bypass allowing SmartScreen evasion via malicious links |
| CVE-2026-21519 | Not provided | Desktop Window Manager elevation of privilege to SYSTEM level |
| CVE-2026-21533 | Not provided | Windows Remote Desktop Services elevation of privilege; exploited zero-day |
| CVE-2026-20841 | Not provided | Notepad remote code execution via crafted Markdown files |
Workarounds and guidance
As of February 15, Microsoft’s release page and health dashboard discussions show no widely published “known issue” entry for a restart-loop regression, even as forum reports accumulate.
If you can still reach the desktop, users recommend uninstalling KB5077181 via Control Panel → Programs and Features → View installed updates, then pausing Windows Update to prevent immediate reinstallation.
If the device cannot boot normally, use Windows Recovery Environment (trigger by interrupting boot three times or using installation media), then open Command Prompt and run:
textwusa /uninstall /kb:5077181 /quiet /norestart
After recovery, run sfc /scannow to repair system files if Windows loads inconsistently.
For enterprises, stage deployment through WSUS or rings, validate on representative hardware, and monitor update compliance and boot health before broad rollout.
Follow us on Google News, LinkedIn, and X to Get Instant Updates and Set GBH as a Preferred Source in Google
