Windows Update failures usually fall into one of three buckets: corrupted download cache files, a stopped or misconfigured update service, or damaged system component stores — and clearing all three takes about 40 minutes on Windows 11 24H2. The single most common error you'll see, 0x80070002, means the update payload never finished writing to disk, not that Microsoft's servers are down. Work through the steps below in order; each one eliminates a class of failure before you move to the next.

The reason order matters here is cost. A full in-place upgrade repair, the heaviest fix on the list, typically consumes 60–90 minutes on a mid-range laptop with a 512 GB SSD because it re-writes the system partition while preserving apps and files. Running it first when a five-minute service reset would have solved the problem wastes an afternoon. The sequence below is arranged cheapest to most expensive, and roughly two in three failures resolve before you reach Step 5.

One boundary before you start: if Windows Update throws a hardware-adjacent code such as 0x80070070 (insufficient disk space) or an OEM driver conflict, these steps may clear the symptom without fixing the cause. Check that 20 GB or more is free on the system drive first — Microsoft's documented baseline for a feature update — and note any error codes exactly as shown. The code drives the diagnosis.

Symptom or code Most likely cause Jump to
0x80070002 Missing or corrupt update download Step 3
0x80073712 Corrupted component store Step 6
0x80070422 Update service disabled Step 4
"We couldn't connect" Network or proxy misconfiguration Step 2
Update hangs at a percentage Stalled service or software distribution lock Steps 3–4

Step 1: Confirm the Failure Is Actually Windows Update

Pull the exact error code before touching anything. Open Settings > Windows Update > Update history and look at the failed entry; the code sits beneath the update name. You can also run Get-WindowsUpdateLog in an elevated PowerShell window, which writes a consolidated log to your desktop — it takes a minute to compile and is dense, but the error code near the bottom is authoritative.

Write the code down. Windows Update error codes are hex values that decode to a Win32 error, and the last four digits are the useful part. 0x80070002 maps to "file not found," 0x80070005 to "access denied," and 0x80070070 to "insufficient disk space." That last one tells you to stop troubleshooting and free capacity.

Check free space on the system drive now. A feature update needs roughly 20 GB free, and cumulative updates need several gigabytes of scratch space even on a small patch. Open Settings > System > Storage and read the figure at the top; don't estimate.

If the code is a driver-specific failure, note the device name. Windows Update sometimes fails on an optional driver package from your OEM while system patches install fine, and that's a separate problem from a broken update pipeline — you'd handle it through Device Manager rather than the steps below.

Step 2: Rule Out Network and Metered Connection Blocks

As a first test, switch off any VPN or third-party firewall for one update attempt. Corporate VPN clients and some antivirus web shields intercept the delivery endpoints and cause "we couldn't connect" errors that look identical to server outages. Disconnect, then retry the update.

Next, verify Windows isn't treating your connection as metered. Open Settings > Network & internet > Wi-Fi > your network, and check "Metered connection." If it's on, Windows suppresses most automatic downloads. Turn it off and retry.

If you're behind a proxy, confirm it under Settings > Network & internet > Proxy. Auto-detect settings occasionally fail on networks that require an explicit script address. Ask your network administrator for the correct PAC file or server address rather than guessing.

Run the built-in network troubleshooter as a quick sanity pass: Settings > System > Troubleshoot > Other troubleshooters > Network and Internet > Run. It resets the adapter and flushes DNS, which clears a surprising number of transient "check your connection" failures.

Step 3: Clear the SoftwareDistribution and catroot2 Caches

This is the workhorse fix, and it addresses 0x80070002 directly. The SoftwareDistribution folder holds downloaded update packages; catroot2 holds the catalog signatures that validate them. Stale files in either place poison subsequent attempts. Clearing them forces a clean re-download.

1: Open Command Prompt as administrator (search "cmd," right-click, Run as administrator). 2: Type net stop wuauserv and press Enter. 3: Type net stop bits and press Enter. 4: Type net stop cryptsvc and press Enter. 5: In File Explorer, navigate to C:\Windows\SoftwareDistribution and delete every file and folder inside it (keep the folder itself). 6: Navigate to C:\Windows\System32\catroot2 and delete its contents the same way. 7: Back in Command Prompt, type net start cryptsvc, then net start bits, then net start wuauserv. 8: Return to Settings > Windows Update and click Check for updates.

If the deletion fails with "file in use," a background service is still holding a handle. Reboot and repeat steps 2 through 4 before deleting again. If catroot2 won't empty even after a reboot, run sfc /scannow first — a corrupt system file can lock the catalog folder.

Step 4: Restart Windows Update Services From Scratch

A service left in a disabled or manual start state blocks updates silently. This check catches 0x80070422, which literally means "the service cannot be started." Verify the three services that matter by opening services.msc.

Service name Display name Startup type Status
wuauserv Windows Update Manual (Trigger Start) Running
bits Background Intelligent Transfer Service Manual Running
cryptsvc Cryptographic Services Automatic Running

Double-click each entry, confirm the startup type matches the table, and click Start if the status is blank. Anything set to Disabled must be changed — it will never start on demand. On Windows 11 24H2 the Windows Update service is set to Manual (Trigger Start) by design, so seeing "Manual" is correct, not a fault.

After changing anything, reboot once. Service state changes sometimes don't take until the next boot, and testing before rebooting produces a false negative that sends people down the wrong path.

If a service refuses to start, open Event Viewer (Windows Logs > System), filter for the service name, and read the error. A dependency failure usually names the missing service directly, which is faster than guessing.

Step 5: Run the Built-In Update Troubleshooter

Microsoft still ships a dedicated Windows Update troubleshooter, though it's buried. Go to Settings > System > Troubleshoot > Other troubleshooters and click Run next to Windows Update. On Windows 11 it only clears a narrow set of conditions — stuck services, a corrupted cache, or a bad registry entry for the update client.

Give it ten minutes. The troubleshooter often reports "fixed" while changing nothing visible, so verify by re-checking for updates afterward rather than trusting the message. Its repair log lives under Settings > System > Troubleshoot > View history, which shows what it actually adjusted.

The troubleshooting tool is worth running because it resets the update client configuration to defaults — a benefit the manual steps above don't fully replicate. It won't fix component store corruption or disk errors.

Step 6: Repair the Component Store With DISM and SFC

Run this when the cache clear and service reset fail, and specifically when you see 0x80073712, which indicates the component store is damaged. DISM repairs the image Windows Update relies on; SFC repairs individual protected files. Run DISM first — it's the broader fix.

1: Open Command Prompt as administrator. 2: Type DISM /Online /Cleanup-Image /CheckHealth and press Enter. This reads the image state quickly and reports whether corruption exists. 3: Type DISM /Online /Cleanup-Image /ScanHealth and press Enter. This takes 10–20 minutes and scans thoroughly. 4: Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs what it finds, pulling replacement files from Windows Update if local sources are absent — which means it needs a working internet connection. 5: When DISM finishes, type sfc /scannow and press Enter. This takes 5–15 minutes. 6: Reboot and retry Windows Update.

If RestoreHealth fails at 84.9% — a well-known stall point — point DISM at a clean source. You can mount a Windows 11 ISO and run DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess, replacing E: with the mounted ISO's drive letter. This bypasses the network entirely and works on machines where the update pipeline itself is the broken part.

Step 7: Reset Windows Update Components With a Script

When individual fixes keep reverting, reset the whole stack. A batch file rebuilds the update registry keys, re-registers the DLLs, and resets the service configuration in one pass. Microsoft's support documentation lists the DLLs involved, including atl.dll, urlmon.dll, mshtml.dll, shdocvw.dll, browseui.dll, and wuapi.dll — re-registering them clears the "update client won't launch" failures that manual steps miss.

Create a .bat file with these commands, run it as administrator, then reboot:

If the script errors on a DLL that's missing from your build — some are absent on newer Windows 11 editions — skip that line. A single failed registration won't block the rest. After the reboot, check for updates once and let it run for at least 15 minutes before concluding anything; the reset pipeline sometimes takes two full cycles to show patches.

Step 8: Use the In-Place Upgrade as the Safe Heavy Fix

The in-place upgrade reinstalls Windows over itself, keeping files, apps, and settings. It's the correct escalation when DISM can't repair the image and 0x80073712 persists, and it takes 60–90 minutes on typical hardware. You must have roughly 20 GB free and a stable power source.

Download the Windows 11 Installation Assistant from Microsoft's software-download page for your edition, run it, and choose Keep personal files and apps when prompted. Do not choose "Nothing" unless you've already backed up. The assistant checks compatibility first and blocks hardware that doesn't meet the Windows 11 requirements list — TPM 2.0, Secure Boot capability, and a supported CPU.

If the assistant refuses to run, mount the ISO manually and launch setup.exe from the root. Choose Change what to keep on the "Ready to install" screen and confirm Keep personal files and apps appears. The installer will skip the compatibility check only if you run it from within a working Windows session, which itself removes one failure mode.

Back up first, even though files are preserved. In-place upgrades fail rarely, but the recovery path after a failed one is a clean install, and that path erases everything. Copy your documents and browser profiles to an external drive before starting.

Fix Time cost Risk Resolves
Cache clear (Step 3) 10 min Low 0x80070002, stuck downloads
Service reset (Step 4) 5 min Low 0x80070422, disabled services
DISM/SFC (Step 6) 30 min Low 0x80073712, corrupt store
Script reset (Step 7) 10 min Medium Reverted update client config
In-place upgrade (Step 8) 60–90 min Medium Persistent image corruption

Step 9: Check Disk Health and Free Space Before Anything Else

A failing drive causes update failures that mimic software problems. Run chkdsk C: /f /r in an elevated Command Prompt when updates fail repeatedly with no clear error, and let it complete — it can take an hour or more and requires a reboot. Sector errors show up here, and if chkdsk reports bad sectors, stop troubleshooting Windows Update and back up your data.

Disk space deserves a separate look. A machine with under 10 GB free on the system drive will fail feature updates on 0x80070070 every time, and clearing the download cache won't touch that. Use Settings > System > Storage > Temporary files to remove the previous installation's Windows.old folder (typically 10–20 GB), delivery optimization files, and old update logs.

If your device uses a mechanical drive, expect large feature updates to take considerably longer and to fail more often due to timeouts. On a 5400 RPM laptop drive, a 24H2 feature update can run past two hours, and Windows may abort the operation on its own timer. Moving to an SSD is the durable fix for that class of failure.

How to Read Error Codes Without Guessing

Decode the code before you act; the number names the fault class. The hex error 0x80070002 is a file-level miss, 0x80070005 is an access denial that often traces to an antivirus quarantine, 0x80070070 is disk space, and 0x80073712 is component store damage. Microsoft's support site maintains the authoritative list, and any code you can't decode there should be reported to support rather than guessed at.

Search the code verbatim rather than paraphrasing it. Support threads for 0x8007000E are a different problem from 0x80070002, and the difference is one digit. Copy-paste the exact string from Update history.

Don't confuse Windows Update codes with Windows Installer codes. A Microsoft Store app update failing with 0x80070005 needs the Store reset (wsreset.exe), not the Windows Update fixes above. The pipelines are separate even though the codes overlap.

If a code persists across all nine steps, contact Microsoft support and give them the code plus the DISM log (C:\Windows\Logs\DISM\dism.log). That log tells support exactly what the repair attempted, which speeds up the case considerably, especially if you include the output from Get-WindowsUpdateLog.

FAQ

How long should a full Windows Update repair take?

Plan for roughly 45 minutes using Steps 1–4, and up to two and a half hours if you go all the way to the in-place upgrade, because the 60–90 minute upgrade time follows the earlier DISM and SFC passes. Running the cache clear alone is about 10 minutes including the service stops and restarts. Time-box your own effort: if four hours of troubleshooting hasn't produced a working update, escalate to Microsoft support.

Will clearing the SoftwareDistribution folder delete my files or installed programs?

No. The SoftwareDistribution folder contains only downloaded update packages and their metadata; deleting its contents removes nothing you installed and touches no personal documents. Windows rebuilds the folder automatically the next time you check for updates, and that rebuild is the point of the fix. The only cost is re-downloading any patches that were partially delivered.

Why does my update hang at the same percentage every time?

A repeated stall at the same percentage points to a specific package failing to apply, not a general network problem. The most common cause is a driver package that conflicts with an existing OEM driver, and the fix goes through Device Manager rather than Windows Update — update the device driver from the manufacturer's site first. A repeated hang at 0% is different: that's usually a stopped bits service.

Can I skip Windows Update and stay on an older build?

Yes, temporarily — you can pause updates for up to five weeks in Settings > Windows Update, and on Windows 11 Pro you can defer through Group Policy. However, once a build reaches end of servicing, Microsoft stops shipping security patches for it, and that's a genuine risk rather than an inconvenience. Deferring for a week while you troubleshoot is sensible; deferring for a year is not.

Does a VPN break Windows Update?

Sometimes. A VPN routes update traffic through an endpoint that some delivery networks rate-limit or block, producing "we couldn't connect" errors while the rest of your internet works normally. Disconnect the VPN, retry, and if the update succeeds, reconnect afterward. Split tunneling, where available, lets you exclude Windows Update traffic from the tunnel and avoid the problem permanently.

What if the in-place upgrade fails too?

That narrows the fault to hardware or firmware. Check drive health with chkdsk, verify RAM with Windows Memory Diagnostic (search for it in Start), and confirm your OEM firmware is current. A machine that fails both a component store repair and an in-place upgrade usually has a drive or memory fault, and no amount of software repair will clear it.

Is 0x80073712 always a corruption problem?

Almost always — it means a required component store file is missing or unreadable. The occasional exception is a failed previous update that left the store in an inconsistent state, which a simple cache clear sometimes resolves before DISM is needed. Try Step 3 first if you see this code; the cost is only ten minutes.

Can I fix this without Command Prompt?

Partially. The Settings-based troubleshooter and a connection check clear some failures, and Windows 11's Settings > Windows Update > Troubleshoot has improved since earlier versions. The cache clear, DISM, and component registration all need an elevated command line, though, and those are the fixes that resolve the majority of persistent errors. Running Windows Terminal as administrator is the shortcut.

Repairing Windows Update is unglamorous work, but the sequence above is reliable because it spends the cheap fixes first. Track the error code, clear the cache, reset the services, repair the store, and escalate to an in-place upgrade only when the earlier steps prove insufficient.