How to Fix Windows Update Problems in Windows 11

You open Settings › Windows Update, click Check for updates, and it hangs at 0%, stalls partway through a download, or throws an error code and rolls back on restart. A stuck Windows Update is one of the most common Windows 11 headaches — and the good news is that it is almost always fixable in a few minutes without reinstalling Windows.

This guide walks the fixes in order, from the safe automatic tools to the manual service and file repairs. Most people never get past step three. The later steps — clearing the download cache and repairing system files — are for the stubborn cases where updates keep failing with the same error. Everything here is framed for Windows 11, with notes where a step differs on Windows 10.

Before you start

A few things prevent most updates from failing in the first place, and they cost nothing to check:

• Reboot once. A clean restart clears a surprising number of stuck updates on its own, because a pending update often just needs the PC to finish a reboot it was waiting on.
• Stay on power and network. Keep a laptop plugged in and connected to Wi-Fi or Ethernet. A metered connection can also throttle downloads — check Settings › Network & internet if updates won't start.
• Give it time. Large feature updates can sit near a percentage for many minutes. Only treat it as "stuck" if there's been no progress for a good while.

Step 1 — Run the Windows Update troubleshooter

Windows ships a troubleshooter that checks the update services, permissions and cache for you and applies common fixes automatically. It is the right first move because it is safe and often enough on its own.

1. Open Settings (Windows+I).
2. Go to System › Troubleshoot › Other troubleshooters.
3. Under Most frequent, find Windows Update and click Run.
4. Let the wizard work through its checks and apply any fixes it recommends.
5. When it finishes, restart the PC, then go to Settings › Windows Update and click Check for updates again.

Step 2 — Pause updates, then resume

Pausing and resuming is an underrated fix. It makes Windows stop the current attempt, discard the half-finished state, and start the download fresh — often clearing an update that was wedged at a particular percentage.

1. Go to Settings › Windows Update.
2. Next to Pause updates, click Pause for 1 week (any duration is fine).
3. Restart the PC.
4. Return to Settings › Windows Update and click Resume updates.
5. Click Check for updates and let the download restart from scratch.

This is also the correct tool when a specific update is causing trouble and you simply want to defer it for a week while a fix ships — pausing holds all updates until the date you set or until you resume.

Step 3 — Check you have enough free disk space

Updates need room to download, expand and install. When the Windows drive is nearly full, updates commonly fail, hang, or roll back after restart — sometimes with a misleading error code. A routine quality update needs only a few gigabytes, but a large feature update can want roughly 20 GB or more of temporary space.

1. Open Settings › System › Storage and check the free space on the drive Windows is installed on (usually C:).
2. If it is tight, turn on or run Storage Sense, or open Cleanup recommendations, to clear temporary files and old update files.
3. For a deeper clean, press Windows+R, type cleanmgr and press Enter to open Disk Cleanup. Click Clean up system files and tick Windows Update Cleanup and any Previous Windows installation(s) entry.

Step 4 — Restart the Windows Update and BITS services

Windows Update relies on a small set of background services. If one of them hangs, updates stall no matter how many times you click Check for updates. Restarting them clears the jam.

1. Press Windows+R, type services.msc and press Enter.
2. Find Windows Update, right-click it and choose Restart (or Start if it is stopped).
3. Do the same for Background Intelligent Transfer Service (BITS), which handles the actual download.
4. And for Cryptographic Services, which verifies update packages.
5. Close Services, then check for updates again.

Prefer the command line? Open Terminal (Admin) and run:

net stop wuauserv
net stop bits
net stop cryptsvc
net start wuauserv
net start bits
net start cryptsvc

Those are the same three services Microsoft's own manual Windows Update component reset on Microsoft Learn stops first — bits, wuauserv and cryptsvc — before any deeper repair.

Windows 10 note: these service names are identical on Windows 10, so the same steps and commands apply.

Step 5 — Clear the SoftwareDistribution download cache

Windows stages every update download in C:\Windows\SoftwareDistribution. If a file in there is corrupted, the same update keeps failing until you clear it. Renaming or emptying the folder forces Windows to build a clean cache and re-download from scratch — this is the classic cure for repeated update errors.

1. Open Terminal (Admin) (right-click Start and choose Terminal (Admin)), and stop the services:

   net stop wuauserv
   net stop bits

2. Rename the cache so Windows treats it as gone but you keep a backup:

   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

   (Renaming is safer than deleting — if anything misbehaves you can rename it back.)
3. Restart the services:

   net start wuauserv
   net start bits

4. Go to Settings › Windows Update and click Check for updates. Windows recreates a fresh SoftwareDistribution folder and downloads again.
5. Once updates install cleanly, you can delete the leftover SoftwareDistribution.old folder to reclaim the space.

Clearing this cache resets your update history list, but it does not remove any installed updates, apps or personal files. If you also see certificate or signing errors, you can reset the update signature cache the same way by stopping cryptsvc and renaming C:\Windows\System32\catroot2, then restarting the service. That rename appears in Microsoft's own reset procedure as Ren %Systemroot%\System32\catroot2 catroot2.bak, alongside renames of the SoftwareDistribution\DataStore and SoftwareDistribution\Download folders.

Step 6 — Repair system files with SFC and DISM

If updates still fail after clearing the cache, the update machinery itself — the component store that Windows Update reads and writes — may be damaged. Two built-in tools repair it: DISM fixes the component store, and SFC (System File Checker) repairs protected system files. Run them in that order, because SFC uses the store that DISM repairs.

1. Open Terminal (Admin).
2. Repair the component store first. This contacts Windows Update for known-good files and can take several minutes:

   DISM /Online /Cleanup-Image /RestoreHealth

3. Then repair system files:

   sfc /scannow

4. Let each command finish completely, then restart the PC and check for updates once more.

These commands are identical on Windows 10 and Windows 11, and that order — DISM first, then sfc /scannow — is the sequence Microsoft prescribes in Fix Windows Update corruptions and installation failures. If DISM cannot reach Windows Update because the update service itself is broken, you can point it at a mounted Windows 11 ISO of the same version with the /Source: switch — but for most people the online repair above is enough.

Still failing? Note the error code

If you have worked through every step and updates still won't install, the specific error code on the Windows Update page is your best lead — it tells you whether the block is a download problem, a disk problem, or a specific package that failed. Search Microsoft's support site for that exact code before resorting to bigger measures like an in-place repair install (running Setup from a current Windows 11 ISO with Keep personal files and apps), which reinstalls Windows around your data and almost always clears a broken update pipeline.

Error code reference — what each code means and where to go

The hexadecimal code Windows Update shows is the fastest way to skip straight to the right step above instead of working through all six. Every code, meaning and fix in the table below is taken from Microsoft's common Windows Update errors reference. If your code isn't here, search Microsoft's support site for that exact code before trying anything drastic.