windows update error 0x80070003 how to fix

TL;DR

Error 0x80070003 means Windows Update cannot find files it expects, usually because a download was interrupted or the download store was partly cleared. Stop the update services, rebuild the SoftwareDistribution download folder, restart the services, and download the update again. Check the system drive and the update service paths if the error returns on a clean download.

windows update error 0x80070003 how to fix

Use this when

• Updates fail soon after download starts or at the start of installation with 0x80070003.
• The error began after a disk cleanup, a power loss, or a manually deleted update cache.
• Windows Update history shows the same code across several different KBs.

Not for this skill when

• A single manually downloaded MSU says it is not applicable. That is a package targeting issue, not this error.
• DISM reports component store corruption with 0x800f codes. Repair the store with the store-specific skill.

Steps

1. Confirm free space on the system drive and note the failing KB and time. Open Windows Update history and the event logs for the WindowsUpdateClient source so you can compare a later attempt against this baseline instead of guessing whether anything changed. Verify: you have the KB, time, and at least several gigabytes free on the system drive, or you freed space first
2. Stop the Windows Update, Background Intelligent Transfer, and Cryptographic services from an elevated terminal. These services hold the download store open, and renaming folders while they run either fails or leaves the same damaged files in use. Verify: all three services report stopped before you touch any folder
3. Rename the SoftwareDistribution folder to a backup name such as SoftwareDistribution.old and rename the catroot2 folder in System32 the same way. Windows creates clean copies on the next scan, and keeping the old folders lets you undo the change if needed. Verify: both folders have backup names and no error says a file is still in use
4. Restart the three services, restart the machine if any service refuses to start, and run Check for updates so Windows builds a fresh download store and re-downloads the update metadata and payload from scratch. Verify: a new SoftwareDistribution folder appears and the scan completes without 0x80070003
5. Install the failing update on its own and review the result in update history. If it succeeds, delete the renamed backup folders after a few days of normal operation to reclaim space. Verify: the KB shows installed successfully and later scans do not offer it again

Why it happens

Windows Update downloads package payloads and metadata into the SoftwareDistribution store and tracks them in its internal datastore. If a download is interrupted by shutdown, disk pressure, aggressive cleanup tools, or a service crash, the datastore can point at payload files that no longer exist or are only partly written. The installer then stops with a path or file not found condition surfaced as 0x80070003. Rebuilding the store forces a clean catalog download and a complete payload, which removes the stale references rather than trying to patch them one file at a time.

Variants and edge cases

0x80070003 after disk cleanup or storage sense ran

Cleanup tools sometimes remove partly downloaded updates. Rebuild the store as above and exclude the update download folder from third-party cleaners afterward.

0x80070003 on WSUS clients only

If every WSUS client shows the code but direct update works, the WSUS content store may be missing the payload. Resynchronize content and check the WSUS content folder permissions and free space.

0x80070003 returns on a brand new download store

A repeat on clean downloads suggests drive errors or security software deleting payloads mid-download. Run a disk check and review antivirus quarantine history for the download folder.

Compatibility: Applies to Windows 10, Windows 11, and Windows Server 2016 and later. Folder changes need administrator rights.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6GeCprSH4OxkNravzS3iCQ