Quick answer: Delete the contents of C:\Windows\SoftwareDistribution and C:\Windows\System32\catroot2 folders, then run Windows Update again.
That error code pops up when Windows Update or the Microsoft Store can't find a file it expects. Usually it's because the update cache got corrupted or some system files are in a weird state. The culprit here is almost always a broken update cache, not a hardware issue. Don't bother reinstalling Windows over this.
Why You're Seeing 0x80070002
The error translates to "The system cannot find the file specified." Windows Update downloads packages to a temporary folder, then verifies and installs them. If that folder has stale or half-written files, the installer chokes and throws this error. You'll see it when installing cumulative updates, driver updates, or even apps from the Store. It's also common after a failed update attempt leaves remnants behind.
Fix 1: Reset the Update Cache (Most Likely Fix)
This clears out the junk that's confusing Windows Update. Takes about 10 minutes.
- Open an elevated Command Prompt. Right-click Start, choose "Command Prompt (Admin)" or "Windows PowerShell (Admin)".
- Stop the update services. Copy and paste these one by one, pressing Enter after each:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver - Rename the cache folders. Don't delete them just yet – renaming is safer. Do this:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 Catroot2.old - Restart the services:
net start wuauserv net start cryptSvc net start bits net start msiserver - Restart your PC and try Windows Update again.
If the update installs, you can delete the .old folders later to free up space. If it still fails, move on to the next fix.
Fix 2: Run System File Checker and DISM
Corrupted system files can also trigger this. SFC checks protected files, DISM fixes the image itself. Run both in order.
- Open an elevated Command Prompt again.
- Run
sfc /scannowand wait for it to finish. If it finds issues, reboot and try the update again. - If that doesn't work, run DISM:
This takes 15-20 minutes. Don't interrupt it.DISM /Online /Cleanup-Image /RestoreHealth - Reboot and retry the update.
DISM uses Windows Update to pull clean files, so you need a working internet connection. If it fails, you might need to specify a source, but that's rare.
Fix 3: Clear the Store Cache (For Store Apps)
If you're seeing this when installing apps from the Microsoft Store, reset the Store cache. Press Win + R, type wsreset.exe, hit Enter. A blank command window will pop up, then close. The Store will open again. Try your download once more.
Fix 4: Check Disk for Errors
Sometimes it's a disk issue – bad sectors or file system corruption. Run a quick check.
- Open an elevated Command Prompt.
- Run
chkdsk /f C:– it'll ask to schedule it on next reboot. Type Y and restart. - Let it run. It might take a while on larger drives.
- Then try the update again.
Alternative Fixes If Nothing Works
If you're still stuck, you've got a couple of options.
Use the Windows Update Troubleshooter
It's built into Windows and does most of what we did manually. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. Run it. It might catch something I didn't mention. Worth a shot, but I've seen it miss the root cause.
Manual Download of the Update
If you know which update is failing (check your Update History), go to the Microsoft Update Catalog and download it manually. Search for the KB number, grab the right version for your system, and run the installer. This bypasses the Windows Update client entirely.
System Restore
If you got a restore point from before this started, roll back. It's a sledgehammer but it works. Type "Create a restore point" in Start, click System Restore, and follow the prompts.
Prevention Tips
This error tends to come back if you force-shutdown during updates or if your disk runs out of space. Keep your system drive with at least 20GB free – Windows needs room to breathe. Also, don't skip updates for months and then install a giant pile at once. That's how you end up with weird errors.
If you're using third-party antivirus, it can interfere with Windows Update. Check if it has a "security update" feature that's blocking things. Have had that bite me more than once.
That's the whole playbook. Nine times out of ten, the SoftwareDistribution reset does the trick. Good luck.