Windows 11 KB5077181 Update Triggers Restart Loop on Some Devices — What You Need to Know

Microsoft’s February 10, 2026 security update KB5077181 for Windows 11 (notably reported on affected 24H2 builds) has been linked to a troubling issue on a subset of systems: devices repeatedly restarting in an infinite loop after applying the patch. If your PC is caught in this cycle, or you manage endpoints in an organization and are seeing similar behavior, here’s a concise guide to what’s happening, who’s affected, and practical steps to recover and mitigate risk.

What’s happening

After installing KB5077181, some users report that Windows begins a continuous restart sequence that prevents the system from booting normally. In many cases the device attempts to apply startup repairs or returns to the sign-in screen and then reboots again, creating a loop that blocks access to the desktop and normal troubleshooting.

Common symptoms

• System restarts automatically during or shortly after boot.
• Windows shows “Preparing Automatic Repair” or “Diagnosing your PC,” then reboots.
• Inability to reach the desktop long enough to use Settings or standard uninstall paths.
• Some devices successfully boot into Safe Mode, while others require recovery environment tools to intervene.

Which devices are affected

Reports so far point to a subset of Windows 11 24H2 systems (builds in the 26200.x family), but the issue appears hardware- and driver-sensitive. Systems with certain OEM drivers, firmware, or third-party boot software are more likely to exhibit the reboot loop. Not every machine receiving KB5077181 will be affected.

Likely causes

• Incompatible or outdated drivers (storage, chipset, graphics) conflicting with updated system components.
• Firmware/BIOS incompatibilities.
• Corruption during update application.
• Interaction with third-party boot managers or security software.

Immediate recovery steps for end users

1. Try Safe Mode

   Force the machine into the Windows Recovery Environment (winRE) by interrupting boot 2–3 times (power off during startup). From winRE choose Troubleshoot → Advanced options → Startup Settings → Restart, then select Safe Mode. If Safe Mode works, use Settings → Update & Security → Windows Update → View update history → Uninstall updates to remove KB5077181, or use Control Panel → Programs and Features → View installed updates.

2. Use the recovery environment to uninstall the update

   In winRE go to Troubleshoot → Advanced options → Uninstall Updates. Try uninstalling the latest quality update first.

3. Use command-line uninstall (if accessible)

   From an elevated Command Prompt in winRE or Safe Mode: wusa /uninstall /kb:5077181 (note: ensure correct KB number and follow on-screen prompts).

4. System Restore or Rollback

   If a restore point exists, use System Restore from winRE → Troubleshoot → Advanced options. If the device upgraded recently, consider rolling back to the previous OS version if that option is presented.

5. Last-resort recovery

   If data access is required, boot from external recovery media or a Windows installation USB to back up files before a clean install.

Actions for IT administrators and helpdesk teams

• Quarantine affected devices: Isolate impacted endpoints from critical networks until resolved.
• Pause and block deployment: Use your patch management tools (WSUS, SCCM/ConfigMgr, Windows Update for Business) to pause or decline KB5077181 rollout in rings. For individual troubleshooting, Microsoft’s Show/Hide Updates tool (wushowhide) can hide the update.
• Test before broad deployment: Increase testing in pilot rings, validate driver and firmware compatibility on representative hardware.
• Provide clear user instructions: Prepare step-by-step recovery guidance for helpdesk teams and users, including safe-mode and uninstall procedures.
• Collect diagnostics: Gather Event Viewer logs, WindowsUpdate logs, setupapi.dev.log, and any crash dumps (minidumps) to assist vendor or Microsoft investigations.
• Coordinate with vendors: Contact OEM and driver vendors to confirm compatibility and to obtain updated drivers or BIOS firmware.

Monitoring and next steps

Check Microsoft’s official support channels and Windows health dashboards for advisories or hotfixes. Microsoft may suspend or revise the update and release a corrected package. Apply any revised or replacement updates only after confirming that the new package resolves the issue in test environments. Keep backups and system images current so you can recover quickly if future updates cause disruption.

When to seek professional support

If recovery steps fail or business-critical devices remain inoperable, escalate to Microsoft Support or your device OEM’s technical support. Provide collected logs and a timeline of events to accelerate troubleshooting.

Conclusion

If your device is stable, consider pausing automatic updates temporarily while IT teams and Microsoft investigate. If you encounter the reboot loop, follow recovery steps to uninstall KB5077181 from Safe Mode or the recovery environment and report the issue through Microsoft and OEM support channels. Coordinated testing, careful deployment rings, and fast communication will minimize disruption while a fix is developed.

Licensed under CC BY-ND 4.0 International