WindowsTutorial

How to Fix a Stuck or Failed Windows Update (2026)

TG By The TechFix Guide Editorial Team  ·  Updated  ·  How we check our guides
A laptop on a desk at night showing a blue update progress screen, lit softly by a warm desk lamp

An update that sits at "Working on updates, 30% complete" for an hour — or fails again and again with an error code like 0x800f0831 — is one of the most frustrating Windows problems, partly because the error messages tell you almost nothing. The fixes below are ordered from least to most involved. None of them delete your personal files, and most stuck updates are solved by the first three steps.

Before anything else: if the update is installing during startup, give it 30 to 60 minutes first. On older laptops with hard disk drives (not SSDs), a genuine update can take a very long time. Interrupting it halfway is the one thing that can cause real damage — do not force a shutdown while the screen says "Working on updates".

Step 1: Note the Error Code

When an update fails inside Windows, go to Settings → Windows Update → Update history. Failed entries show a code such as 0x80070002 or 0x800f0922. You do not need to memorize it, but keep a note — if one specific fix works for your code, forums and Microsoft's own pages will say so, and the code tells support exactly which stage failed. Sometimes the code changes between attempts; that is normal too and still useful information.

Step 2: Restart and Unplug Extras

It sounds obvious, but a full restart resolves a surprising share of failed updates — especially failures that happen instantly, which usually mean some running program is holding a file the installer needs.

  • Restart from the Start menu (a full shutdown with Fast Startup on may not count — Restart bypasses Fast Startup, Shutdown does not).
  • Unplug unnecessary USB devices: external drives, printers, dongles. Installers occasionally hang trying to include them.
  • Try the update again immediately after the restart. Many failures are one-off file locks that a clean session clears.

Step 3: Run the Windows Update Troubleshooter

Windows has a built-in troubleshooter made for exactly this job.

  1. Open Settings → System → Troubleshoot → Other troubleshooters.
  2. Find Windows Update and click Run.
  3. Let it finish, apply any fixes it offers, then restart and retry the update.

It repairs common issues automatically — a stuck service, a misconfigured background transfer, the BITS service not running. It is quick, safe and often enough on its own.

Step 4: Check Free Disk Space

Updates need several gigabytes of working room. If your system drive (usually C:) is below about 10% free space, installs can stall or fail silently halfway.

  • Open Settings → System → Storage and check the C: drive.
  • Run Storage Sense or use Disk Cleanup (search "Disk Cleanup" in the Start menu), tick Windows Update Cleanup, and remove old downloads and the contents of the Recycle Bin.
  • Aim for at least 15–20 GB free before retrying a large feature update.

Step 5: Reset the Update Cache

When downloads repeatedly fail or stall at the same percentage, the update cache itself is usually corrupted. Resetting it is safe — Windows simply re-downloads what it needs.

  1. Right-click Start → Terminal (Admin) (or search "cmd", right-click, Run as administrator).
  2. Stop the update services by running these lines one at a time:
    net stop wuauserv
    net stop bits
    net stop cryptsvc
  3. Rename the cache folder:
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  4. Restart the services:
    net start wuauserv
    net start bits
    net start cryptsvc

Then go back to Windows Update, click Check for updates, and let it download fresh. If all goes well you can delete the SoftwareDistribution.old folder later to free space.

Step 6: Repair System Files

Updates refuse to install when the files they depend on are damaged. Two built-in tools repair that without touching your data.

  1. Open Terminal (Admin) again.
  2. Run sfc /scannow and wait — it may take 10–20 minutes. Restart afterwards.
  3. If the update still fails, run DISM /Online /Cleanup-Image /RestoreHealth. This checks the component store that installers build from and repairs it from Windows Update itself, so keep the internet connected.

Run the update again after DISM finishes. This combination fixes the stubborn "error every single time" cases more often than any other step.

Step 7: Install the Update Manually

If one specific update keeps failing, you can usually sidestep the whole pipeline.

  1. In Update history, find the KB number of the failing update (for example KB5062553).
  2. Go to the Microsoft Update Catalog (catalog.update.microsoft.com) in your browser and search that KB number.
  3. Download the version matching your system (x64 for most PCs) and run the downloaded .msu file.

The standalone installer bypasses Windows Update's download mechanism entirely, so network problems and cache corruption stop mattering.

Step 8: If It Stuck During Startup

If the machine has been sitting on the spinner screen for more than about two hours, the update is genuinely stuck. Wait one more hour, and only then force a shutdown by holding the power button for 10 seconds. Turn it on again — Windows will normally roll the update back automatically and boot to your desktop. From there, work through Steps 2 to 6 before trying again. If it boots into Startup Repair or shows "Undoing changes", let it finish; that is the safety net doing its job, and after it completes the system is exactly as it was before.

FAQ

Should I just turn Windows Update off?

You can pause updates for a week at a time in Settings, and that is a reasonable response to a badly timed problem. Turning updates off permanently is not recommended: cumulative security fixes are what keep ransomware and browser exploits out, and the longer you wait the bigger (and more failure-prone) the eventual update becomes.

Are third-party "update repair" tools worth it?

No. Every step above uses tools already inside Windows. Third-party updaters often bundle adware, install drivers from unofficial sources, or break things the built-in troubleshooter would have fixed safely.

The update fails with 0x800f0922 specifically — anything special?

That code usually means the system could not reach Microsoft's servers or the system reserved partition is too small. Check your internet connection (use a cable if Wi-Fi is flaky), make sure no VPN is running during the install, and free up disk space — those three actions resolve most 0x800f0922 cases.

Quick Checklist

  • Gave a stuck install at least an hour before acting
  • Full restart, USB extras unplugged, retried once
  • Update Troubleshooter run
  • At least 15 GB free on C:
  • Update cache reset (SoftwareDistribution renamed)
  • sfc /scannow and DISM run
  • Manual install from the Update Catalog for a single stubborn KB

Work through these in order and roughly nine in ten update problems end at Step 5 or earlier. The steps never touch your documents, photos or installed programs, so there is no reason to hold back from trying them all before considering a reset or reinstall — that is almost never necessary for an update problem alone.