Windows Update Error 0x80070002 Stuck at Downloading? Fixed
This error pops up when Windows Update can't find a file it needs. Here's the direct fix and why it works.
Getting 0x80070002 when Windows Update hangs at "Downloading 0%" is frustrating. I've seen this on Windows 10 22H2 and Windows 11 23H2. The core cause is almost always corrupted or missing files in the update cache. Here's the fix that works.
The Quick Fix: Reset Windows Update Components
This is the fix I've used on hundreds of machines. It forces Windows to rebuild the update cache from scratch.
- Press Windows Key + X and select Windows Terminal (Admin) or Command Prompt (Admin). Click Yes on the UAC prompt.
- Stop the Windows Update services by running these commands one at a time. Each one should say "service stopped successfully":
If a service says "not running" — that's fine, move on.net stop wuauserv net stop cryptSvc net stop bits net stop msiserver - Rename the two cache folders. These hold the corrupted data:
You won't see a success message after renaming — that's normal. Just type the next command.ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 Catroot2.old - Restart the services you stopped earlier:
Each should say "service started successfully."net start wuauserv net start cryptSvc net start bits net start msiserver - Close the Command Prompt. Then restart your PC — don't skip this restart, it flushes pending changes.
- After restart, go to Settings > Windows Update and click Check for updates. The download should start fresh, and the error should be gone.
Why This Works
Windows Update stores downloaded update files in two folders: SoftwareDistribution and Catroot2. When a download gets interrupted — say your PC crashed mid-update, or you lost internet — those files can end up corrupted or incomplete. Next time Windows tries to update, it sees a file that's named right but has wrong data, throws 0x80070002, and gives up.
By renaming those folders (not deleting — renaming gives you a fallback if something goes wrong), you force Windows to create fresh folders with clean files. The old corrupted folders stick around as .old — you can delete them after a week if everything works fine.
Less Common Variations
Sometimes the basic reset doesn't cut it. Here are the edge cases I've run into:
Corrupted System Files Blocking the Reset
If you get errors when stopping services or renaming folders, run these in order after step 2:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
DISM takes 5-15 minutes — let it finish. Then run SFC. After that, repeat the fix from step 3. I've seen this fix a stubborn case on a Dell Latitude 5420 running Windows 11 23H2.
Update Troubleshooter — Worth a Shot
Go to Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters (Windows 10). Run the Windows Update troubleshooter. It'll reset the same services and folders automatically, plus clear some BITS cache. It's less thorough than manual, but if you're not comfortable with commands, start here.
Time Sync Issues
Believe it or not, wrong system time can cause 0x80070002. Windows Update checks certificate validity against your PC's clock. If the time's off by more than 5 minutes, the update fails. Go to Settings > Time & Language > Date & time. Toggle "Set time automatically" off, wait 10 seconds, toggle it back on. Then sync manually: click Sync now. Restart and try updates again.
Third-Party Antivirus Conflict
I've seen Norton, McAfee, and even Malwarebytes Premium block Windows Update downloads. They sometimes quarantine or block update files they think are suspicious. Temporarily disable your antivirus (not uninstall — just disable real-time protection for 15 minutes), run Windows Update, then re-enable it. If it works, check your antivirus logs for blocked files and whitelist Windows Update paths.
Prevention
Here's how to avoid this in the future:
- Don't force shutdown during updates. If Windows says "Updating — don't turn off your PC," don't. Even if it's stuck — wait 2 hours before forcing a restart. Most stuck updates resolve themselves.
- Keep 20GB free space on your system drive. Windows needs room to download and unpack updates. A full drive can corrupt the download.
- Schedule updates outside peak usage. Set active hours in Settings > Windows Update > Advanced options so Windows doesn't restart mid-download.
- Run a monthly manual check. Every 4 weeks, go to Windows Update and click "Check for updates." Let it finish. This keeps the update pipeline clean.
That's it. You'll probably never see 0x80070002 again if you do this. I haven't seen it on my own machine in over three years.
Was this solution helpful?