Error 0x80070002 is Windows Update’s way of saying it reached for a file that was not there. The update downloads, starts installing, and then fails with this code, sometimes repeatedly for the same update. It is one of the most common Windows 11 update errors, and it is also one of the most fixable, because the cause is almost always local: corrupted cached files, a damaged update database, or a broken component store.
The fixes below target those causes directly. They start with the update troubleshooter and the cache clear that resolves most cases, then move to the deeper repairs for stubborn ones. None of them touch your personal files.
Why this happens
- Corrupted update cache. Downloaded update files in the SoftwareDistribution folder get damaged, and every retry uses the same broken files.
- Damaged component store. The WinSxS store that Windows Update draws from is corrupted, so files it needs are missing.
- Interrupted downloads. A dropped connection or a shutdown during download leaves partial files that fail verification.
- Antivirus interference. Security software can quarantine or block update components as they download.
- Disk errors. Bad sectors corrupt the files Windows Update writes to disk.
- Wrong system time. Update servers reject requests when the clock is far off, producing confusing errors.
- Corrupted update database. The DataStore that tracks which updates are installed gets damaged and misreports state.
- Metered connection interruptions. On metered or unstable connections, Windows may pause and resume downloads in ways that leave the cache inconsistent, especially with large feature updates.
How to fix it
Work through these in order, starting with the quickest fixes first.
Fix 1: Run the Windows Update troubleshooter
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Click Run next to Windows Update.
- Let it diagnose and apply fixes. It commonly repairs the update database and restarts the necessary services.
- Try the update again from Settings > Windows Update.
Fix 2: Clear the SoftwareDistribution cache
This is the definitive fix for corrupted cached files, and it resolves the majority of 0x80070002 cases on its own.
- Press Windows key + X and open Terminal (Admin).
- Stop the update services with these commands, one at a time:
net stop wuauserv,net stop bits,net stop cryptSvc. Wait for each to confirm it stopped before running the next. - Delete the cache contents:
rd /s /q C:\Windows\SoftwareDistribution. This removes only temporary update files, never your data. - Restart the services:
net start wuauserv,net start bits,net start cryptSvc. - Open Settings > Windows Update and click Check for updates. Windows downloads fresh copies of everything, which takes a few minutes on slower connections.
Fix 3: Repair the component store and system files
- In an elevated Terminal, run
DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store that updates draw from. - When it finishes, run
sfc /scannowto fix protected system files. - Restart the laptop and retry the update. A damaged component store is the most common reason Fix 2 alone does not work.
Fix 4: Check the date, time, and disk health
- Open Settings > Time & language > Date & time. Turn on Set time automatically and click Sync now.
- In an elevated Terminal, run
chkdsk C: /f. Type Y to schedule it and restart. - Disk errors that corrupt downloaded files will keep producing this error until the disk is checked. If chkdsk finds many bad sectors, the drive itself may be failing.
Fix 5: Temporarily disable third-party antivirus
- Open your antivirus settings and disable real-time protection temporarily.
- Retry the Windows update.
- Re-enable protection immediately afterward. If the update succeeds with protection off, add the Windows Update folders to your antivirus exclusions or switch to Windows Security, which never conflicts with updates.
Fix 6: Install the update manually from the catalog
When the automatic process keeps failing, go around it.
- Note the update’s KB number from Settings > Windows Update > Update history.
- Visit the Microsoft Update Catalog and search for that KB number.
- Download the version matching your system, x64 for most laptops, and run the installer.
- Manual installation bypasses the corrupted automatic pipeline entirely. Keep the downloaded file until the update shows as installed, in case you need to retry.
Fix 7: Check the drive’s SMART health
If 0x80070002 keeps returning no matter how many times you clear the cache, the drive itself may be damaging every file it writes.
- In an elevated Terminal, run
wmic diskdrive get status. It should say OK. Anything else means the drive is reporting its own failure. - For more detail, check your SSD maker’s toolbox software (Samsung Magician, Crucial Storage Executive, WD Dashboard) and look at the drive health percentage.
- A drive below 80 percent health, or one logging reallocated sectors, will keep corrupting update downloads until it is replaced. No amount of cache-clearing fixes a drive that damages data on write.
Fix 8: Reset the Windows Update components
- In an elevated Terminal, stop the services:
net stop wuauserv,net stop bits,net stop cryptSvc,net stop msiserver. - Rename the cache folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old. - Restart the services:
net start wuauserv,net start bits,net start cryptSvc,net start msiserver. - Check for updates again. This is a deeper reset than Fix 2 and handles database corruption.
Fix 9: Repair Windows in place
- Go to Settings > System > Recovery > Fix problems using Windows Update. This reinstalls the current Windows version while keeping files and apps.
- If that option is unavailable, download the Windows 11 ISO from the Windows 11 download page , mount it, and run setup, choosing to keep files and apps.
- Related update errors: error code 0x80070057 fix and the Windows 11 install error on Lenovo laptops . Microsoft’s update help is on the Microsoft support site .
Closing
Error 0x80070002 is annoying but almost never serious: it is a missing-file problem, not a broken-Windows problem. Clear the update cache, repair the component store, and retry, and the update usually sails through. If it keeps coming back, look at disk health and antivirus interference before assuming the worst. And once updates are flowing again, leave the SoftwareDistribution folder alone; the urge to clean it is understandable, but Windows manages it fine on its own, and manual deletions between updates are how these corruptions start in the first place.
