Windows Update Error 0x80070002 – Missing Files Fix

You're trying to install a Windows Update, maybe a monthly security rollup or a feature update like 22H2. The progress bar gets to about 30%, then stops. A few minutes later you see the error: 0x80070002 – ERROR_FILE_NOT_FOUND. This happens most often after a failed update attempt left broken files behind, or if you've manually deleted the SoftwareDistribution folder without stopping the update service first.

What's Actually Causing This

The error code 0x80070002 means the Windows Update service looked for a specific file (like update.cab or express.psf) in the C:\Windows\SoftwareDistribution\Download folder, and it didn't find it. That folder holds temporary update files. If a previous download got interrupted, or if you ran a disk cleanup that trimmed those files, the update can't finish.

The fix isn't complicated, but you have to do it in the right order. Skip a step, and the problem comes back. Here's the process I've used on hundreds of machines—Windows 10 and 11 both.

Step-by-Step Fix

Step 1: Stop the Windows Update Service and Background Intelligent Transfer Service

1. Press Windows Key + R, type services.msc, hit Enter.
2. Find Windows Update in the list. Right-click it, choose Stop. The status should change to Stopped.
3. Find Background Intelligent Transfer Service (BITS). Right-click it, choose Stop.
4. Leave the Services window open—you'll need to restart these later.

What to expect: Both services stop immediately. You might see a brief spinner, then the status goes blank (no Running text). That's correct.

Step 2: Delete the SoftwareDistribution Folder Contents

1. Open File Explorer. Go to C:\Windows\SoftwareDistribution.
2. Inside, you'll see folders like Download, DataStore, SelfHost. Do not delete the entire SoftwareDistribution folder—only its contents. If you delete the folder itself, Windows will recreate it later, but you might get permission errors.
3. Select all items inside (Ctrl+A), then press Shift+Delete to permanently remove them. Confirm if asked.

What to expect: Some files might give a “file in use” error. That's fine—skip those. We'll clean them in the next step.

Step 3: Clear the Catroot2 Folder (Carefully)

1. Navigate to C:\Windows\System32\catroot2.
2. Delete everything inside that folder. Again, do not delete the catroot2 folder itself—only the files and subfolders inside it.
3. If you get permission errors, you may need to take ownership. But usually, with services stopped, it works.

Why this matters: Catroot2 stores update signatures. Corrupted signatures here can trigger the same error.

Step 4: Run System File Checker (SFC) and DISM

1. Open Command Prompt as Administrator. (Search for cmd, right-click, Run as administrator.)
2. Type sfc /scannow and press Enter. This checks all protected system files and replaces bad ones from a local cache.
3. Wait for it to finish. It can take 15–30 minutes. Don't close the window. You'll see a progress percentage.
4. When SFC completes, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This uses Windows Update to fix the component store.
5. Let DISM finish—it can take 20–40 minutes. If it sticks at 62% for a while, that's normal. Let it run.

Expected outcome: SFC should say “Windows Resource Protection found corrupt files and successfully repaired them.” DISM should say “The restore operation completed successfully.” If either says it couldn't fix something, run both again.

Step 5: Restart the Services You Stopped

1. Go back to the Services window.
2. Right-click Windows Update, choose Start.
3. Right-click Background Intelligent Transfer Service, choose Start.
4. Close Services.

Now restart your PC. A full reboot clears any leftover locks on files.

Step 6: Try the Update Again

1. Go to Settings > Windows Update > Check for updates.
2. Windows will download the update fresh. The progress bar should now go smoothly past the 30% mark.
3. If it asks to restart, do it.

Still Failing? Here's What to Check Next

If you still see error 0x80070002 after following all the steps, there are two less common but real possibilities:

• Third-party antivirus interference. Temporarily disable your antivirus (not just Windows Defender) and try the update again. I've seen Norton and McAfee block file downloads during updates.
• Disk space. Open File Explorer and check C: drive free space. Windows Update needs at least 10 GB free. If you're low, delete old Windows Update cleanup files using Disk Cleanup (run cleanmgr, select Windows Update Cleanup).
• Corrupted system drive. Run chkdsk C: /f /r from an admin command prompt. It will schedule a scan on next reboot. Restart and let it run—it can take hours. This fixes bad sectors that corrupt update files.

Most of the time, steps 1–6 clear the error. The process takes about an hour total, but it's the only reliable way I've found across dozens of machines. Don't skip the SFC/DISM part—that's where the real repair happens.