DEV Community

Darkssel
Darkssel

Posted on

Windows 11 KB5077181 Causing Boot Loops? Here's How to Fix It

#windows11 #bootloop #troubleshooting #sysadmin

You turn on your PC.

The manufacturer logo appears.

Then the spinning circle of dots appears.

And appears.

And appears.

Your PC keeps restarting — over and over — and never reaches the desktop.

You might think:

"Did my PC just die? Did I get hacked?"

Maybe not.

In early 2026, some Windows 11 users reported boot loops and black screens after installing a specific update — KB5077181.

While Microsoft hasn't officially confirmed widespread issues with this update, many users have shared their experiences in forums and Microsoft Q&A.

If you're stuck — or helping someone who is — this guide will help you recover.

What Is KB5077181?

KB5077181 was a cumulative update released on February 10, 2026.

It included security fixes, quality improvements, and new Secure Boot certificates.

For most users, it installed without problems.

But for some, it caused:

  • Boot loops (infinite restarts)
  • Black screens
  • Failed sign-ins with SENS errors
  • DHCP and Wi-Fi issues
  • Installation errors like 0x800f0983 and 0x800f0991

How to Know If You're Affected by KB5077181

If you're stuck in a boot loop after installing updates, here's how to check:

  1. Enter the Windows Recovery Environment (WinRE):

    • Restart your PC
    • As soon as the manufacturer logo appears, hold the power button to force shutdown
    • Repeat this 2–3 times until you see "Preparing Automatic Repair"
    • Then click Advanced options

  2. Check installed updates:

    • Go to Troubleshoot → Advanced options → Uninstall Updates
    • Look for KB5077181 in the list of recently installed updates

If you see KB5077181, it may be the cause of your problem.

Fix 1: Uninstall KB5077181 Using DISM (Recommended)

Because KB5077181 is a combined package (LCU + SSU), Microsoft's preferred method for removal is using DISM.

Important: In WinRE, the Windows drive isn't always C:. It could be D:, E:, or another letter.

How to find the correct drive:

  1. Enter WinRE → Command Prompt
  2. Run: 
diskpart
list volume
Enter fullscreen mode Exit fullscreen mode
  1. Look for the volume that contains your Windows installation. You can identify it by checking for the Windows, Program Files, and Users folders.

Example:

dir C:\
dir D:\
Enter fullscreen mode Exit fullscreen mode
  1. Look for Windows, Program Files, and Users folders — that's your Windows drive

Once you've found the correct drive (let's say it's D:):

  1. List all installed packages: 
dism /image:D:\ /get-packages
Enter fullscreen mode Exit fullscreen mode
  1. Find the package name for KB5077181 (it will look like Package_for_KB5077181~...)
  2. Copy the full package name
  3. Remove it with: 
dism /image:D:\ /remove-package /packagename:Package_for_KB5077181~...
Enter fullscreen mode Exit fullscreen mode
  1. Restart your PC

Fix 2: Uninstall Using WinRE Interface (Alternative)

If you prefer a graphical method:

  1. Enter WinRE
  2. Go to Troubleshoot → Advanced options → Uninstall Updates
  3. Select Uninstall latest quality update
  4. Follow the on-screen instructions
  5. Restart your PC

Fix 3: Uninstall Using wusa.exe (Alternative, May Not Work)

Some users have reported success with this method.

However, Microsoft notes that wusa /uninstall may not work for combined LCU+SSU packages.

If you want to try it:

  1. Enter WinRE → Command Prompt
  2. Run: 
wusa /uninstall /kb:5077181 /quiet /norestart
Enter fullscreen mode Exit fullscreen mode
  1. Restart your PC

If this doesn't work, use the DISM method above.

Fix 4: Reset Secure Boot Keys (If Applicable)

In some cases, users reported that Secure Boot keys were cleared or corrupted after installing KB5077181.

Important: This is not a universal issue. It appears to affect specific hardware configurations.

If you're affected:

  1. Enter your BIOS/UEFI (usually by pressing F2, Del, Esc, or F12 during boot)
  2. Look for Secure Boot settings (usually under Security or Boot)
  3. Find and use Reset/Install default keys or Factory Key Provision — not just "Clear"
  4. Save changes and exit

Alternative: Updating your BIOS to the latest version may also help.

Fix 5: System Restore (If Available)

If you had System Restore enabled:

  1. Enter WinRE
  2. Go to Troubleshoot → Advanced options → System Restore
  3. Select a restore point from before the update
  4. Follow the on-screen instructions

Fix 6: Clean Install (Last Resort)

If nothing else works:

  1. Create a Windows 11 installation USB
  2. Boot from the USB
  3. Select Custom installation
  4. Delete all partitions on the system drive
  5. Click Next to install

Warning: This erases all data on your system drive.

Prevention: How to Avoid This in the Future

  • Delay updates — wait a few days before installing new updates
  • Create restore points — before each major update
  • Pause updates — if you're unsure, pause updates for a week

What If You Want to Monitor Your System Automatically?

Manually checking for problems after every update is tedious.

That's why I built SysPulse — a lightweight Windows security and performance monitoring tool.

SysPulse:

  • Tracks CPU, RAM, Disk, and Network usage in real-time
  • Alerts you when processes spike or crash
  • Logs startup changes and system events
  • Uses less than 30MB of RAM
  • Sends Telegram notifications when unusual activity is detected

You can set it up once and let it watch your PC for you.

You can find it at: syspulse.pro

Summary Table

Problem Solution
Boot loop after KB5077181 Uninstall using DISM (recommended) or WinRE
Secure Boot keys corrupted Reset to factory defaults in BIOS
DISM doesn't work Try wusa.exe (may not work for combined packages)
No restore point Try Safe Mode or clean install

Final Thought

KB5077181 was a frustrating experience for some Windows 11 users.

If you're stuck in a boot loop, don't panic.

Start with the recommended fix:

  1. Enter WinRE
  2. Uninstall using DISM

If that doesn't work, try the other methods in order.

Many users may be able to recover their systems without reinstalling Windows.

Have questions or a boot issue I didn't cover? Drop a comment below.

Happy troubleshooting!

Top comments (0)