Fix Error 0x80070002 on Windows 10

Error 0x80070002 on Windows 10 usually means Windows Update or the Microsoft Store cannot find a required file, often due to corrupted update cache or system files. The fix is to stop Windows Update services, clear the SoftwareDistribution and catroot2 folders, and then restart the services—this resolves the majority of cases.

What Causes Error 0x80070002?

This error code is a generic “file not found� error that Windows returns when an update or app installation process expects a file that is missing, corrupted, or locked. It commonly appears during Windows Update, but you may also see it when installing drivers, using the Microsoft Store, or running system maintenance tasks.

Typical triggers include:

• Interrupted downloads leaving incomplete update files in the cache.
• Corrupted system files or a damaged Windows Update database.
• Third-party antivirus or security software locking update files.
• Disk errors or low disk space preventing temporary files from being written.
• Outdated or conflicting drivers, especially after a major feature update.

Understanding the underlying cause matters because the fix differs slightly depending on whether the issue is a corrupted cache, a system file problem, or a conflict with security software. The steps below address the most common causes in order of likelihood.

Before You Start: Basic Checks

Run these quick checks first—they often resolve the error without deeper troubleshooting:

1. Restart your PC. A simple reboot clears temporary locks and may allow the update to proceed.
2. Check that you have at least 10 GB of free space on the drive where Windows is installed (usually C:). Updates need room for temporary files.
3. Run the Windows Update Troubleshooter: go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, select Windows Update, and run it.
4. Temporarily disable third-party antivirus or firewall software, then try the update again. Re-enable it immediately after.

If the error persists, proceed to the main fix below.

Main Fix: Clear the Update Cache

The most reliable fix is to reset the Windows Update components. This clears the temporary files where Windows stores downloaded updates and the database that tracks them. Follow these steps exactly:

1. Open Command Prompt as administrator: press Windows key, type cmd, right-click Command Prompt, and select Run as administrator.
2. Stop the relevant services by typing these commands one at a time, pressing Enter after each:

   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver

   If any service fails to stop, that’s okay—continue.

3. Rename the update cache folders. This preserves them as backups but forces Windows to create fresh ones:

   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old

   If you get an “access denied� error, double-check that you’re running as administrator and that the services are stopped.

4. Restart the services you stopped:

   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver

5. Restart your PC and try Windows Update again.

This process clears out any partially downloaded update files that Windows thinks are missing. It’s safe—Windows will re-download everything it needs.

If That Doesn’t Work: Run System File Checker

If the error persists, corrupted system files may be the culprit. Windows includes two tools to find and repair them:

1. Open Command Prompt as administrator again.
2. Run System File Checker by typing sfc /scannow and pressing Enter. This scans protected system files and replaces corrupted ones. It can take 10-15 minutes.
3. After it finishes, run DISM (Deployment Imaging Service and Management Tool) to repair the system image:

   DISM /Online /Cleanup-Image /RestoreHealth

   This downloads healthy system files from Windows Update. It may take several minutes.

4. Restart your PC and try the update again.

Running both tools in sequence is important: DISM fixes the underlying image that SFC relies on, so running SFC first and then DISM (or vice versa) may not fully resolve the issue. Do SFC first, then DISM, then SFC again if needed.

Other Common Fixes

If the cache reset and system file checks don’t solve it, try these in order:

• Check disk for errors: Run chkdsk /f in an elevated Command Prompt. You’ll be prompted to schedule it for the next restart—type Y and restart. This scans for and repairs file system errors that can cause “file not foundâ€� issues.
• Reset Windows Update components manually: Use the official Microsoft “Windows Update Resetâ€� script if you’re comfortable with PowerShell. It automates the steps above and also resets the Winsock catalog and proxy settings. You can find it on Microsoft’s support site—search for “Windows Update Reset script.â€�
• Install the update manually: If a specific update is failing, go to the Microsoft Update Catalog, search for the KB number (shown in Windows Update history), download the standalone installer, and run it. This bypasses the Windows Update client entirely.
• Perform a repair upgrade: If nothing else works, download the Windows 10 Media Creation Tool and choose “Upgrade this PC now.â€� This reinstalls Windows while keeping your files and apps, and it often fixes stubborn update issues. It takes about an hour.

How to Avoid This Error in the Future

While you can’t prevent every update glitch, these habits reduce the chances of seeing 0x80070002:

• Keep at least 15-20 GB free on your system drive.
• Don’t force-shut down your PC during updates. Let updates finish, even if they take long.
• Run Windows Update regularly rather than letting updates pile up for months.
• If you use third-party antivirus, exclude the C:\Windows\SoftwareDistribution folder from real-time scanning, or temporarily disable it during updates.
• Periodically run sfc /scannow and DISM as preventive maintenance.

Frequently Asked Questions

Will clearing the update cache delete my personal files?

No. The SoftwareDistribution and catroot2 folders contain only update-related temporary files and the update database. Your documents, photos, and installed apps are untouched. The only downside is that Windows must re-download updates that were already cached, which may take some time.

Why do I get error 0x80070002 when installing Microsoft Store apps?

The same underlying “file not foundâ€� issue can affect the Store. Try resetting the Store cache by running wsreset.exe (press Win+R, type it, press Enter). If that fails, use the same update cache reset steps above, as the Store shares the same update infrastructure. Also check that your system date and time are correct—incorrect time can cause certificate errors that manifest as 0x80070002.

Is error 0x80070002 dangerous?

No. It’s a standard Windows Update error, not a sign of malware or hardware failure. It simply means Windows couldn’t find a file it needed. The fixes above are safe and well-documented by Microsoft and the tech community.

Can I ignore this error if I don’t care about updates?

You can, but it’s not recommended. Windows Update delivers critical security patches. Ignoring the error leaves your PC vulnerable. Also, the same error can affect the Microsoft Store and driver installations, so it’s worth fixing even if you rarely update manually.

How long does the fix take?

The cache reset takes about 5-10 minutes, including a restart. Running SFC and DISM adds another 20-30 minutes. The repair upgrade takes about an hour. Most people resolve the issue with the cache reset alone.

What if the error appears during a feature update (like version 22H2)?

Feature updates are larger and more prone to file issues. Try the cache reset and SFC/DISM first. If the update still fails, download the ISO using the Media Creation Tool and mount it (double-click the ISO), then run setup.exe from within Windows. This performs an in-place upgrade and often succeeds where Windows Update fails.

Related

• How to Mount Your GPU Vertically in Any PC Case
• How to Check and Change NAT Type in Windows
• Bluetooth Speaker for Outdoor Events: How to Choose