FixHub
Windows

Windows Update Error 0x80070002 (ERROR_FILE_NOT_FOUND)? Pin the Real Cause from CBS.log

Published June 10, 2026 · by The FixHub Team

A Windows update or monthly rollup fails with 0x80070002 (“some files needed… are missing” / ERROR_FILE_NOT_FOUND) — during install, as a post-reboot rollback, or mid in-place upgrade.

Why “reset the cache” is a coin flip: nearly every page reduces 0x80070002 to “reset SoftwareDistribution and run the troubleshooter.” Sometimes that works — but Microsoft documents several distinct root causes you can only distinguish from CBS.log, each with its own fix. Read the log first.

Fix 1: Reset Windows Update components (try first; it’s quick)

Admin Command Prompt:

net stop wuauserv & net stop bits & net stop cryptsvc
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old
net start wuauserv & net start bits & net start cryptsvc

Reboot, retry. Still 0x80070002? Read the log.

Fix 2: Read CBS.log to identify the specific cause

Open C:\Windows\Logs\CBS\CBS.log and search near the failure. Documented 0x80070002 causes include:

  • A stale clr_optimization scheduled-task key
  • A missing Start Menu → System Tools folder
  • Missing WinSxS DLLs (component store gap)
  • A failed driver-update registry key
  • A missing WIMMOUNT.sys entry during an in-place upgrade

The log line near the error tells you which — then apply that targeted fix.

Fix 3: Run SFC + DISM if the store is implicated

If CBS.log shows missing WinSxS components:

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

(Use /Source against a matching ISO if the PC can’t reach Windows Update — see 0x80073712 component store fix.)

Fix 4: In-place upgrade for upgrade-time 0x80070002

If it fails during a feature update (e.g. missing WIMMOUNT.sys), run setup.exe from the matching ISO with Keep apps and files to repair servicing.

FAQ

Why do generic fixes sometimes work? Because one of the causes (a stale download) is cache-related — the others aren’t. Reading CBS.log (Fix 2) tells you which you have so you don’t guess.

0x80070002 vs 0x80070003? File-not-found vs path-not-found — related; the latter is usually a missing driver path, see 0x80070003 fix.

Sources: Microsoft Learn — Troubleshoot Windows Update error 0x80070002