There is a special frustration reserved for the laptop that installed a Windows 11 update last week and has failed every update since. The first failure might have been a fluke — a closed lid, a dead battery, a hiccup in the Wi-Fi — but the failures after it are not flukes. They are the fallout: a poisoned cache and a servicing stack that no longer trusts its own state.

This cascade pattern is one of the most common update problems I see in the shop. The good news is that it is also one of the most fixable, because the root cause is almost never your hardware. It is leftover state from the failed install, and leftover state can be cleared.

The sequence below is designed for exactly this situation: an update failed after a Windows 11 update, and now nothing installs. We will identify the failing KB, clear the damage, repair the engine, and verify clean installs resume. If your failure involves the rollback screen specifically, also see our guide on updates that undo their own changes .

Why this happens

  • Poisoned download cache: the failed update’s partial files remain in SoftwareDistribution, and the engine keeps trying to resume from the corrupt data.

  • Half-registered servicing components: an interrupted install leaves components registered as both installed and not installed, confusing every later update.

  • Stuck pending operations: the failed update’s pending.xml entries block the queue until they are cleared or completed.

  • Damaged DataStore records: the update database recorded the failure inconsistently, so subsequent scans misjudge what is needed.

  • Driver left in a bad state: if the failed update included a driver, the device may be in a limbo state that blocks related updates.

  • Error code inherited, not diagnosed: users chase the newest error code when the real problem is the original failed KB still sitting in the queue.

  • Low disk space from failed attempts: each failed attempt can leave gigabytes of temp files, and the shrinking free space then causes the next failure.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Identify the exact failing update

You cannot fix what you have not identified. The update history names the failing KB and its error code, and that pair determines whether you are dealing with one bad update or a systemic engine problem.

  1. Open Settings, Windows Update, then Update history.
  2. Find entries marked Failed and note each KB number and error code.
  3. If one KB fails repeatedly while others succeed, the problem is that update, not the engine.
  4. If everything fails with varying codes, the engine itself is damaged — continue through all fixes.
  5. Write down the newest error code; you will verify it is gone at the end.

Fix 2: Clear the poisoned update cache

This is the fix that breaks most cascades. Removing the corrupted downloads and database forces the engine to fetch fresh copies and rebuild its records, which is exactly what a cascade needs.

  1. Open Terminal (Admin) from the Start right-click menu.
  2. Run net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Run ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Restart the four services with matching net start commands.
  5. Restart the laptop, then click Check for updates and watch what happens.

Fix 3: Run the Windows Update troubleshooter

With the cache cleared, the troubleshooter can now repair the service and task registrations that the cascade damaged. Run it after the cache clear, not before, so it works on clean state.

  1. Go to Settings, System, Troubleshoot, Other troubleshooters.
  2. Click Run next to Windows Update and let it complete fully.
  3. Apply all suggested fixes and restart when it finishes.
  4. Check for updates again and note whether the failing KB changed or cleared.
  5. If the troubleshooter will not run at all, see our troubleshooter repair guide .

Fix 4: Repair the servicing stack with DISM and SFC

A failed update can damage the very machinery that installs updates. DISM restores the component store from Windows Update or local sources, and SFC then repairs protected system files against that clean store.

  1. In Terminal (Admin), run DISM /Online /Cleanup-Image /RestoreHealth.
  2. Wait for completion — 15 to 30 minutes is normal on a laptop.
  3. Then run sfc /scannow and let it reach 100 percent.
  4. Restart the laptop after both complete.
  5. Retry the previously failing update before declaring victory.

Fix 5: Install the failing KB manually

Sometimes only one specific update is broken in the automatic pipeline while the engine is otherwise healthy. Grabbing that KB from the Microsoft Update Catalog and installing it by hand breaks the logjam.

  1. Copy the KB number of the repeatedly failing update from update history.
  2. Search for it on the Microsoft Update Catalog site.
  3. Download the version matching your system (x64 for most laptops).
  4. Run the .msu file and let the standalone installer finish.
  5. Restart, then run Check for updates to confirm the queue flows again.

Fix 6: Check drivers tied to the failed update

When the failing KB is a driver update, the device itself may be wedged. Device Manager reveals the casualties: yellow warnings, unknown devices, or drivers with dates from the failed install day.

  1. Open Device Manager (Win + X, then Device Manager).
  2. Look for yellow warning icons, especially under Display, Network, and System devices.
  3. Right-click any troubled device, choose Update driver, then Search automatically.
  4. If that fails, download the driver from your laptop maker’s support site instead.
  5. Our walkthrough for driver updates that keep failing covers the deeper cases.

Fix 7: Reclaim disk space choked by failed attempts

Every failed attempt leaves temp files behind, and the shrinking free space eventually becomes a cause of failure itself. Cleaning up after the cascade ensures the next attempts have room to complete.

  1. Search Disk Cleanup in Start, run it, then click Clean up system files.
  2. Tick Windows Update Cleanup, Temporary files, and Delivery Optimization Files.
  3. Check Settings, System, Storage for large unexpected consumers.
  4. Confirm at least 20 GB free on C: afterward.
  5. Run one final Check for updates and verify installs complete.

Closing

Update failure cascades feel like the laptop is dying, but they are really just bookkeeping damage from one bad install. Identify the failing KB, clear the poisoned cache, repair the servicing stack, and verify with a clean install — in that order — and the queue almost always starts flowing again without drastic measures.

Frequently asked questions

Why do updates keep failing after one Windows 11 update fails?
Update failures cascade because a failed install leaves behind a corrupted download cache, half-registered components, and pending operations. Every later update inherits that broken state and fails the same way. Clearing the cache and repairing the servicing stack breaks the chain so fresh updates start from a clean state.
Should I keep retrying a failed update?
One or two retries are reasonable — transient network glitches happen. Beyond that, blind retrying wastes time and can deepen the corruption. After two failures, stop and work through the diagnostic sequence below instead of hammering the retry button. Persistent failures after a proper repair sequence point at servicing damage, not bad luck.
Will a failed update damage my laptop?
Almost never. Windows is designed to roll back failed updates to the previous working state; that is what the undoing changes screen is. The risk is not damage but stagnation: a laptop that silently stops taking security patches while looking normal.
How do I know which update is actually failing?
Open Settings, then Windows Update, then Update history. Failed updates show a red failed status with an error code. Note the KB number and code — that pair is what you search for, and it is what support will ask about.