Windows 11 KB5077181 linked to boot loops: how to uninstall it and recover

What is happening

Some Windows 11 users have hit a brutal failure mode after installing the cumulative update KB5077181: the machine restarts endlessly during boot and never reaches the desktop. According to a troubleshooting guide published on dev.to, the reports surfaced in early 2026 across forums and Microsoft's own Q&A site. Beyond boot loops, users described black screens, failed sign-ins tied to SENS errors, DHCP and Wi-Fi problems, and installation failures with error codes such as 0x800f0983 and 0x800f0991.

The guide notes that Microsoft has not officially confirmed widespread issues with the update, but the pattern reported by users is consistent: the trouble begins right after KB5077181 installs.

What KB5077181 contains

The dev.to write-up describes KB5077181 as a cumulative update released on February 10, 2026. Alongside the usual security fixes and quality improvements, it shipped new Secure Boot certificates — a detail that matters, because some affected users later found their firmware's Secure Boot keys in a corrupted or cleared state.

How to check whether you are affected

If a PC is stuck in a boot loop, the first step is getting into the Windows Recovery Environment (WinRE). The method described in the guide: force a shutdown by holding the power button as soon as the manufacturer logo appears, repeat two or three times, and Windows should eventually show "Preparing Automatic Repair". From there, choose Advanced options, then Troubleshoot, Advanced options and Uninstall Updates, and look for KB5077181 among recently installed updates. If it appears, it is a likely culprit.

The recommended fix: remove the package with DISM

KB5077181 is a combined package — a cumulative update bundled with a servicing stack update — and the guide says Microsoft's preferred removal route for such packages is DISM rather than the standard uninstaller.

One trap catches many people: in WinRE, the Windows drive is not always C:; it may be D:, E: or another letter. From a WinRE command prompt, run diskpart followed by list volume to see the volumes, then use dir C:\, dir D:\ and so on to find the one containing Windows, Program Files and Users. With the correct drive identified, the steps are:

• Run dism /image:D:\ /get-packages to list installed packages
• Locate the entry beginning Package_for_KB5077181~...
• Run dism /image:D:\ /remove-package /packagename:Package_for_KB5077181~..., substituting the full package name

A restart should then complete the recovery, according to the guide.

Alternative removal routes

Two other approaches are documented. The graphical one stays inside WinRE: Troubleshoot, Advanced options, Uninstall Updates, then "Uninstall latest quality update". There is also the command-line route, wusa /uninstall /kb:5077181 /quiet /norestart, which some users reported success with — but Microsoft notes that wusa may fail on combined LCU+SSU packages, so DISM remains the dependable option.

Secure Boot keys may need a reset

A separate subset of users found that Secure Boot keys had been cleared or corrupted after the update. The guide stresses this is not universal and appears limited to particular hardware configurations. Where it applies, the fix is to enter BIOS or UEFI during boot, find the Secure Boot settings, and use the option to reset or install default factory keys rather than a plain "Clear". Updating the BIOS to the latest version can also help.

If nothing else works

Where a restore point predating the update exists, System Restore from WinRE is the simplest path back. Failing everything else, the last resort is a clean install from Windows 11 installation media using custom setup — which erases all data on the system drive, so it earns its last-resort label.

For prevention, the guide suggests waiting a few days before installing new updates, creating restore points before major updates, and pausing updates for a week if unsure.

Why it matters

A boot loop is one of the most severe outcomes of automatic patching: the machine is unusable, and normal uninstall paths may not be reachable. Because KB5077181 is a combined package, the standard Windows Update uninstaller can fail, leaving offline DISM as the realistic recovery route — a procedure most users have never run. The Secure Boot certificate angle adds another layer, showing that an OS update can interact with firmware state in ways that outlive the update itself. With Microsoft not yet confirming the issue, the practical lessons are the old ones: keep restore points enabled, and consider delaying cumulative updates until reports settle.