How to Fix Windows Update Error 0x80070003
Error 0x80070003 means Windows Update could not find a file or folder it expected (Microsoft lists it as ERROR_PATH_NOT_FOUND). It usually points to a damaged update cache in the SoftwareDistribution folder, a stopped update service or corrupted system files. Resetting the update components and running DISM and SFC fixes most cases.
Key takeaways
- 0x80070003 is a “path not found” error: the servicing stack tried to reach a file or folder that is missing or unreadable.
- Start simple: restart, free up disk space, run the Windows Update troubleshooter.
- Clearing the SoftwareDistribution cache and resetting the update services resolves most stubborn cases.
- If system files are damaged, run
DISM /RestoreHealththensfc /scannow; as a last resort, “Fix problems using Windows Update” reinstalls Windows while keeping apps and files.
In this guide
- What is error 0x80070003?
- Quick checks to try first
- How to clear the SoftwareDistribution folder
- How to reset Windows Update components fully
- Repair system files with DISM and SFC
- Read the CBS log to find the missing path
- Reinstall Windows without losing files
- Frequently asked questions
- The bottom line
- Useful links
What is error 0x80070003?
Error 0x80070003 is the Windows code for ERROR_PATH_NOT_FOUND: “The system can’t find the path specified.” In Windows Update it means the servicing stack could not reach a file or folder it needed while downloading or installing an update. The update fails and Windows usually retries later, often with the same result.
Microsoft’s list of common Windows Update errors describes it as the servicing stack being unable to access a specific path. In practice, the missing path is usually one of these:
- A damaged update cache. Partly downloaded files in
C:\Windows\SoftwareDistributionreference folders that no longer exist. - Corrupted system files or component store. Files that an update needs to replace are missing or broken.
- Stopped or misconfigured services. Windows Update, BITS or Cryptographic Services is disabled.
- Interference from third-party software. Some security tools or “cleaner” utilities delete or lock folders that Windows Update uses.
- Low disk space. Extraction fails partway, leaving incomplete folder structures.
The fixes below are in order, from least to most disruptive. Test Windows Update after each one.
Quick checks to try first
Before changing anything, restart the PC, make sure the system drive has at least 20 GB free, and run the Windows Update troubleshooter. These three steps clear a surprising number of 0x80070003 failures, because a pending restart or a full drive can leave the update cache half-written.
- Restart (a full restart, not shut down and power on, if Fast Startup is enabled), then go to Settings > Windows Update > Check for updates.
- Free disk space in Settings > System > Storage. Use Cleanup recommendations or Temporary files.
- Run the troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters and select Run next to Windows Update. On current builds this opens the Get Help app, which runs the same checks.
- Temporarily disable third-party antivirus, retry the update, then turn protection back on. Microsoft Defender can stay on.
- Check the date, time and time zone in Settings > Time & language; an incorrect clock can break secure connections to the update servers.

How to clear the SoftwareDistribution folder
Clearing the SoftwareDistribution folder forces Windows Update to download fresh copies of pending updates. Stop the Windows Update service, delete the folder’s contents, then start the service again. It is safe: Windows rebuilds the cache automatically, although your update history list in Settings may appear empty afterwards.
Open Terminal (Admin) or Command Prompt as administrator and run these commands one at a time:
net stop wuauservnet stop bitsrd /s /q %systemroot%\SoftwareDistributionnet start bitsnet start wuauserv
If the rd command says a file is in use, a service has restarted itself. Run the stop commands again and retry, or restart in Safe Mode and repeat. Then return to Settings > Windows Update and check for updates; the first scan may take longer than usual.
How to reset Windows Update components fully
A full reset stops the three services Windows Update depends on, deletes the BITS download queue and renames both the SoftwareDistribution and catroot2 folders so Windows creates clean ones. Use it when clearing SoftwareDistribution alone did not stop error 0x80070003.
These steps follow Microsoft’s documented process to reset Windows Update components manually. Run each command in an elevated Command Prompt:
| Step | Command | What it does |
|---|---|---|
| 1 | net stop bits |
Stops Background Intelligent Transfer Service |
| 2 | net stop wuauserv |
Stops the Windows Update service |
| 3 | net stop cryptsvc |
Stops Cryptographic Services (uses catroot2) |
| 4 | Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" |
Clears the BITS download queue |
| 5 | Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak |
Sets aside the update cache |
| 6 | Ren %systemroot%\System32\catroot2 catroot2.bak |
Sets aside the signature catalogue cache |
| 7 | netsh winsock reset |
Resets the network stack (needs a restart) |
| 8 | net start bits, net start wuauserv, net start cryptsvc |
Restarts the services |
Restart the PC and check for updates. Once updates install successfully, you can delete the .bak folders to recover space.
Microsoft’s article also includes steps that re-register DLLs and reset service security descriptors. Those are rarely needed for this error, and the security-descriptor step overwrites custom permissions, so skip them unless everything else fails.
Repair system files with DISM and SFC
If the update cache was not the problem, corrupted system files or a damaged component store probably are. Run DISM.exe /Online /Cleanup-image /Restorehealth first, then sfc /scannow, from an elevated Command Prompt. DISM repairs the store that SFC uses as its source, so the order matters.
- Open Command Prompt or Terminal as administrator.
- Run
DISM.exe /Online /Cleanup-image /Restorehealth. Stay connected to the internet; it can sit at 20% or 62% for several minutes. - When DISM reports success, run
sfc /scannowand wait for verification to reach 100%. - Restart and try Windows Update again.
Microsoft sets out the same sequence in its guide to using System File Checker in Windows. For a deeper walkthrough of each switch, see our guide to repairing Windows 11 with DISM RestoreHealth, and if you are unsure which tool to reach for, our comparison of SFC vs DISM vs CHKDSK explains what each one repairs.
Rebuilding a PC that keeps failing updates?
If repairs reveal that Windows on this machine was never properly activated, or you are doing a clean install on new hardware, a Windows 11 Pro retail key gives you a licence you can move to a future PC. Our Windows 11 Pro download and installation guide covers the install itself.
Read the CBS log to find the missing path
If the error keeps returning, the CBS log usually names the exact path Windows could not find. Microsoft’s own mitigation for 0x80070003 is to open the latest CBS.log in %Windir%\Logs\CBS, search for “, error” and match the entries to the time the update failed.
- Note the time the update failed in Settings > Windows Update > Update history.
- Open
C:\Windows\Logs\CBSin File Explorer and copyCBS.logto your desktop (the original is locked while Windows is running). - Open the copy in Notepad and search for
, erroror0x80070003. - Look at lines close to the failure time for a folder or file path.
A missing path inside a third-party program folder suggests uninstalling or repairing that program. A missing path under C:\Windows\WinSxS points back to DISM, or to the in-place reinstall below.
Reinstall Windows without losing files
When nothing else works, use Settings > System > Recovery > Fix problems using Windows Update > Reinstall now. It downloads and reinstalls your current version of Windows 11 while keeping your apps, files and settings, which replaces any damaged update components in one pass.
Microsoft explains the requirements in fix issues by reinstalling the current version of Windows. The option may not appear on older builds or on work-managed PCs; in that case, an in-place upgrade from Windows 11 installation media that keeps files and apps achieves the same result.
Back up important files first, even though this process is designed to keep them. If a specific update caused the trouble, you can also uninstall that update from Settings > Windows Update > Update history > Uninstall updates and wait for a corrected release. Your Windows activation is normally kept through a repair install; if it is not, our guide to checking whether Windows 11 is activated shows you how to confirm it.
Frequently asked questions
What causes error 0x80070003 in Windows Update?
It is caused by Windows being unable to find a file or folder it needs during an update. The usual culprits are a corrupted SoftwareDistribution cache, damaged system files, stopped update services, very low disk space, or third-party security and cleaning tools that removed or locked update folders. Resetting the update components fixes most cases.
Is it safe to delete the SoftwareDistribution folder?
Yes, provided you stop the Windows Update and BITS services first. Windows recreates the folder and re-downloads any pending updates. You lose only the cached downloads and the local update history list shown in Settings; installed updates stay installed and nothing in your personal files is touched.
Does error 0x80070003 mean my hard drive is failing?
Not usually. The error means a path was missing, which is more often a software problem than a hardware one. If you also see slow file access, clicking noises or disk errors in Event Viewer, check the drive’s health with the manufacturer’s tool or chkdsk and back up your data promptly.
How long does DISM RestoreHealth take?
DISM RestoreHealth typically takes 10 to 30 minutes, but it can take longer on slow drives or connections. It often appears stuck at 20% or 62%; that is normal, so leave it running. Run sfc /scannow once DISM finishes and reports that the restore operation completed successfully.
Can I fix 0x80070003 without losing my files?
Yes. Every fix in this guide keeps your files, including the “Fix problems using Windows Update” reinstall option, which Microsoft designs to keep apps, files and settings. Only “Reset this PC” with the Remove everything option deletes personal data. Back up first regardless, as a sensible precaution before any repair.
Does error 0x80070003 affect Windows activation?
No. 0x80070003 is an update error, not an activation error, and resetting update components does not touch your licence. A repair reinstall normally keeps activation too. If Settings > System > Activation shows a problem afterwards, it is a separate issue with its own error code.
The bottom line
Error 0x80070003 is a missing-path problem, and the fix is usually to give Windows Update a clean cache and healthy system files. Work through the steps in order and most PCs are updating again well before the reinstall stage. For other Windows 11 problems, browse our guides on the WinCDKey blog.
Useful links
| Resource | Why it helps |
|---|---|
| DISM RestoreHealth guide | Detailed walkthrough of DISM repair options |
| SFC vs DISM vs CHKDSK | Which repair tool to use and when |
| Windows 11 Pro retail key | Transferable licence for a clean install |
| Windows 11 Pro install guide | Download, install and activate Windows 11 Pro |
| Check Windows 11 activation | Confirm your licence after repairs |
| Microsoft: common Windows Update errors | Official definition and mitigation for 0x80070003 |
| Microsoft: reset Windows Update components | Full documented reset procedure |
| Microsoft: System File Checker | Official DISM and SFC steps |
| Microsoft: reinstall current version of Windows | Repair install that keeps apps and files |