Fix Error 0x80070002 in Windows Update

Error 0x80070002 in Windows Update means the system could not find a required file or folder, usually because of a corrupted update cache or a damaged system file. The fix is to stop the Windows Update service, clear the SoftwareDistribution and Catroot2 folders, and restart the service—this resolves the majority of cases in a few minutes.

What Does Error 0x80070002 Actually Mean?

Windows Update error 0x80070002 is a generic “file not found” error that appears when the update process tries to access a file that is missing or unreadable. The code maps to the system error ERROR_FILE_NOT_FOUND, which in the context of Windows Update typically points to a problem with the update cache or a corrupted system component.

You will usually see this error in the Windows Update settings page, sometimes accompanied by a message like “There were some problems installing updates, but we’ll try again later.” It can affect Windows 10 and Windows 11, and it often appears after a failed update attempt, a disk cleanup that removed update files, or an interruption during the update download.

Why Does This Error Happen?

The most common causes are:

Corrupted SoftwareDistribution folder – This folder stores temporary update files. If a download is interrupted or files become corrupted, Windows Update cannot find what it needs.
Corrupted Catroot2 folder – This folder holds the update signature catalog. Damage here can cause update verification to fail.
System file corruption – Essential Windows files may be damaged, preventing the update service from functioning correctly.
Third-party antivirus interference – Some security software locks or quarantines update files, causing the error.
Disk space issues – If the system drive is full, Windows cannot write temporary update files.

How to Fix Error 0x80070002 (Step-by-Step)

Follow these steps in order. The first method resolves most cases; the later ones address less common causes.

Method 1: Clear the Windows Update Cache

Press Windows + R, type services.msc, and press Enter.
Scroll to Windows Update, right-click it, and select Stop.
Also stop Background Intelligent Transfer Service (BITS).
Open File Explorer and navigate to C:\Windows\SoftwareDistribution. Delete all files and folders inside (if some are in use, skip them and reboot, then try again).
Go to C:\Windows\System32\catroot2 and delete its contents as well.
Return to Services, right-click Windows Update and BITS, and select Start.
Restart your PC and try Windows Update again.

Method 2: Run the System File Checker (SFC)

Open Command Prompt as administrator (search for “cmd”, right-click, and choose “Run as administrator”).
Type sfc /scannow and press Enter. This scans and repairs protected system files.
Wait for the scan to complete (it may take 10-15 minutes). If it finds issues, restart and run it again.

Method 3: Use DISM to Repair System Image

In the same administrator Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth.
This command repairs the Windows system image. It can take up to 20 minutes.
After it finishes, run sfc /scannow again.

Method 4: Check Disk for Errors

Open Command Prompt as administrator.
Run chkdsk C: /f. If prompted to schedule a check on next reboot, type Y and restart.

Method 5: Temporarily Disable Antivirus

If you have third-party antivirus, disable its real-time protection temporarily and try the update. Re-enable it immediately after. If the update succeeds, add an exception for the Windows Update folders.

Common Mistakes to Avoid

Deleting the entire SoftwareDistribution folder – It is safe to delete its contents, but the folder itself must remain. Windows recreates it automatically, but deleting the parent folder can cause issues.
Skipping the service stop – If you try to delete files while Windows Update is running, some files will be locked and the fix won’t work.
Not running SFC after clearing cache – The error can return if system files are still corrupted.
Using a third-party “fixer” tool – These often do more harm than good. Stick to built-in Windows tools.

What If the Error Persists?

If you have tried all the methods above and the error remains, consider these additional steps:

Run the Windows Update Troubleshooter – Go to Settings > System > Troubleshoot > Other troubleshooters, and run the Windows Update troubleshooter.
Reset Windows Update components manually – This is a more thorough version of Method 1. You can find official Microsoft guidance, but the steps are essentially: stop BITS and Windows Update, rename the SoftwareDistribution and Catroot2 folders (instead of deleting), restart the services, and reboot.
Perform an in-place upgrade repair – Download the Windows 11 or Windows 10 Installation Assistant from Microsoft’s website and run it. This reinstalls Windows while keeping your files and apps. It often fixes stubborn update issues.

Frequently Asked Questions

Will clearing the SoftwareDistribution folder delete my personal files?

No. The SoftwareDistribution folder only contains temporary update files. Your documents, photos, and other personal data are not stored there, so deleting its contents is safe.

Can I fix error 0x80070002 without admin rights?

No. Stopping services and deleting system folders requires administrator privileges. You must be logged in as an administrator or know the admin password.

How long does the SFC scan take?

Typically 10-15 minutes, but it can take longer on older or heavily fragmented drives. Do not interrupt it; let it finish.

Is this error dangerous or a sign of a virus?

No. It is a common Windows Update issue caused by file corruption or cache problems. It is not a security threat, but it can prevent your system from receiving important security updates, so it should be fixed promptly.

Will this error affect my installed programs?

No. The error only affects Windows Update’s ability to download and install updates. Your existing programs and files are not affected.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →