Error 0x80070003 is Windows Update telling you it went looking for files it needs and found an empty shelf. The update cache — where Windows stages downloads before installing them — has gotten into a corrupted state, so every retry fails the same way. It’s frustrating, but it’s also one of the most straightforward update errors to fix.
The core repair is simple: stop the update services, clear the broken cache, and let Windows rebuild it fresh. Work through these in order. If you’re hitting a different code, see our guides for error 0x80073712 (component store damage) or error 0x80070057 .
Why this happens
- Corrupted SoftwareDistribution cache: Interrupted downloads leave partial or mismatched files that the installer can’t use.
- Failed previous update: An update that didn’t complete cleanly leaves the cache and the catroot2 signature store in an inconsistent state.
- Disk errors: Bad sectors or file system corruption in the Windows folder damage cached update files over time.
- Third-party antivirus interference: Kernel-level security software sometimes quarantines or blocks update files mid-download.
- Insufficient disk space: Updates that run out of room mid-stage produce truncated files that fail verification.
- Metered or unstable connection: Downloads interrupted repeatedly by connection drops create the same partial-file corruption.
- Stuck BITS transfer queue: The Background Intelligent Transfer Service can hold a wedged download job that poisons every subsequent attempt until the queue is cleared.
How to fix it
Work through these in order — start with Fix 1 and stop as soon as updates install successfully.
Fix 1: Run the Windows Update troubleshooter
Worth two minutes — it automates the basic cache reset for simple cases.
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Click Run next to Windows Update.
- Apply whatever it recommends and restart.
- Retry the update in Settings > Windows Update. If 0x80070003 persists, continue — the troubleshooter rarely fixes entrenched cache corruption.
Fix 2: Reset the Windows Update components manually
This is the definitive fix for 0x80070003: clear the broken cache completely and let Windows rebuild it. It looks like a lot of commands, but the whole thing takes about two minutes.
- Open an administrator Command Prompt (Win + S, type
cmd, right-click, Run as administrator). - Stop the update services with these commands, one at a time:
net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserver - Rename the cache folders so Windows rebuilds them fresh:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 Catroot2.old - Restart the services:
net start wuauservnet start cryptSvcnet start bitsnet start msiserver - Restart the laptop, then check for updates again. The first check takes longer than usual while the cache rebuilds.
- If the error returns immediately after a clean reset, don’t just repeat the reset — move on to the disk and antivirus checks below, because something is re-corrupting the cache.
Fix 3: Free up disk space
A cramped system drive is a repeat offender for this error — give the updater room to work.
- Open Settings > System > Storage.
- Click Cleanup recommendations and remove temporary files, old downloads, and unused apps — aim for at least 20 GB free on C:.
- Empty the Recycle Bin and clear Temporary files via Settings > System > Storage > Temporary files.
- If space is still tight, move personal files (photos, videos) to an external drive.
- Retry the update with breathing room.
Fix 4: Check the disk for errors
Since disk corruption is a common root cause, verify the drive before retrying endlessly.
- Open an administrator Command Prompt.
- Run
chkdsk C: /fand press Y when asked to schedule it at the next restart. - Restart and let the scan complete — don’t skip it.
- After booting, repeat Fix 2’s component reset, then retry the update.
- If CHKDSK keeps finding errors on every run, the drive may be failing — back up your data promptly.
Fix 5: Temporarily disable third-party antivirus
Security software that hooks file writes can corrupt update downloads in transit.
- Open your third-party antivirus and disable real-time protection temporarily (keep Windows Security enabled).
- Run Fix 2’s component reset to clear any files the AV already damaged.
- Retry the update with the third-party AV still disabled.
- Re-enable your antivirus immediately after the update succeeds.
- If this was the cause, add the C:\Windows\SoftwareDistribution folder to your AV’s exclusions to prevent recurrence.
Fix 6: Install the failing update manually
Bypass the broken pipeline entirely by installing the KB directly.
- In Settings > Windows Update > Update history, note the exact KB number that’s failing.
- Visit the Microsoft Update Catalog and search for that KB number.
- Download the x64 version matching Windows 11 24H2.
- Double-click the
.msufile and follow the prompts, then restart. - Afterward, still run Fix 2 once so future automatic updates use a clean cache.
Fix 7: Repair system files and do an in-place upgrade if needed
For stubborn cases where the error survives everything above, the servicing stack itself may be damaged.
- Open an administrator Command Prompt.
- Run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealth. - Restart and retry the update.
- If it still fails, do an in-place upgrade: download the Windows 11 ISO from the Windows 11 download page , mount it, run setup.exe, and choose Keep personal files and apps.
- This reinstalls Windows over itself, rebuilding the update machinery while preserving everything.
Closing
Error 0x80070003 is almost always a corrupted update cache, and the manual component reset in Fix 2 resolves it for the vast majority of laptops. The key is doing it properly — stopping all four services before renaming the folders, then restarting cleanly. If the error keeps returning, look deeper: check your disk health, give the drive more free space, and keep third-party antivirus from interfering during updates. And remember the golden rule of Windows updates: never force-shutdown while an update is installing. That single habit prevents most cache corruption in the first place.
