How to Fix Windows Update Errors (0x80070002, 0x800f0922 and More)

Published 2026-10-14 · Marion Remote Fix

Windows Update failures usually come from a short list of causes: not enough free space, a corrupted download cache, damaged system files, or a single update that will not install on your machine. The error code tells you which one you are likely dealing with, so write it down before you start. You will find it under Settings > Windows Update > Update history.

What the common codes usually mean

Code	Usual meaning	Start with
0x80070002 / 0x80070003	Files the update expected are missing, often a damaged download	Reset update components
0x800f0922	Could not reach the update service, or the System Reserved partition is too small	Check VPN/network, then disk partitions
0x80070070	Not enough disk space	Free up space
0x800f081f / 0x800f0831	Component store is missing source files	DISM repair
0x80073712	A file Windows Update needs is damaged	DISM, then SFC
0x8024a105 / 0x80240034	Download failed or stalled	Restart, reset update components

Codes are hints, not diagnoses. If yours is not listed, the same sequence below still applies.

1. Restart and try again

Many updates need a restart to finish a previous update before the next one will install. Use Restart, not Shut down; with Fast Startup enabled, Shut down does not fully reset the system. Then go back to Windows Update and select Check for updates.

2. Make sure there is enough free space

Feature updates can need well over 20 GB of free space during installation. Open Settings > System > Storage and check the C: drive. Use Cleanup recommendations or Temporary files to remove old update files, previous Windows installations, and the Downloads folder contents you no longer need. Empty the Recycle Bin afterward.

3. Run the Windows Update troubleshooter

In Windows 11, open Settings > System > Troubleshoot > Other troubleshooters and run Windows Update. In Windows 10 it is under Settings > Update & Security > Troubleshoot > Additional troubleshooters. It resets some services and settings automatically. Restart and check for updates again.

4. Disconnect VPNs and pause third-party security tools

A VPN, a proxy, or an overly aggressive firewall can block the update servers and produce connection-type errors such as 0x800f0922. Disconnect the VPN, temporarily disable third-party antivirus (Microsoft Defender can stay on), and try again. Re-enable protection immediately afterward.

5. Reset the Windows Update components

This clears the download cache, which fixes most errors caused by a corrupted or half-finished download. Open Command Prompt as administrator and run these commands one at a time:

net stop wuauserv
net stop bits
net stop cryptsvc
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old
net start cryptsvc
net start bits
net start wuauserv

Windows rebuilds both folders automatically. Your update history list will look empty afterward, which is normal; the updates themselves are still installed. Restart and check for updates. Once everything works, you can delete the .old folders.

6. Repair system files with DISM and SFC

If updates fail with codes pointing to missing or damaged components, repair the Windows component store and then the system files. In an administrator Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth — this can sit at a percentage for a long time. Let it finish.
sfc /scannow — run this after DISM, not before, because SFC relies on the component store DISM just repaired.

Restart and try the update again.

7. Install the stuck update manually

If one specific update keeps failing, note its KB number from Update history. Search for that KB number in the Microsoft Update Catalog, download the package that matches your Windows version and system type (x64 or ARM64; check Settings > System > About), and run it. Manual installation often succeeds when Windows Update's own download keeps failing.

8. For feature updates that will not install

Moving to a new Windows version (for example, a new annual release of Windows 11) uses a different process than monthly patches. If it fails repeatedly:

Unplug external drives, USB hubs, and docks you do not need. Extra drives sometimes confuse the installer.
Update storage, chipset, and graphics drivers from the PC maker's support site.
Use Microsoft's Installation Assistant or the installation media tool, which performs an in-place upgrade that keeps your files and apps.

What not to do

Do not force power off during the Working on updates screen unless it has been frozen with no disk activity for several hours. Interrupting an install is a common way to end up with a PC that will not boot.
Do not use registry cleaners or random "update fixer" downloads. They add risk and rarely fix the actual cause.
Do not permanently disable updates. Security patches are the main thing protecting you from known attacks.

When to get help

If the PC rolls back after every update, gets stuck in a restart loop, or DISM reports that it cannot repair the component store, the next step is usually an in-place repair install. That is safe when done correctly, but it is worth having a current backup first.

Remote help from Marion Remote Fix

A Marion Remote Fix technician can connect to your computer, read the update logs to find the real cause, and run the repair steps for you while you watch. Most update problems can be resolved in a single remote session without anyone touching your files.