Skip to the content
The Update Bureau
Guide · Fix & Manage Updates Repair & Error Codes Windows 11 & 10

How to fix a Windows update that fails or gets stuck

Step-by-step fixes for an update that will not install or stops halfway, from the built-in troubleshooter to repairing the component store, plus what the common error codes mean.

All guides Check active Known Issues →

An update that fails, rolls back or sits at the same percentage for hours is rarely a sign of a broken PC. Most of the time Windows Update just needs a restart, a repair of its own files or a fresh download cache. Work through the steps in this order and stop when the update installs. First check the update's page on this site: its Known issues section may already name your problem (see known issues).

1. Run the troubleshooter

  1. Restart the PC and try Check for updates again.
  2. On Windows 11 open Settings › System › Troubleshoot › Other troubleshooters and select Run next to Windows Update. On Windows 10 it is under Update & Security › Troubleshoot › Additional troubleshooters.
  3. Restart when it finishes and check for updates again.

You can jump straight to the page with ms-settings:troubleshoot (press Win + R).

2. Repair Windows system files

Open Command Prompt as administrator (right-click, then Run as administrator) and run these two commands, in this order, then restart:

Command Prompt (Admin)
> DISM.exe /Online /Cleanup-Image /RestoreHealth> sfc /scannow

DISM repairs the component store, the library Windows takes its update files from. SFC then replaces damaged system files from it. Microsoft advises running DISM first. If Windows Update itself is broken, DISM can read a healthy copy of Windows instead: add /Source:<path> /LimitAccess.

3. Reset the update cache (IT admins and advanced users)

Stop the services, rename the cache folders so Windows rebuilds them, then start the services again:

Command Prompt (Admin)
> net stop wuauserv> net stop bits> net stop cryptsvc> ren %systemroot%\SoftwareDistribution\DataStore DataStore.bak> ren %systemroot%\SoftwareDistribution\Download Download.bak> ren %systemroot%\system32\catroot2 catroot2.bak> net start cryptsvc> net start bits> net start wuauserv

Nothing personal is deleted. If the same error comes back, the log is %windir%\Logs\CBS\CBS.log.

What the common error codes mean

Code Meaning What to try
0x80070002 "The system cannot find the file specified." Step 3, then step 2.
0x800f081f Source files missing: the component store is damaged. Step 2.
0x800f0922 Installation failed and was rolled back. Check CBS.log; Microsoft documents a permissions cause on Windows Server 2016 (the spp folder).
0x80073712 "The component store has been corrupted." Step 2.
0x80240034 The update failed to download. Check the connection or proxy, then step 3.

If nothing works

You can install the update by hand or, if a recent update caused the trouble, uninstall it. Find the KB number in update history.

Sources

Edited by the site editor. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake