Frustrated user at a desk looking at a Windows laptop with a failed update screen

Why Did Windows Update Fail to Install?

Windows Update can fail because of download integrity, disk space, system files, or a pending-restart/update stack mismatch. If you ignore the error code, you can fix the wrong layer and waste hours. This guide maps each failure mode to the correct repair path for Windows 10 and 11.

This guide is part of our Windows Update: how to fix common update problems series.

What you’ll need

  • Administrator access on the PC
  • The KB number or error code from Update history
  • A stable internet connection
  • At least 20GB of free space if a feature update keeps failing
  • Access to Settings
  • Command Prompt or Windows Terminal opened as administrator

Windows Update failure decision table

Start with the symptom, not the headline error. The same “updates failed” message can come from a damaged download cache, a corrupted component store, a blocked prerequisite, or a Store-backed update problem that appears in Reliability Monitor instead of the normal update page.

Key points: Windows Update failure decision table
SymptomLikely causeFastest safe checkNext fixWhen to escalate
“Updates Failed. There were problems installing some updates”Generic install-stage failureOpen Settings > Windows Update > Update history and note the KB or codeRun the update troubleshooterEscalate if the same KB fails after a reset and manual install
0x800706beWindows Update component or system-file issueCheck whether the failure repeats on the same KBReset update components, then run SFCEscalate if the code returns after DISM and SFC
0x800f081fMissing source files or component-store corruptionRun DISM and watch for repair completionRun DISM, then SFCEscalate if DISM cannot complete or the feature update still rolls back
Repeated retries with no progressCorrupted download cacheSee whether the update sits in Downloading, Installing, or Pending restartRename SoftwareDistribution and Catroot2Escalate if the same package redownloads and fails again
Failure after rebootPending restart or servicing mismatchCheck Update history for install and rollback entriesRun the update troubleshooter, then DISMEscalate if the rollback repeats on the same build
Feature update fails near the endMissing SSU or incompatible servicing stackConfirm the KB needs a prerequisite updateInstall the SSU first, then retry the feature updateEscalate to a manual feature update attempt or an in-place upgrade
Store app updates fail but Windows Update looks normalStuck Store componentCheck Reliability Monitor for Microsoft Store or App Installer errorsRun wsreset.exe and retry the Store-backed updateEscalate if Store resets do not clear the failure
Install fails only when VPN or third-party security is activeNetwork or filter interferenceTemporarily disconnect VPN and pause third-party securityRetry the update with a clean connectionEscalate if the same KB still fails on a direct connection
Update will not stage because space is lowInsufficient free disk spaceCheck available space on the system driveFree space, then try againEscalate if the feature update still rolls back after enough space is available

Why is Windows Update failing to install?

It can fail in one of three phases: download, installation, or the post-reboot stage. A download failure often points to cache corruption, an installation failure often points to component-store or file-integrity problems, and a rollback after reboot often points to a pending update stack mismatch or missing prerequisite.

Quick steps: Why is Windows Update failing to install?

Read the failure pattern first

  1. Open Settings > Windows Update > Update history.
  2. Find the failed KB number or error code in the history list.
  3. Check whether the failure is on a cumulative update, a feature update, or a servicing stack update.
  4. Note whether the failure repeats before reboot or only after reboot.

If a cumulative update fails twice with 0x800706be, but the Microsoft Store still updates apps, that points away from the Store and toward Windows Update components or system files. If a Store app fails in Reliability Monitor while Windows Update itself looks normal, use a different repair path.

Which failure mode matches your error?

Use the code, the update type, and where the failure appears. A code such as 0x800706be often points to Windows Update components or system files, while 0x800f081f often points to missing source files or component-store corruption. A feature update that stops near the end can also mean a missing servicing stack update.

Use the update type as a filter

Cumulative updates, SSUs, and feature updates fail for different reasons. Cumulative updates usually patch quickly and fail when the cache or system files are damaged. Feature updates are larger and are more likely to expose free-space shortages, prerequisite gaps, or a blocked servicing stack.

Spot a Store-backed failure

If the error appears in Microsoft Store, App Installer, or Reliability Monitor rather than the Windows Update page, the Windows Update cache may not be the main issue. In that case, wsreset.exe is the safer first reset before deeper Windows Update repair steps.

Run the built-in repair tools

The update troubleshooter is the first built-in check because it can fix common service and cache problems without changing more than needed. If that does not clear the failure, run DISM and SFC next, since they address component-store damage and file integrity problems that the troubleshooter cannot always repair.

Start with the troubleshooter

  1. Open Settings > System > Troubleshoot > Other troubleshooters in Windows 11, or Settings > Update & Security > Troubleshoot > Additional troubleshooters in Windows 10.
  2. Run Windows Update.
  3. Apply each recommended fix.
  4. Check whether the same update installs before moving to manual repair.

Run DISM and SFC

  1. Open Windows Terminal (Admin) or Command Prompt (Admin).
  2. Run:
    DISM /Online /Cleanup-Image /StartComponentCleanup
  3. Restart the PC after DISM finishes.
  4. Run:
    sfc /scannow
  5. Retry Windows Update.

Run DISM component cleanup before trying the update again, and restart after the command finishes.

Reset Windows Update components

Reset this layer when the same download or install keeps failing on the same KB. SoftwareDistribution commonly stores downloaded updates, and Catroot2 holds update metadata. If either cache is stuck or damaged, Windows can keep retrying the same broken package instead of pulling a clean copy.

Rename the update caches

  1. Open Command Prompt (Admin).
  2. Run:
    net stop wuauserv
    net stop bits
    net stop cryptsvc
    ren %windir%\SoftwareDistribution SoftwareDistribution.bak
    ren %windir%\System32\catroot2 catroot2.bak
    net start wuauserv
    net start bits
    net start cryptsvc
  3. Restart the PC.
  4. Go back to Settings > Windows Update and check whether the update installs.

Windows Update Medic Service can restore repairable components in the background, but it will not fix every bad cache. If the same package fails again after this reset, move to manual install or a repair upgrade instead of repeating the same reset loop.

When should you use the Microsoft update Catalog?

Use the Microsoft Update Catalog when automatic delivery fails but you already know the exact KB number. It is the right move for many cumulative updates and some SSUs. For feature updates, a manual feature update attempt or an in-place upgrade is often the better fallback.

Key points: When should you use the Microsoft Update Catalog?

Install the right package manually

  1. Open Settings > Windows Update > Update history and copy the failed KB number.
  2. Check whether the package matches your device architecture, such as x64 or ARM64.
  3. Download the package that matches your Windows version and build target.
  4. Install the KB, then restart and check Update history.

Escalate feature updates carefully

If a feature update still fails after DISM, SFC, and a cache reset, try a manual feature update attempt first. If that still fails, use an in-place upgrade repair that keeps personal files and apps.

Do not delete update folders while the services are still running. That can leave the cache in a half-reset state and create a new failure on the next retry. Stop wuauserv, BITS, and cryptsvc first, then rename the folders.

Common mistakes

  • Mixing feature updates with cumulative updates. They fail for different reasons.
  • Skipping the SSU check before a feature update retry.
  • Deleting SoftwareDistribution or Catroot2 without stopping the update services first.
  • Assuming antivirus or VPN software is the cause without testing a clean retry.
  • Using a repair upgrade before trying the troubleshooter, DISM, SFC, and a cache reset.
  • Ignoring free space on the system drive when a large feature update keeps rolling back.

A Windows 11 feature update that fails after reboot with the same code every time, while the system drive has only 8GB free, fits a capacity problem far better than a bad package. Free space first, then retry, then move to manual install if the error stays put.

Frequently asked questions

Why is Windows 11 update failing to install?

Windows 11 failures often come from corrupt system files, incorrect registry policy settings, or a missing prerequisite update. Check the update type in Update history, run the troubleshooter, then try DISM and SFC. If it is a feature update, confirm the needed SSU before retrying.

Why is Windows 10 update failing to install?

Windows 10 update failures often come from the same core issues as Windows 11, plus not enough free disk space for larger builds. Check Settings > Windows Update, clear the cache if the same KB keeps failing, and use the Microsoft Update Catalog when automatic delivery does not work.

What causes Windows update errors like 0x800706be or 0x800f081f?

Run DISM first for 0x800f081f, then SFC, then reset Windows Update components if the same error comes back.

How do I fix a Windows update that fails repeatedly?

Use the same order every time: troubleshoot, repair, reset, then install manually. Open the update troubleshooter, run DISM and SFC, rename SoftwareDistribution and Catroot2, and retry. If the same KB still fails, install it from the Microsoft Update Catalog or move to a repair upgrade.

Should I use the Microsoft Update Catalog or a repair install?

Use the Microsoft Update Catalog for a known KB that will not install automatically. Use an in-place upgrade repair when the same update keeps failing after the troubleshooter, DISM, SFC, and a cache reset. For feature updates, a manual feature update attempt is the first fallback.

Similar Posts