Windows Update Error 0x80070002: Complete Solution

What Does Error 0x80070002 Mean

Error 0x80070002 (readable as: ERROR_FILE_NOT_FOUND) is a Windows system code that literally translates to "File Not Found." In the context of an update process (Windows Update or Microsoft Store), this error means the installer cannot find a critical system file, component, or metadata required to complete the operation.

You may see it in:

• Windows Update when attempting to install cumulative updates, feature updates, or security updates.
• Microsoft Store when downloading or installing apps (especially Centennial apps, i.e., Win32 apps distributed through the Store).
• Windows Installer logs (C:\Windows\Logs\CBS\CBS.log or C:\Windows\Logs\WindowsUpdate\).

Symptoms: the update process hangs, fails with an error code, or the system reports that the update failed without specifying a concrete cause.

Causes

Error 0x80070002 is almost always related to corrupted or lost system data. Specific causes:

1. Corrupted update cache. Files temporarily saved in the C:\Windows\SoftwareDistribution\Download folder may be incomplete or damaged due to an interrupted download.
2. Conflicting or corrupted services. Services like Windows Update (wuauserv), Background Intelligent Transfer Service (BITS), or Delivery Optimization are not functioning correctly.
3. Corrupted system files. Key Windows files required for update deployment (e.g., files from WinSxS) are damaged or missing. This can result from a previous failed update, virus activity, or hard drive issues.
4. Insufficient access permissions. The update process (which runs under the SYSTEM account) lacks permissions to access certain files or folders. This can be caused by antivirus software or manual changes to ACLs.
5. Hard drive problems. The drive has bad sectors, or there is insufficient free space to unpack the update.
6. Software conflict. Third-party antivirus programs, system cleaners, or "tweakers" may block or modify system files required for the update.

Solutions

Troubleshoot sequentially, from simple to complex. Before starting, ensure you have sufficient free space on the system drive (at least 20 GB) and a stable internet connection.

Method 1: Restart Update Services and Clear Cache

This is the most common and effective fix for issues related to cache corruption or "stuck" services.

1. Open Command Prompt (cmd) or PowerShell as an administrator.
2. Stop the services by running:

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

3. Rename the cache and update data folders (this forces Windows to recreate them):

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

   If the folders are not located in C:\Windows, specify the correct path to the system partition.
4. Restart the services:

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

5. Close the console and restart your computer.
6. Try checking for updates again.

Method 2: Check System File Integrity (SFC)

If clearing the cache didn't help, the system files themselves may be corrupted.

1. Launch Command Prompt (cmd) as an administrator.
2. Run the command:

   sfc /scannow
   

   The process may take 10–30 minutes. The tool will scan all protected system files and replace corrupted versions with correct ones from the WinSxS store.
3. After completion (successful or not), restart your computer.
4. If SFC reports that it found corruptions but couldn't fix some (Windows Resource Protection found corrupt files but was unable to fix some of them), proceed to the next method.

Method 3: Repair System Image (DISM)

DISM (Deployment Image Servicing and Management) operates at a deeper level than SFC and can restore the "base" system image if the WinSxS store is damaged.

1. In Command Prompt (administrator), run the command to check image health:

   DISM /Online /Cleanup-Image /CheckHealth
   

2. For a more detailed scan (takes longer):

   DISM /Online /Cleanup-Image /ScanHealth
   

3. If DISM detects issues, initiate repair by downloading necessary files from Microsoft servers:

   DISM /Online /Cleanup-Image /RestoreHealth
   

   This process requires a stable internet connection and may take 15–40 minutes.
4. After successful completion, restart your computer, then run sfc /scannow again for a final check and to fix any remaining file system issues.

Method 4: Manually Reset Update Components (PowerShell)

This method re-registers all update-related DLLs. It's effective if previous steps failed.

1. Open PowerShell as an administrator.
2. Copy and paste the following command block in full. It stops services, re-registers components, and restarts services:

   Stop-Service -Name BITS, wuauserv, cryptSvc, bits -Force
   $Tools = (Get-ChildItem -Path "$env:windir\System32" -Filter "*.dll" | Where-Object { $_.Name -match "atl|dism|wuapi|wuaueng|wucltux|wudf|wups|wups2|wuwebv" }).FullName
   foreach ($Tool in $Tools) {
       Write-Host "Registering: $Tool"
       & regsvr32.exe /s $Tool
   }
   Start-Service -Name BITS, wuauserv, cryptSvc, bits
   

3. Restart your computer and try updating again.

Method 5: Clear Microsoft Store Cache (For Store Errors)

If the error occurs when updating apps from Microsoft Store:

1. Press Win + R, type wsreset.exe, and press Enter.
2. An empty command window will appear, close after 10–15 seconds, and Microsoft Store will launch with a cleared cache.
3. Try updating or installing the app again.

Prevention

To minimize the risk of error 0x80070002 in the future:

• Do not interrupt the update process. Do not shut down your computer or disconnect the internet during update installation.
• Regularly check disk integrity. Run chkdsk C: /f (with reboot) every few months.
• Maintain sufficient free space. Ensure your system drive always has at least 15–20 GB of free space.
• Update drivers and BIOS/UEFI. Outdated hardware or drivers can cause conflicts during system kernel updates.
• Be cautious with "tweakers". Avoid programs that mass-modify Windows system files or services without full understanding of the consequences.
• Create system restore points regularly. Before major updates, create a restore point. This allows quick rollback in case of failure.