Windows

Windows Update Rolls Back with 0x80070003? It's a Missing Driver Path, Not Just the Cache

Published June 10, 2026 · by The FixHub Team

You install an update, restart, and Windows shows “Some update files are missing or have problems… Error code: (0x80070003)” and rolls the update back on reboot.

Why the cache reset usually doesn’t fix this one: almost every guide treats 0x80070003 as a generic “corrupt update cache” and pushes the SoftwareDistribution reset. But at startup this code is ERROR_PATH_NOT_FOUND — Microsoft documents it as a driver file that’s missing or inaccessible, so the update can’t complete and reverts. Clearing the cache doesn’t restore the missing driver path.

Fix 1: Find the failing driver in CBS.log

  1. Open C:\Windows\Logs\CBS\CBS.log (copy it out if locked).
  2. Search for , error and look for a .inf / driver path that failed.
  3. That path points at the driver the update couldn’t apply — note it.

Fix 2: Repair / reinstall that driver, then retry

  • Update or reinstall the named driver from the hardware vendor (or remove a broken one in Device Manager), then re-run Windows Update.

Fix 3: The most reliable fix — in-place repair (upgrade install)

For a stubborn 0x80070003 rollback, an in-place upgrade repairs the OS while keeping apps and files:

  1. Download the Windows ISO matching your version, mount it.
  2. Run setup.exeKeep personal files and apps.
  3. This rebuilds the servicing stack/driver store, so the update then installs.

Fix 4: Then (and only then) reset Windows Update components

If the above is done and downloads are still flaky, clear the cache as a finishing step:

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

FAQ

Why does it work on the first reboot then roll back? The install stages, but at the apply-on-restart phase a required driver path is missing (ERROR_PATH_NOT_FOUND), so it reverts. Fix the driver (Fix 1–2) or repair-install (Fix 3).

Different code (0x80070002)? That’s ERROR_FILE_NOT_FOUND — related but with its own causes; see 0x80070002 fix.

Sources: Microsoft Learn — Error 0x80070003 when Windows Update fails