When Windows Update fails to install — not one update, but everything, every time — the problem is not the updates. It is the machine that installs them. Something in the update engine is broken: the cache, the database, the services, or the servicing stack underneath them all. The updates themselves are almost certainly fine.

This distinction matters because it changes the strategy. You do not need a different update; you need a working installer. The sequence below repairs the installer layer by layer, from the two-minute checks to the deep servicing repairs, with a verification step so you know exactly when you are done.

Follow it in order and stop at the first fix that works. If your failure shows the undoing changes rollback screen, pair this guide with our undoing changes repair guide for the rollback-specific steps.

Why this happens

  • Corrupted SoftwareDistribution cache: damaged downloads and database files make every install fail the same way.

  • Damaged servicing stack: the component store or system files that perform installs are corrupt.

  • Disabled update services: wuauserv, cryptSvc, bits, or msiserver disabled or stuck in a bad state.

  • Security software blocking installs: antivirus or OEM security suites intercepting the installer’s file operations.

  • Insufficient disk space: installs need working room; full drives fail everything uniformly.

  • Pending operations jam: a stuck previous install blocks the queue for all subsequent ones.

  • Policy or registry damage: tweakers and bad policies can disable the install machinery.

How to fix it

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

Fix 1: Capture the error code and pattern

Five minutes of observation now saves an hour of wrong fixes later. The code and the pattern — everything fails versus one thing fails — determine the entire strategy.

  1. Open Settings, Windows Update, Update history and list every failed entry.
  2. Write down each error code; identical codes mean one cause, varied codes mean engine damage.
  3. Note whether downloads complete and installs fail, or downloads themselves fail.
  4. Check free space on C: (Settings, System, Storage) — rule out the trivial cause now.
  5. Keep this notes list; you will verify each code is gone at the end.

Fix 2: Run the Windows Update troubleshooter

The automated first pass: it repairs services, tasks, and registry entries in two minutes. Even when it does not fully fix things, its detailed report narrows the diagnosis and tells you exactly which deeper repair to attempt next. Even when it does not fully fix things, its report narrows the diagnosis.

  1. Go to Settings, System, Troubleshoot, Other troubleshooters.
  2. Click Run next to Windows Update; let it finish completely.
  3. Apply all fixes and restart the laptop.
  4. Click Check for updates and observe whether the failure pattern changed.
  5. View detailed information and note anything marked Not fixed.

Fix 3: Reset the update components completely

The central repair for universal install failure. New cache, new database, restarted services — this gives the installer a clean foundation and resolves most cases outright.

  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.
  4. Run ren C:\Windows\System32\catroot2 catroot2.old.
  5. Restart the services with net start commands, reboot, and retest.

Fix 4: Repair the servicing stack

When the cache reset does not help, the damage is deeper — in the servicing stack itself. DISM restores the component store; SFC repairs system files against it.

  1. In Terminal (Admin), run DISM /Online /Cleanup-Image /RestoreHealth.
  2. Allow 15-30 minutes for completion without interruption.
  3. Run sfc /scannow to 100 percent.
  4. Restart the laptop.
  5. Retry the failing updates and check whether the codes changed or cleared.

Fix 5: Eliminate security software interference

With the engine repaired, rule out the external blocker. Security suites are the most common reason a healthy engine still cannot install.

  1. Temporarily disable third-party antivirus real-time protection.
  2. Pause any OEM security suite (HP Wolf, Dell, Lenovo equivalents) if present.
  3. Run Check for updates and attempt the install.
  4. Re-enable all protection immediately after the test, pass or fail.
  5. If installs succeed while disabled, configure antivirus exclusions for update folders.

Fix 6: Install one update manually as a test

A manual install isolates the engine from the automatic pipeline. If the standalone installer works, the automatic pipeline has the problem; if it fails identically, the servicing stack needs deeper repair.

  1. Pick one small failing update and note its KB number.
  2. Download it from the Microsoft Update Catalog .
  3. Run the .msu package and observe the result carefully.
  4. Success points at pipeline issues — repeat the Fix 3 reset more aggressively.
  5. Identical failure points at servicing damage — continue to Fix 7.

Fix 7: Perform an in-place upgrade repair

The final repair before reinstallation: reinstalling Windows over itself refreshes the entire servicing stack while keeping files and apps. It fixes install failures that resist every targeted repair.

  1. Back up important files (the process preserves them, but verify the backup).
  2. Download the Windows 11 ISO from Microsoft’s download page .
  3. Mount the ISO, run setup.exe, and choose Keep personal files and apps.
  4. Let the upgrade complete through all restarts.
  5. Run Windows Update afterward and confirm installs now succeed.

Closing

Universal install failure is an engine problem with an engine solution: observe the pattern, run the troubleshooter, reset the components, repair the servicing stack, rule out security software, and verify with a manual install. Worked in order, this sequence restores the installer on virtually every laptop without reaching for the reinstall option. If the troubleshooter itself is part of the problem, our troubleshooter usage guide gets it working again.

Frequently asked questions

Why does Windows Update fail to install everything?
Total installation failure — where no update of any kind installs — points at the update engine itself rather than any single update: corrupted cache or database, damaged servicing files, disabled services, or interference from security software. The engine-level repairs in this guide address exactly that category of failure. The engine-level repairs in this guide address exactly that.
How do I find the error code for a failed install?
Open Settings, Windows Update, then Update history. Each failed entry shows an error code like 0x80070002, which narrows the cause dramatically when you search for targeted fixes. That code narrows the cause dramatically — write it down before searching for fixes, and mention it if you ask for help.
Is it safe to delete the SoftwareDistribution folder?
Yes, after stopping the update services. Windows rebuilds it automatically, and only cached update files are lost — they re-download. Personal files, programs, and settings are never stored there, so your data and applications are completely safe throughout the process.
At what point should I reinstall Windows?
Only after the full sequence here fails, including the manual KB install and the in-place upgrade. Reinstallation is the last resort because these repairs resolve the overwhelming majority of install failures — most users never need to go that far.