Windows KB5077181 Triggers Boot Loops, Login Errors, and Internet Issues

Microsoft’s Windows KB5077181 update is reportedly causing serious problems for some users, including infinite boot loops and login failures.

According to Neowin, multiple reports appeared shortly after the rollout of update KB5077181, with users describing critical system instability.

KB5077181 update causes boot loops and login failures

The most severe issue involves devices getting stuck in an endless restart cycle. One user claimed their PC rebooted more than 15 times before finally reaching a broken login screen, and multiple systems were reportedly affected in the same case.

During login attempts, a System Event Notification Service (SENS) error appears, stating that a specified procedure could not be found. This error prevents users from accessing the desktop entirely, effectively locking them out of their systems.

Internet connectivity is lost due to DHCP failures

Networking problems have also surfaced after installing the update. Some users report losing internet connectivity even though their devices still show an active Wi-Fi connection.

The issue appears tied to DHCP errors that prevent the system from obtaining a valid IP configuration, resulting in no usable internet access despite being connected to a network.

Installation failures and error codes

Beyond runtime issues, several users have encountered installation failures. Error codes such as 0x800f0983 and 0x800f0991 have been reported during the update process.

One user managed to resolve installation errors by running the System File Checker tool using the “sfc /scannow” command. However, this workaround does not appear to address the broader boot loop and networking issues.

For some affected users, uninstalling KB5077181 has resolved login loops and service errors. The update can be removed through the Control Panel or via recovery mode using the command “wusa /uninstall /kb:5077181 /quiet /norestart.”

Windows 11 may attempt to automatically reinstall the update after removal, so pausing updates can temporarily prevent it from returning.

A permanent fix will likely require an out-of-band update from Microsoft. Until then, uninstalling the patch and pausing updates remains the most practical workaround. Users should monitor the Windows Release Health dashboard for official guidance and status updates.

The situation mirrors January’s Patch Tuesday issues, when update KB5074109 caused widespread instability and forced Microsoft to issue an emergency fix shortly afterward.