Fix Windows Update Error 0x80070002 Without Losing Files

Windows Update error 0x80070002 usually means Windows is missing an update file or cannot complete its local update cache, often because a download was interrupted or a cached file is incomplete or corrupted. Start by checking the clock, free space, pending restarts, and external storage, then run the Windows Update troubleshooter and rebuild the update cache. These steps do not delete personal files; use extra caution if you also see disk errors, repeated crashes, or failures outside Windows Update.

What error 0x80070002 means and whether these fixes apply to you

Windows may show this message when an update download was interrupted, a cached file is incomplete or corrupted, or a file Windows expects is missing:

0x80070002

The code commonly appears during ordinary Windows 10 and Windows 11 updates. By itself, it does not mean that Windows is deleting your documents, photos, or other personal files. The fixes below rebuild Windows Update's temporary data and repair system components; they do not format the drive or remove personal files.

These steps apply when the error appears under Windows Update in Settings. They may not fix an update for a separate application, such as Microsoft 365, a printer utility, or another vendor's software. A managed work computer may also have update policies that only an organization's administrator can change.

You need an Administrator account for the command-line repairs later. The initial checks and the Windows Update troubleshooter can be run from Settings. Restarting is required during the cache reset, and backing up important files is sensible before broader repairs.

Be more cautious if you see disk errors, repeated file corruption, unusual drive noise, frequent crashes, or failures outside Windows Update. Those signs can point to storage or hardware trouble. Avoid resetting Windows until the cause is clearer.

Check these simple causes before resetting Windows Update

Before changing update services, complete these reversible checks. A pending restart, an incorrect clock, low free space, or removable storage can prevent an update from completing.

1. Restart the PC from Start > Power > Restart. A pending restart can prevent a new update from completing.
2. Check the date, time, and time zone. Open Settings, search for Date & time, turn on automatic time and automatic time-zone options if they are available, then select Sync now. An incorrect clock can interfere with update verification.

Settings > Time & language > Date & time

3. Check the system drive's free space in File Explorer under This PC. If it is nearly full, remove temporary files or uninstall something you no longer need. Windows needs working space for downloaded and unpacked updates; the exact amount depends on the update.
4. Disconnect unnecessary USB drives, SD cards, external disks, and other removable storage. Leave connected only devices required for the PC. An incompatible or unavailable external path can sometimes interfere with an update.
5. Record the failed update before making changes. Open Update history and write down the update name, its KB number if shown, and the date of the failure.

Windows 11: Settings > Windows Update > Update history
Windows 10: Settings > Update & Security > Windows Update > View update history

If the same KB number fails repeatedly, keep it available for the verification and log-review steps later.

Fix Windows Update in the safest order

Start with Windows' built-in repair tool. It makes targeted checks and is easier to undo than manually changing services.

1. Open the Windows Update troubleshooter.

Windows 11: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run
Windows 10: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter

Apply any recommended repair, then restart the PC if Windows requests it. Try Windows Update again. If the troubleshooter reports that it could not identify the problem, continue to the cache reset rather than repeating the troubleshooter.

2. Open Command Prompt as Administrator. Search for Command Prompt, right-click it, and choose Run as administrator. Stop the services that use the update cache.

net stop wuauserv
net stop bits
net stop cryptsvc

You should see messages that the services stopped successfully. If a service was not running, that is usually harmless. If Windows refuses access, close the window and reopen Command Prompt with Administrator privileges.

3. Rename the two cache folders. Renaming preserves the old data as a fallback; Windows creates fresh folders when the services start again.

Do not delete other folders in C:\Windows, and do not rename these folders while the related services are still running.

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

A successful command returns to the prompt without an error. If you see that a file is in use, repeat the service-stop commands and try again. If the folder name already ends in .old, choose another temporary name such as SoftwareDistribution.old2.

4. Start the services again, then restart Windows.

net start wuauserv
net start bits
net start cryptsvc
shutdown /r /t 0

After the restart, Windows rebuilds the update cache. The old folders can remain temporarily; do not remove them until the update works and you have no need to recover their contents.

5. If the error remains, repair the Windows component store with DISM. Open an Administrator Command Prompt again and run the command below. Keep the window open until it finishes; the duration varies by system.

DISM.exe /Online /Cleanup-Image /RestoreHealth

A successful run normally ends with a message that the restore operation completed successfully. If DISM reports that it cannot find source files, make sure Windows Update is available and retry after reconnecting to a reliable network. Do not interrupt the command simply because progress appears to pause.

6. Run System File Checker after DISM completes. SFC checks protected Windows files and replaces damaged copies when possible.

sfc /scannow

The useful results are a message that no integrity violations were found, or that corrupted files were found and repaired. If SFC says it could not repair some files, restart the PC, run DISM again, and then run SFC once more. If both tools repeatedly fail, the component store or the drive may need further investigation.

How to tell whether 0x80070002 is gone—and what to try next

Retry the update from Windows Update after the restart. Let the process finish before deciding it failed; downloading, installing, and restarting can appear as separate stages.

1. Open Windows Update and select Check for updates, or select Retry beside the failed update. If the update installs and Windows requests a restart, restart before checking its status.
2. Confirm the result in Update history. The specific KB entry should show Successfully installed rather than Failed. A successful installation of the same KB number is stronger evidence than the disappearance of the error banner alone.

Windows 11: Settings > Windows Update > Update history
Windows 10: Settings > Update & Security > Windows Update > View update history

3. If it fails again, record the exact KB number, the failure date, and whether the failure occurs during download, installation, or restart. A different KB number may represent a separate problem.
4. Review Windows Update logs. In PowerShell, run this as Administrator:

Get-WindowsUpdateLog

Windows creates a readable WindowsUpdate.log file on the desktop or in the current user profile, depending on the Windows version. Search it for the KB number and 0x80070002. The log can show whether Windows was missing a package, could not read a cache file, or encountered another error.

5. Check the component-repair results if DISM or SFC reported a problem. DISM writes details to C:\Windows\Logs\DISM\dism.log, while SFC records its findings in the CBS log. Avoid changing entries in those files; use them to identify a repeated error or provide details to support staff.

If the same update continues to fail after the cache reset, DISM, and SFC, check Microsoft's current documentation for that exact KB number. A repair install that keeps installed applications and personal files may be the next Windows-level option, but confirm the backup first and follow the instructions for your edition. On a work-managed device, contact the organization's administrator. If storage errors or broader system failures are present, address the drive problem before attempting another update.

Conclusion

Check the basic causes first, then run the troubleshooter and rebuild the update caches. If the same KB still fails, use DISM followed by SFC, review Update history and the relevant logs, and back up important files before considering a repair install or contacting Microsoft support.

Frequently Asked Questions

Will clearing the SoftwareDistribution folder delete my personal files?

No. Renaming `SoftwareDistribution` moves Windows Update's local download cache out of active use. It does not remove documents, photos, installed applications, or personal settings, and Windows creates a new cache after the update services restart.

Do I need to run DISM and SFC as Administrator?

Yes. Open Command Prompt as Administrator. Run DISM first, let it finish, and then run `sfc /scannow` so SFC can use any component-store repairs made by DISM.

What if 0x80070002 returns after the update installs?

Check Update history to see whether the same KB failed again or a newer update failed. Record the failure stage, review the generated Windows Update log, and check for storage errors or management policies before attempting a repair install.