Key Takeaways
1. Microsoft’s Patch Tuesday update on February 10, 2026, introduced Windows 11 KB5077181, updating 24H2 to Build 26100.7840 and 25H2 to Build 26200.7840, with no known issues reported by Microsoft.
2. Despite Microsoft’s claims, users report problems such as a restart loop during installation and sign-in, with devices restarting over 15 times before users can log in.
3. Some users experience sign-in failures related to the System Event Notification Service, encountering an error message without a clear explanation from Microsoft.
4. Networking issues have surfaced post-update, including Wi-Fi connections failing with DHCP errors, leading to a “Connected but no internet” status, and some users unable to install the update due to specific error codes.
5. The update coincides with Microsoft’s Secure Boot transition, which includes warnings about expiring certificates and potential compatibility issues with certain applications due to changes in Windows components.
Microsoft’s Patch Tuesday update on February 10, 2026, introduces Windows 11 KB5077181, elevating 24H2 to Build 26100.7840 and 25H2 to Build 26200.7840. According to Microsoft’s official KB page, the company claims it is not aware of any issues with this release.
Concerns with the Update
However, numerous reports indicate that KB5077181 may cause problems in real-world use, often trading one issue for another. This is particularly concerning since Microsoft asserts that this February update is intended to fully fix the previous UNMOUNTABLE_BOOT_VOLUME boot failure bug, which was linked to failed updates in December 2025, with effects becoming apparent after the January 13, 2026 update or later.
Restart Loop and Sign-In Issues
A major complaint involves a restart loop that occurs during the later stages of installation or around the sign-in process. Third-party sources note that systems might enter “endless” restart cycles after applying KB5077181. Reports on Microsoft’s Q&A forum mention devices restarting more than 15 times before users are able to log in.
For those who do reach the login screen, some users encounter a System Event Notification Service (SENS) error during sign-in which reads: “The System Event Notification Service service failed the sign-in. The specified procedure could not be found.” Currently, there is no clear public explanation from Microsoft, so it’s better to describe it as a post-update sign-in failure related to that specific service error, rather than a clear “DLL mismatch” issue.
Networking Problems and Update Errors
Other discussions highlight networking issues following the update. One report from Microsoft’s Q&A indicates that Wi-Fi connections fail with a DHCP error right after the KB5077181 restart, leading to a “Connected but no internet” status, which only resolves after uninstalling the update (until Windows Update reissues it).
Some users are unable to receive the update at all, with error codes like 0x800f0983 and 0x800f0991 being reported. PCWorld specifically mentions these codes in their overview of the repercussions from KB5077181.
Secure Boot Transition and Compatibility Alerts
KB5077181 is also arriving amidst Microsoft’s larger Secure Boot transition. The company has cautioned that Secure Boot certificates from 2011 will start expiring in June 2026, and they are updating devices to 2023 certificates to prevent a compromised Secure Boot state.
In a separate note, Wibu-Systems (CodeMeter) has issued a product alert indicating that KB5074105 and KB5077181 alter Windows components in ways that could render an AxProtector function-call obfuscation mechanism incompatible under specific protection setups, potentially leading to some protected applications failing to start or operate correctly.
Source:
Link
Leave a Reply