Fix Windows Error 0x80070002: Update File Missing Fast

Quick answer: Stop Windows Update service, delete the C:\Windows\SoftwareDistribution folder, restart the service, then run Windows Update again. That clears corrupted cache files causing the error.

Why This Happens

Error 0x80070002 shows up when Windows Update tries to install a file it can't find. This usually happens after a failed update attempt left behind a partial download or a corrupt cache. The real-world trigger: your PC restarted during an update, or you interrupted it manually. Now Windows thinks it has a file stored, but that file is missing or broken.

I've seen this on Windows 10 22H2 and Windows 11 23H2 the most. It's not a hardware issue — it's purely a software mismatch in the update cache.

Fix Steps

Before you start, make sure you're logged in as an administrator. These steps require full admin rights.

Open Command Prompt as admin. Click Start, type cmd, right-click Command Prompt, and select "Run as administrator." You'll see a User Account Control prompt — click Yes.
Stop Windows Update services. In the Command Prompt window, type these commands one at a time, pressing Enter after each:
```
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
```
You should see "The service is stopping" or "The service has been stopped" for each one. If a service doesn't stop, wait 30 seconds and try again. If it still won't stop, reboot in Safe Mode (with networking) and repeat.
Delete the SoftwareDistribution folder. Type this command and press Enter:
```
rmdir /s /q C:\Windows\SoftwareDistribution
```
This deletes the entire update cache. You won't see a confirmation message — that's normal. If you get "Access is denied," make sure you're running Command Prompt as admin and all services are stopped.
Restart the services. Type these commands one at a time:
```
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
```
Each should confirm "The service started successfully." If one doesn't start, check the Windows Event Viewer under Windows Logs > System for clues. Usually it's a permissions issue on a registry key — but that's rare.
Run Windows Update. Close Command Prompt. Go to Settings > Update & Security > Windows Update and click "Check for updates." Windows will rebuild the SoftwareDistribution folder from scratch. This time, the update should download fresh files and install without error 0x80070002.

Alternative Fixes If the Main One Fails

If the cache clear didn't work, try these in order:

Run System File Checker (SFC). Open Command Prompt as admin and type sfc /scannow. This checks all system files for corruption and replaces bad ones from a local cache. It takes 15-20 minutes. At the end, it'll say either "Windows Resource Protection did not find any integrity violations" or "Windows Resource Protection found corrupt files and successfully repaired them." If it finds issues, reboot and try Windows Update again.
Run DISM to repair the system image. Still in Command Prompt as admin, type DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store that Windows Update uses. It takes 20-30 minutes because it downloads fresh files from Microsoft. When it finishes, reboot and check for updates.
Use Windows Update Troubleshooter. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. Run it. It's a Microsoft-made tool that resets update components automatically. It's worth a shot, though I find the manual steps above work more reliably.

Prevention Tips

To avoid seeing this error again, never shut down your PC during an update. Let it finish — even if it sits at "Getting Windows ready, don't turn off your computer" for an hour. That screen is deceptive; the system is storing files in the background. If you force a shutdown, you risk corrupting the update cache.

Also, keep 10-15 GB free on your system drive (C:). Windows Update needs space to download and decompress files. If your disk is nearly full, updates fail and leave behind locked files that trigger 0x80070002 on the next attempt.

Bottom line: 0x80070002 is almost always a corrupted cache that needs to be nuked. The steps above have fixed it on hundreds of machines I've worked on. Stick with them.