How to Fix Windows Update Error 0x8007000D on Windows 10

What error 0x8007000D means

The trailing 0D is Win32 error 13, “The data is invalid” — the updater has the file, but its contents fail validation, or a registry record points to data that no longer matches what is on disk. On Windows 10 this typically follows an interrupted download or an install cut off mid-write: the cache ends up holding half-written packages, and every retry trips over the same broken file. Less often, the component store itself (the WinSxS folder that holds all update payloads) carries corruption the installer refuses to work with.

Because the cause is damaged data rather than a blocked permission, every fix revolves around repairing or discarding the bad data. The list below goes from the gentlest option to the most thorough. Each step also tells you what it found, so you learn whether corruption actually existed.

• A partially downloaded or damaged package in the SoftwareDistribution cache
• Corruption in the component store (WinSxS) that DISM can detect and repair
• Windows Update registry entries pointing at files that no longer exist
• Disk errors that silently corrupt freshly downloaded update data
• A servicing stack left half-configured by an interrupted install

The fix: troubleshooter, DISM repair and cache reset

Open Settings → Update & Security → Troubleshoot → Additional troubleshooters → Windows Update and run the troubleshooter first; it clears damaged transient data surprisingly often. Next, repair the system image: open Command Prompt as administrator and run DISM /Online /Cleanup-Image /RestoreHealth (expect 10–20 minutes), then sfc /scannow to fix any files the store could not supply. Both tools print a report at the end, so you can tell whether corruption actually existed.

If the error persists, reset the update cache: in the same admin prompt run net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver, then ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old. Start the services again (net start wuauserv, net start cryptSvc, net start bits, net start msiserver), reboot and run the update check once more. A chkdsk C: /f pass, scheduled for the next reboot, rules out the disk itself as the source of the corruption.

Manual installation from the Microsoft Update Catalog

When Windows Update keeps rejecting the same update, install it by hand. Find the KB number — either in Settings → Update & Security → Windows Update → View update history or in Microsoft's support announcement for this month's cumulative update — and search for it at catalog.update.microsoft.com. Download the .msu that matches your build: run winver to check the version number and pick the x64 (or x86) package for it. Double-click the file and the standalone installer applies the update through the same servicing machinery, bypassing the broken download path.

After a successful manual install, run the update check again: the update disappears from the queue, and error 0x8007000D does not return for it. The catalog carries cumulative and security updates alike, so this route covers essentially everything Windows 10 offers. If several updates keep failing even after DISM and a cache reset, that points to deeper store damage — and an in-place repair upgrade is the clean way out: run setup.exe from the Windows 10 ISO and choose to keep files and apps.

Questions and Answers

Read next

All articles · FAQ