How to Fix Windows Update Error 0x80070002 on Windows 11

Windows Update error 0x80070002 has a wonderfully vague message: the update failed, and Windows will try again later. Trying again sometimes works, but if the same update keeps failing, the useful clue is the code itself.

At the system level, Microsoft maps 0x80070002 to ERROR_FILE_NOT_FOUND—Windows cannot find a file it expected to use. During an update, that can point to an incomplete download, a stale update cache, or a missing or damaged Windows component. It does not automatically mean your SSD is failing, and it is not proof of malware.

This guide is for the code shown in Settings > Windows Update. If it appears while opening an app, restoring a backup, or installing Windows from USB, the cause may be different.

Do these quick checks first

Open Settings > Windows Update > Update history and note the name and KB number of the failed update. That detail is useful if you eventually need support.

Before changing update components, save your work and back up important personal files. Keep a laptop connected to power, use a stable internet connection, and make sure the system drive is not almost full. It is also worth opening Settings > Time & language > Date & time, enabling automatic time and time-zone settings, and selecting Sync now. Microsoft notes that incorrect time settings can interfere with Windows Update.

Disconnect external drives, docks, and other accessories that Windows does not need to run. Then work through the fixes below in order, testing Windows Update after each one.

Windows 11 desktop prepared for update troubleshooting

1. Restart Windows and try the update again

A normal restart clears pending processes and can finish an update stage that did not close cleanly.

  1. Close your apps and select Start > Power > Restart.
  2. After signing in, open Settings > Windows Update.
  3. Select Check for updates.

2. Run the Windows Update troubleshooter

Windows 11 includes an automated troubleshooter that checks common update settings and services.

  1. Open Settings > System > Troubleshoot.
  2. Select Other troubleshooters.
  3. Find Windows Update and select Run.
  4. Follow the prompts in Settings or the Get Help app, apply any recommended fix, and restart the PC.

Return to Windows Update and retry the failed update. This is the least invasive repair, so it belongs near the top of the list.

3. Clear the Windows Update download cache

If a downloaded package is incomplete, Windows may keep retrying the same bad copy. Clearing the cache makes it download fresh update files.

  1. Press Windows key + R, enter services.msc, and press Enter.
  2. Right-click Windows Update and select Stop.
  3. Open File Explorer and go to C:\Windows\SoftwareDistribution.
  4. Delete the files and folders inside SoftwareDistribution.
  5. Return to Services, right-click Windows Update, and select Start.
  6. Restart the PC and check for updates again.

4. Repair Windows components with DISM and SFC

If the cache is not the problem, repair the Windows component store and protected system files. Microsoft says to run DISM before System File Checker.

  1. Search for Command Prompt, right-click it, and select Run as administrator.
  2. Enter this command and wait for it to finish:

    DISM.exe /Online /Cleanup-image /Restorehealth
  3. After DISM reports that the operation completed successfully, enter:

    sfc /scannow
  4. Leave the window open until verification reaches 100 percent.
  5. Restart Windows and try the update again.

If either tool reports that it could not complete the repair, note the exact message rather than running random file-replacement commands from the web.

5. Reset the update working folders

This is the advanced version of refreshing the update cache. Microsoft recommends command-line procedures only if you are comfortable using an administrator Command Prompt.

Run these commands one at a time, waiting for each to complete:

net stop bits
net stop wuauserv
ren %systemroot%\softwaredistribution softwaredistribution.bak
ren %systemroot%\system32\catroot2 catroot2.bak
net start bits
net start wuauserv

6. Use Windows 11’s repair reinstall

If 0x80070002 survives the troubleshooter, fresh caches, and system-file repairs, Windows 11 has a recovery option designed for update-related component problems.

Go to Settings > System > Recovery. Under Fix problems using Windows Update, select Reinstall now and follow the prompts. Microsoft says this reinstalls the same Windows version, repairs system files and components, and preserves apps, files, and settings. Keep the PC connected to power and the internet throughout the process, and back up important files first anyway.

The option may be absent on a work- or school-managed PC, or on a device missing the Windows updates required to provide it. In that case, contact the organization’s administrator or Microsoft Support instead of changing update policies yourself.

Laptop running Windows Update diagnostics

Frequently asked questions

Is it safe to delete SoftwareDistribution?

Microsoft’s troubleshooting instructions say to stop the Windows Update service and delete the contents of C:\Windows\SoftwareDistribution. Stay inside that folder and start the service again afterward. Windows will download needed update files again.

Will DISM or SFC erase my personal files?

They are Windows repair tools for components and protected system files, not personal-file cleanup tools. A current backup is still sensible before any system repair.

Is 0x80070002 the same as 0x80070002-0x20009?

No. The longer code is associated with a Windows installation or upgrade phase. Microsoft says 0x80070002-0x20009 can occur when another connected disk creates a system-partition conflict; its guidance is to remove disks on which Windows 11 is not being installed. Do not disconnect your Windows system drive.

When should I stop troubleshooting?

Stop if Windows no longer starts normally, DISM cannot repair the image, or the same update fails after the repair reinstall. Record the KB number, your Windows version from winver, and the exact error, then contact Microsoft Support. Manual registry deletions and copied DLL files are case-specific repairs, not sensible generic fixes for a home PC.

Official Microsoft sources

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top