Error 0x80070003 is Windows Update reporting that a path it expected to exist simply was not there. It is the close sibling of the better-known 0x80070002, and like its sibling, it almost always means the update cache or data store has become corrupted. The update engine keeps a careful map of where everything lives; when that map no longer matches reality, you get this error.

The repair strategy is straightforward: rebuild the paths the engine depends on, verify the services that maintain them, and repair any underlying file system damage. The steps escalate gently, and most machines are fixed well before the end of the list.

Where 0x80070002 complains about a missing file, 0x80070003 complains about a missing path — the folder the file should live in is not where the update engine expects it. In practice the distinction barely matters, because both errors grow from the same soil: a corrupted SoftwareDistribution structure, usually after an interrupted download or an overzealous cleaner. The engine keeps an internal map of its folders, and when the map and the disk disagree, you get this code. The repair rebuilds both the folders and the map, bringing them back into agreement.

Why this happens

  • Corrupt SoftwareDistribution structure: Folders inside the update cache go missing or become unreadable after interrupted operations.
  • Damaged update database: The data store that maps updates to their file locations corrupts, pointing the engine at phantom paths.
  • Aggressive cleaner software: Third-party cleaners delete cache folders the update engine still references.
  • Interrupted downloads: Power or network failures mid-download leave half-written directory structures.
  • Disk errors: File system corruption removes or damages the folders Windows Update expects.
  • Broken BITS queue: The Background Intelligent Transfer Service can hold job references to paths that no longer exist.
  • Antivirus quarantine: Overzealous scanners sometimes quarantine update components, removing files from their expected paths.
  • Failed previous update: A half-applied earlier update leaves the servicing state referencing paths from an incomplete operation.

How to fix it

Work through these in order — diagnose first, then act.

Notice that several fixes below rename folders with a .old suffix instead of deleting them. That is deliberate: renaming forces Windows to rebuild the structure from scratch while preserving a fallback copy. If anything unexpected happens, the originals are still there. It costs a little disk space temporarily and buys real safety.

Fix 1: Run the Windows Update troubleshooter

Let the automated tool take the first pass at the corrupted paths.

  1. Open Settings, System, Troubleshoot, Other troubleshooters.
  2. Run the Windows Update troubleshooter and apply its recommended fixes.
  3. Restart the laptop when it finishes.
  4. Check for updates to see if the error is resolved.

Fix 2: Clear the download cache

Removing the damaged cache contents is the direct fix for missing-path errors.

  1. Open Command Prompt as administrator.
  2. Run net stop wuauserv and net stop bits.
  3. Delete everything inside C:\Windows\SoftwareDistribution\Download.
  4. Run net start wuauserv and net start bits, then restart and retry.

Fix 3: Reset the Windows Update components

Rebuild the full folder structure the update engine depends on.

  1. In an admin Command Prompt, stop all four services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  2. Rename the data folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  3. Restart the services: net start wuauserv, net start cryptSvc, net start bits, net start msiserver.
  4. Reboot and check for updates — the folders rebuild automatically.

Fix 4: Reset the BITS queue

A wedged transfer queue can keep referencing paths that no longer exist.

  1. Open an admin Command Prompt.
  2. Run bitsadmin /reset /allusers to clear all transfer jobs.
  3. Restart the Background Intelligent Transfer Service from services.msc.
  4. Retry Windows Update and observe whether downloads now proceed.

Fix 5: Repair system files

Deeper corruption in Windows can break the paths the update engine needs.

  1. In an admin Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth.
  2. Follow with sfc /scannow once DISM completes.
  3. Restart the laptop after both finish.
  4. Test Windows Update again.
  5. The closely related 0x80070002 error guide covers the file-not-found sibling with additional angles.

Fix 6: Check the disk for file system errors

If the folders are missing because the file system is damaged, repair the disk.

  1. Run chkdsk C: /f in an admin Command Prompt.
  2. Schedule the scan for the next restart and reboot.
  3. Allow the check to complete fully.
  4. After booting, reset the update components once more and retry.

Fix 7: Stop cleaner apps from deleting update files

Recurring 0x80070003 errors often have a repeat offender.

  1. Open any third-party cleaner or optimizer apps and review their cleaning rules.
  2. Disable any option that targets Windows Update cache, temporary update files, or the SoftwareDistribution folder.
  3. Pause real-time antivirus protection temporarily and retry the update.
  4. Re-enable protection afterward and keep the cleaner rules adjusted.

Fix 8: Install the failing update manually

Bypass the broken path lookups by delivering the package directly.

  1. Find the KB number of the failing update in your update history.
  2. Download the .msu from the Microsoft Update Catalog.
  3. Run the standalone installer and restart when prompted.
  4. Confirm the KB shows as installed in update history.
  5. See our detailed walkthrough on manually installing Windows updates on Windows 11 for the full Catalog process.

Recurrence is the signal to look beyond the update engine. If 0x80070003 returns weeks after a successful repair, something is damaging the cache structure on a schedule — almost always a cleaner app, occasionally a failing drive. Audit your installed utilities for anything that ‘cleans’ Windows Update files, run a disk check to rule out file system damage, and the error should stay fixed. A healthy update cache is boring and invisible, which is exactly what you want. For the file-not-found sibling with the same repair DNA, see our 0x80070002 walkthrough .

Closing

Error 0x80070003 is the update engine complaining about a map that no longer matches the territory. Rebuild the territory — clear the cache, reset the components, fix the disk — and the engine finds its paths again. If the error keeps returning, look for the cleaner app or failing drive that keeps redrawing the map wrong.

Frequently asked questions

What is the difference between 0x80070002 and 0x80070003?
They are close cousins. Error 0x80070002 means a specific file could not be found, while 0x80070003 means a path or directory could not be found. In practice, both point to corruption in the Windows Update cache or data store, and the repair steps are nearly identical. If you have seen fixes for one, they apply to the other with only minor differences.
Can 0x80070003 be caused by a missing user profile folder?
Occasionally. Some update operations reference profile paths, and a damaged or renamed user profile can trigger path-not-found errors. More commonly, though, the missing path is inside the Windows Update infrastructure itself — the SoftwareDistribution folders. The cache reset steps in this guide rebuild those paths from scratch, which resolves the majority of cases.
Should I delete the entire SoftwareDistribution folder?
The safer approach is to rename it rather than delete it, using the .old suffix as shown in the steps below. Renaming achieves the same rebuild while leaving you a fallback if something unexpected happens. Windows recreates the folder automatically on the next update check. Never delete the Windows folder itself or anything outside SoftwareDistribution and catroot2.
Why does this error keep coming back after I fix it?
Recurrence usually means something is re-corrupting the cache: an aggressive cleaner app deleting update files, a failing drive producing file system errors, or an antivirus quarantining update components. Identify the repeat offender with the steps below — particularly the disk check and the review of cleaner software — or the error will keep returning after every repair.