Windows Update Error 0x80070002: What It Means and How to Fix It (2026 Updated Guide)

Quick answer

0x80070002 is the Windows error code for ERROR_FILE_NOT_FOUND. When Windows Update throws it, the cause is almost always missing or corrupted update files in the local staging folders, or a half-finished previous update that left the system in an inconsistent state. The fastest fix is to clear the SoftwareDistribution folder and let Windows redownload. If that doesn’t work, run DISM and SFC. Hardware-level fixes are rarely needed.

Before you start

You will need administrator rights for almost every step.
This procedure requires a working internet connection. The fix involves Windows redownloading update files, which can be several gigabytes.
Don’t run a third-party “update repair tool” first. The official Windows Update troubleshooter does the same job and won’t break anything in the process.
If the affected device is managed by your employer, see If you are on a work or school device before you change anything.

What this error means

0x80070002 is one of the most precise error codes Windows actually returns. It maps to the Win32 system error ERROR_FILE_NOT_FOUND — and that’s exactly what’s happening. Windows Update has tried to access a file it expects to be there, and the file isn’t.

There are three ways that situation arises in practice:

The download was interrupted. A Windows Update is delivered as a collection of files staged in C:\Windows\SoftwareDistribution. If the download is interrupted — by sleep, by a bad network, by an antivirus tool that quarantines a file mid-write — the file index is correct but the file itself is missing or zero bytes.
A previous update is half-installed. Windows Update is transactional in design but not always in practice. An update that wrote some registry entries before failing leaves Windows in a state where it expects DLLs and resource files that aren’t on disk yet.
The system date and time are wrong. Windows Update uses signed payloads and time-bound certificates. If the system clock is significantly off — most often because a CMOS battery is dying or because a manually-set timezone is pointing somewhere obviously wrong — file lookups can fail signature validation in ways that surface as “file not found.”

In 2026, the largest single source of this error is the first cause. Antivirus software interacting badly with the SoftwareDistribution folder is the second most common. The third is rare but easy to rule out.

Where this error appears

You will see 0x80070002 in:

Settings → Windows Update, with messages like “There were some problems installing updates, but we’ll try again later” or “Windows could not search for new updates”.
Update History, with the failure logged against a specific KB number.
The standalone Windows Update Standalone Installer (.msu files) when manually installing.
Windows Server environments, where it surfaces on rollup updates and frequently traces back to corrupted entries in the WinSxS folder.

The error sometimes also appears as 80070002 (no 0x) in older logs and in legacy parts of the Windows Update interface. They mean the same thing.

Common causes

Symptom	Most likely cause
Error appears immediately on “Check for updates”	SoftwareDistribution corrupted, or system time wrong
Update downloads but fails at install with this code	Half-installed previous update, missing servicing-stack files
Error appears after a recent crash, power cut or forced shutdown	Interrupted download — common, easy to fix
Error on Windows Server during rollup install	Missing files in WinSxS, often resolvable with DISM /RestoreHealth
Error appears alongside other strange behaviour (apps crashing, files missing)	Storage hardware problem — diagnose hardware first

Fixes to try first

These are low-risk and resolve the majority of cases. Work through them in order.

1. Check the system date and time

This sounds trivial, but it’s caught a non-trivial number of 0x80070002 failures over the years. Open Settings → Time & language → Date & time. Confirm:

Set time automatically is on.
The time zone matches your location.
The clock is showing within a minute or two of the correct local time.

If the clock is significantly wrong, click Sync now, restart, and retry the update.

2. Run the Windows Update troubleshooter

Go to Settings → System → Troubleshoot → Other troubleshooters, then click Run next to Windows Update. The troubleshooter checks for the most common Update problems, applies fixes, and reports what it found. Allow it to run all the way through, then retry the update.

3. Restart the PC

A clean restart resolves more 0x80070002 failures than the public guidance suggests, because it forces all locked files to release and lets Windows complete pending file rename operations. Don’t skip this.

4. Clear the SoftwareDistribution folder

This is the canonical fix for 0x80070002. The full reset procedure is documented separately in How to reset Windows Update components. For this error specifically, you can use a shorter version:

Open Command Prompt as administrator and run:

net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

Then go to Settings → Windows Update and click Check for updates. Windows will rebuild the SoftwareDistribution folder and redownload anything that was pending. Allow 5–15 minutes for the first check.

5. Manually install the failed update

If you know the specific KB number that failed:

Note the KB number from Settings → Windows Update → Update history.
Search for it in the Microsoft Update Catalog.
Download the version matching your Windows architecture (x64 in almost all cases).
Run the downloaded .msu file.

A manual install bypasses the Windows Update orchestrator entirely and frequently succeeds when the orchestrator failed.

If the basic fixes haven’t moved it, the next step is checking the underlying system files.

Advanced fixes

These are still reversible — but understand each before running it.

Run DISM and SFC

0x80070002 from corrupted system files is a real phenomenon, particularly on machines that have been through power-loss events. Run, in order, from an elevated Command Prompt:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

RestoreHealth will take 15–45 minutes. Don’t cancel it. For a deeper walkthrough including how to fix DISM itself when it errors out, see How to run DISM and SFC safely.

Reset the entire Windows Update component stack

If clearing SoftwareDistribution alone wasn’t enough, the full reset procedure (which also clears catroot2 and re-registers update DLLs) often is. Walk through How to reset Windows Update components carefully — it’s a longer procedure, but it’s the version that actually fixes the hard cases.

Check for storage problems

If 0x80070002 keeps coming back even after a successful reset, the underlying storage may be failing. Open Command Prompt as administrator and run:

chkdsk C: /scan

This is a read-only scan that won’t change anything. Review the output for filesystem errors. If the scan reports significant corruption, back up your data immediately before doing anything else.

Repair install (in-place upgrade)

The deepest reasonable fix for stubborn 0x80070002 is an in-place repair install. Download the Windows 11 ISO (or Windows 10 ISO if applicable), mount it, and run setup.exe from inside Windows. Choose Keep personal files and apps. The installer reinstalls the Windows component store while preserving your data and applications. Block out 60–90 minutes; ensure you have a recent backup; do this when you don’t need the PC for the rest of the afternoon.

If you are on a work or school device

The standing rules apply. Don’t run DISM, don’t reset components, and don’t clear SoftwareDistribution on a managed device without your administrator’s involvement. The right action is to:

Note the exact failed KB number and the error code.
Send those details to your IT administrator.
Wait. The update may be deliberately deferred, or there may already be a known issue your admin team is tracking.

If you’re the admin for a small business and there’s no separate IT to escalate to, see our admin checklist for new M365 sign-in failures — the equivalent admin-side approach.

When to stop

Stop and seek a different approach when:

The error keeps returning despite multiple successful resets. The underlying state on the machine is unstable; an in-place repair install is the right next step.
DISM /RestoreHealth itself fails. That points to a deeper component-store problem and needs an in-place repair install.
chkdsk /scan reports significant filesystem errors. Hardware diagnosis comes before any further software fixes.
You’re on a work device. Stop earlier — escalate to IT.
You’ve been at this for more than four hours. The next step is an in-place repair install, which is faster than continuing to troubleshoot at this point.

Windows Update error 0x80070643 — the related “install failure” error with different root causes.
Windows Update error 0x800f081f — when source files for a specific component can’t be located.
Windows Update stuck at 0%, 33% or 100% — for the symptom-led version of “update isn’t working.”
How to reset Windows Update components — the full reset procedure referenced above.
How to run DISM and SFC safely — for the system file repair commands.

Official references

Microsoft Learn: Troubleshoot Windows Update Error 0x80070002
Microsoft Support: Fix Windows Update errors
Microsoft Update Catalog: catalog.update.microsoft.com

FAQ

Is 0x80070002 the same as 80070003? Yes. They’re variants of the same ERROR_FILE_NOT_FOUND error, surfaced through slightly different parts of the update stack. The fixes are identical.

Will I lose any installed software if I clear the SoftwareDistribution folder? No. SoftwareDistribution stores pending and downloading updates only — not installed software, settings, or files. The folder rebuilds automatically the next time you check for updates.

Why does the update redownload from scratch every time after I do this? Because the SoftwareDistribution folder is the cache. Clearing it forces Windows to rebuild from Microsoft’s servers. That’s the trade-off — a redownload in exchange for a working update.

Can a wrong system clock really cause this error? Yes — though it’s rare. Windows Update uses certificates that are valid only within specific date ranges. A clock that’s months or years off can fail certificate validation, which surfaces as a missing-file error rather than a more obvious “your clock is wrong” message. The clock check costs nothing; do it.

Should I disable my antivirus permanently? No. Disable it temporarily during a single update attempt to test whether it’s interfering. If it is, the right fix is to add an exclusion for the SoftwareDistribution folder, not to leave the antivirus disabled. Mainstream antivirus tools — Microsoft Defender, Bitdefender, ESET, Kaspersky, the major commercial brands — should not need to be uninstalled for Windows Update to work.

What does ERROR_FILE_NOT_FOUND actually look like in the logs? If you want to confirm exactly which file is missing, check the CBS log at C:\Windows\Logs\CBS\CBS.log. Search for entries containing 0x80070002; the surrounding lines will name the specific file or registry key Windows expected. This is a power-user step but it’s diagnostic gold for stubborn cases. The same approach works for the WindowsUpdate.log file, which on Windows 11 is generated on demand via Get-WindowsUpdateLog in PowerShell rather than being maintained continuously.

Does this error mean Windows is going to fail to boot soon? No. 0x80070002 is an update-time error, not a boot-time error. A machine with persistent 0x80070002 failures will continue to boot and run normally — it just won’t successfully apply Windows Updates. The risk is that you eventually fall behind on security patches, which is a problem of a different shape.

Will an in-place repair install delete my apps and files? No, not when you choose Keep personal files and apps during setup. The repair install replaces the Windows component store and system files while leaving installed applications and your personal data untouched. Settings are mostly preserved too, with the caveat that some Group Policy and registry customisations may be reset to defaults. Recent backup before doing this is the standard precaution; the procedure is not destructive when followed correctly.

↑ Back to top