Windows Update Error 0x80070002: The Missing File Fix

Cause 1: Corrupted Update Cache (The Most Common Fix)

I know this error drives people nuts. It shows up right when you think the update will finally install. The real culprit is almost always a corrupted cache in the SoftwareDistribution folder. Over time, partial downloads and failed updates leave junk files that Windows can’t read, triggering the 0x80070002 error.

How to fix it

1. Open Command Prompt as administrator. Hit Win + X and pick “Terminal (Admin)” or “Command Prompt (Admin)”.
2. Stop the update services by typing these commands, one by one:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

Wait a few seconds after each. If they’re already stopped, you’ll get a message—that’s fine.

3. Rename the cache folders. This is safer than deleting them outright:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old

Windows will recreate fresh versions when you restart the services.

4. Restart the services:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Now run Windows Update again. This fix works for about 70% of cases—seriously. I’ve used it on dozens of machines, from Windows 10 22H2 to Windows 11 23H2.

Cause 2: Low Disk Space on the System Drive

This tripped me up the first time, too. The error message doesn’t mention disk space, but Windows Update needs a few GB free to download and stage files. If your C: drive has less than 10 GB free, updates will fail with 0x80070002. It’s especially common on laptops with small SSDs (128 GB or less).

How to check and fix

1. Open File Explorer, right-click your C: drive, and select Properties. Look at “Free space”.
2. If it’s below 10 GB, run Disk Cleanup. Search for “Disk Cleanup” in the Start menu, select the C: drive, and click “Clean up system files”. Check boxes for:

• Windows Update Cleanup
• Delivery Optimization Files
• Recycle Bin
• Temporary files

This can free up several GB. I’ve seen it reclaim 5–8 GB on a crowded system.

3. If you still need more space, disable Hibernate and shrink the page file:

powercfg -h off

That removes the hiberfil.sys file, which can be 4–16 GB. Then go to System Properties > Advanced > Performance > Advanced > Virtual memory, and set a custom size — I usually set it to 4096 MB min and max. This puts a hard cap on it.

After freeing space, restart and try the update again. I’ve fixed 0x80070002 this way on a Dell Latitude with a 128 GB SSD running Windows 10.

Cause 3: System File Corruption (SFC + DISM)

If the cache is fresh and you’ve got plenty of disk space, the real problem is likely corrupted system files. The 0x80070002 error often hides deeper corruption, especially in the Component Based Servicing (CBS) log. Windows Update can’t find the file it needs because the file’s registry entry points to a broken or missing location.

How to repair

1. Open an elevated Command Prompt (Admin).
2. Run the System File Checker first. This scans and replaces protected system files:

sfc /scannow

This can take 15–30 minutes. If it finds corruption, reboot and run it again until it says “Windows Resource Protection found no integrity violations”. No shortcuts here.

3. Next, run DISM to fix the component store. This is the heavy lifter:

DISM /Online /Cleanup-Image /RestoreHealth

This command uses Windows Update itself to pull clean files—ironic, I know. If your internet is slow or unstable, you can point it to a Windows installation media instead. Insert a USB or DVD, note its drive letter (say, D:), and run:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess

Make sure the .wim file is there. On Windows 11 23H2 media, it’s in the sources folder. I’ve used this trick on networks where Windows Update was blocked by a corporate proxy.

4. After DISM finishes (usually 10–20 minutes), run sfc /scannow one more time. This catches any remaining issues DISM left behind.

If the error still shows up after all this, look at the CBS.log file at C:\Windows\Logs\CBS\CBS.log. Open it in Notepad and search for “0x80070002”. You’ll see the exact file path Windows can’t find—it’s usually a .manifest or .mum file. If you’re comfortable, you can restore that file from a healthy copy of Windows. For most people, though, it’s easier to use the Windows Media Creation Tool to do an in-place upgrade. That replaces all system files without touching your apps or data.

Quick Reference: Fixes for Error 0x80070002

Start with the first fix—it’s quick and covers most cases. If that doesn’t work, move to disk space, then system file repair. And if you’re still stuck, don’t reset your PC just yet—try the in-place upgrade. It’s saved me more times than I can count.