Error 0x80070002 is Windows Update’s way of saying it cannot find files it needs. The update service downloaded a package, or tried to, and when the installer went looking for those files in the cache, they were corrupted, incomplete, or missing entirely. It is one of the most common update errors and, fortunately, one of the most fixable, because the root cause is almost always the download cache rather than anything deeply wrong with your system.

The signature symptom is an update that fails quickly with this code, retry after retry, with no progress. Sometimes the download itself stalls or loops. The underlying story is usually an interrupted download, a wedged Background Intelligent Transfer Service, or cache files damaged by a previous failed attempt. Occasionally a failing drive or overzealous antivirus keeps re-corrupting fresh downloads, which explains the stubborn cases.

This guide gives you seven fixes in the order that resolves 0x80070002 fastest, starting with the automated troubleshooter and the definitive cache reset, then addressing the deeper causes for repeat offenders. For the related access-denied code, see our 0x80070005 guide .

Why this happens

  • Corrupted download cache: Damaged files in SoftwareDistribution fail the installer’s file checks.
  • Interrupted downloads: Network drops leave partial packages the installer cannot use.
  • Wedged BITS service: The transfer service stalls and never completes the download properly.
  • Antivirus quarantining update files: Security software removes files the installer expects to find.
  • Failing storage: Bad sectors corrupt cached files as they are written.
  • Stale update metadata: Mismatched catalog data points the installer at wrong file versions.
  • Servicing stack damage: A broken update engine mishandles otherwise fine downloads.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Run the Windows Update troubleshooter

The automated tool resets services and cache state, which resolves this error without manual commands for many users.

  1. Open Settings, System, Troubleshoot, Other troubleshooters.
  2. Run the Windows Update troubleshooter.
  3. Apply every recommended fix it offers.
  4. Restart the laptop.
  5. Retry the update and check whether the error is gone.

Fix 2: Perform the full cache reset manually

This is the definitive fix for 0x80070002: remove the corrupted cache entirely and force a clean re-download. Stopping the services first ensures no process holds the folders open while you rename them, and the .old copies remain as a fallback you can delete later once the update succeeds.

  1. Open Command Prompt as administrator.
  2. Run net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Run ren C:\Windows\SoftwareDistribution SoftwareDistribution.old.
  4. Run ren C:\Windows\System32\catroot2 catroot2.old.
  5. Restart the services with net start for each one.
  6. Reboot and check for updates, confirming a fresh download completes.

Fix 3: Restart BITS and check the network

Ensure the transfer service is healthy and the connection is stable for the re-download.

  1. Open services.msc and restart Background Intelligent Transfer Service.
  2. Switch to a stable network, preferably wired, for the download.
  3. Disable any VPN temporarily.
  4. Retry the update and watch the download progress steadily.
  5. If it stalls again, the network path needs attention before anything else.

Fix 4: Check antivirus quarantine for update files

See whether your security software has been removing update components.

  1. Open your antivirus and review its quarantine or threat history.
  2. Look for quarantined files with paths under C:\Windows\SoftwareDistribution.
  3. Restore any legitimate Windows Update files it captured.
  4. Add the SoftwareDistribution folder to the antivirus exclusions.
  5. Re-run the cache reset from Fix 2 and retry the update.

Fix 5: Verify disk health

Rule out storage hardware as the recurring corruption source.

  1. Open Command Prompt as administrator.
  2. Run wmic diskdrive get status and confirm every drive reports OK.
  3. Run chkdsk C: /f, approve the restart scan, and reboot.
  4. Let the check complete fully before logging in.
  5. Retry the update on the verified-healthy drive.

Fix 6: Repair the servicing stack with DISM and SFC

If the error survives a clean cache, the update engine itself may be damaged.

  1. Open an elevated Command Prompt.
  2. Run DISM /Online /Cleanup-Image /RestoreHealth to 100 percent.
  3. Run sfc /scannow and wait for verification.
  4. Restart the laptop.
  5. Perform the cache reset once more, then retry the update.

Fix 7: Install the update manually from the Catalog

Bypass the download machinery entirely with the standalone package.

  1. Note the failing KB number from update history.
  2. Download the x64 .msu from https://www.catalog.update.microsoft.com .
  3. Double-click to install and restart when prompted.
  4. Verify success in Update history.

Our manual installation guide details package selection.

Fix 8: Flush DNS and reset the network stack

Corrupted DNS cache entries or a damaged network stack can make update downloads fail in ways that look exactly like missing files. If Windows cannot reliably reach Microsoft’s content servers, downloads arrive truncated or mismatched, and the installer reports 0x80070002. Resetting the network stack is quick, safe, and resolves an entire class of download corruption that cache resets alone cannot touch.

  1. Open Command Prompt as administrator.
  2. Run ipconfig /flushdns to clear the resolver cache.
  3. Run netsh winsock reset to rebuild the Windows sockets layer.
  4. Run netsh int ip reset to reset the TCP/IP stack to defaults.
  5. Restart the laptop so the resets take effect.
  6. Retry the update on the clean network stack and confirm the download completes.

Closing

Error 0x80070002 is a missing-files problem with a missing-files solution: reset the cache, stabilize the download, and the installer finds everything it expects. The troubleshooter or the manual cache reset clears it for most laptops, while the disk check and DISM repair handle the stubborn repeat cases. Keep your connection stable during downloads and this error rarely returns.

Frequently asked questions

What does Windows Update error 0x80070002 mean?
Error 0x80070002 means the system cannot find a file it expects, which in the update context almost always points to corrupted or incomplete download cache files. The installer looks for package files in the SoftwareDistribution folder, finds them damaged or missing, and aborts with this code. Clearing the cache and letting Windows re-download the files fixes it in the large majority of cases.
Why does 0x80070002 keep coming back after I fix it?
If the error returns, something is re-corrupting the downloads, most commonly an unstable network connection that keeps producing partial files, a failing storage drive writing bad data, or antivirus quarantining update files. It can also mean the servicing stack itself is damaged, in which case the DISM and SFC repairs in this guide address the deeper cause rather than just the symptoms.
Can I fix 0x80070002 without the command prompt?
Yes, running the Windows Update troubleshooter from Settings often resolves this error without any commands, since it resets the relevant services and cache automatically. The manual command-prompt cache reset in this guide is simply the more thorough version of the same repair. Try the troubleshooter first if you prefer to avoid typing commands.
Does 0x80070002 affect the Microsoft Store as well?
It can, because the Store uses similar download and servicing machinery. If both Windows Update and the Store show file-not-found errors, run the Windows Store Apps troubleshooter in addition to the update troubleshooter, and use the wsreset command to clear the Store cache. The underlying cache and servicing repairs in this guide benefit both.