Microsoft’s February 10, 2026 security update KB5077181 for Windows 11 versions 24H2 (build 26200.7840) and 25H2 (build 26100.7840) is reportedly causing serious boot issues on some devices.
Shortly after installing the update, affected users say their PCs enter an infinite restart loop, sometimes rebooting more than 15 times without reaching the desktop. The issue appears to impact select hardware configurations, though Microsoft has not officially acknowledged the problem.
KB5077181 is a cumulative security update that includes fixes for 58 vulnerabilities across various Windows components. Among them are six zero-day vulnerabilities that were actively exploited. The update also delivers improvements from earlier releases, new Secure Boot certificates ahead of their June 2026 expiration, fixes for WPA3 Wi-Fi connectivity, and corrections to certain gaming eligibility checks.
Despite these important security improvements, some systems fail immediately after installation. Users report seeing System Event Notification Service (SENS) errors at login, with messages stating that “a specified procedure could not be found.” In some cases, DHCP failures prevent internet connectivity even when a network connection appears active. Installation error codes such as 0x800f0983 and 0x800f0991 have also been reported.
As of mid-February, Microsoft’s release health dashboard does not list any known issues related to KB5077181. However, multiple users have shared their experiences online, describing similar symptoms and boot failures.
For users who can still access their desktops, the recommended step is to uninstall KB5077181. This can be done by going to Control Panel, selecting Programs and Features, choosing View installed updates, locating the KB5077181 update, and clicking Uninstall. After restarting the system, it is advisable to pause Windows Update temporarily to prevent the patch from reinstalling automatically.
If the device is stuck in a restart loop, users can enter the Windows Recovery Environment by interrupting the boot process three times or using installation media. From there, selecting Troubleshoot, then Advanced options, and opening Command Prompt allows the update to be removed using the command:
wusa /uninstall /kb:5077181 /quiet /norestart
After running the command, the system should be restarted manually. Running “sfc /scannow” may also help repair any corrupted system files.
Enterprise administrators are advised to test the update in controlled environments before wider deployment. Using managed deployment tools and monitoring system stability can help reduce risk until further clarification or a revised patch is issued.
While some users have reported improvements such as better graphics stability and general system fixes, the boot loop problem highlights the potential risks that can accompany major security updates. Until Microsoft provides official guidance, caution may be advisable, especially on critical production systems.
