Windows Update

Windows Update error 0x8007000d: what it means and how to fix it

Error 0x8007000d means Windows Update downloaded invalid or corrupted data. Run the troubleshooter, clear the update cache, download again, then repair with DISM.

By EpiFive Editorial TeamSources checked How we check our guides

What the error means

0x8007000d is the Windows error ERROR_INVALID_DATA, whose standard text is "The data is invalid." When Windows Update reports it, Microsoft's explanation is specific: data that isn't valid was downloaded, or something in the Windows Update files or update cache is corrupted. Windows tried to read an update package it had stored, the contents did not check out, and the install stopped.

That makes this one of the more predictable update errors. The problem usually sits in files Windows downloaded, not in your documents or apps, so the documented fixes are about throwing the bad copy away and fetching a clean one. Only if that fails do you need to repair Windows itself.

The same hex value can appear in other tools. If you see it in dsregcmd /status output during a Microsoft Entra hybrid join, read Fix Microsoft Entra hybrid join failures instead, because the cause there is different. For the wider set of update failures, see Windows 11 update stuck or failing.

Common causes

  • A download that was interrupted or arrived damaged, leaving an invalid package in the cache.
  • Corruption in C:\Windows\SoftwareDistribution, the folder Windows Update uses to stage downloads.
  • Damaged system files in the component store, which stop a good package from installing.
  • A PC that is several updates behind, which Microsoft's upgrade page addresses with "Ensure your system is fully updated."

How to fix it

1. Run the Windows Update troubleshooter

On Windows 11 select Start, Settings, System, then Troubleshoot and Other troubleshooters. Find Windows Update and select Run, then follow the prompts. This is the first step Microsoft lists for 0x8007000d, and it resets several update components for you.

2. Clear the Windows Update cache

This is the fix Microsoft pairs with this code on its troubleshooting page.

  1. Press Win + R, type services.msc and press Enter.
  2. Right-click the Windows Update service and select Stop.
  3. Open C:\Windows\SoftwareDistribution and delete all files and folders inside it. Leave the folder itself in place.
  4. Go back to Services, right-click Windows Update and select Start.

3. Download the update again

Go to Settings, Windows Update and select Check for updates. Microsoft's mitigation for 0x8007000d is to redownload the update and then start the installation, which happens automatically once the cache is empty. Keep the PC awake and connected until the download finishes.

4. Repair system files with DISM and SFC

If the fresh download fails with the same code, repair the component store. Open Command Prompt as administrator and run the commands below in order. Wait for DISM to report that the restore operation completed successfully before starting SFC, and let SFC reach 100%.

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Restart and check for updates again.

If nothing works

DISM records its results in %windir%\Logs\CBS\CBS.log. Search it for corruption entries near the time of the failure. If DISM cannot reach Windows Update to fetch clean files, Microsoft documents running it with a /Source that points to a working Windows installation of the same version, followed by /LimitAccess. When an update still will not install after a repaired component store, the last item on Microsoft's troubleshooting page is a clean installation of Windows, so back up your files first or contact Microsoft support before going that far.

What we checked

On 2026-11-19 we read four Microsoft pages that list 0x8007000d. The Windows Update troubleshooting page on support.microsoft.com describes it as a problem with update files or cache corruption and gives the troubleshooter and cache-clearing steps. The Microsoft Learn list of common Windows Update errors calls it ERROR_INVALID_DATA and recommends downloading the update again. The Learn article on fixing update corruption lists it with the description "The data is invalid" and documents DISM, and the upgrade errors page recommends the troubleshooter, updating fully, and SFC with DISM. We did not reproduce the error ourselves.

Last checked: 2026-11-19.

Official sources

Questions people ask

What causes Windows Update error 0x8007000d?

Microsoft says the update data that was downloaded is not valid, or the Windows Update files or cache are corrupted. That is why its fixes focus on clearing the cache and downloading the update again.

Is it safe to delete the SoftwareDistribution folder contents for 0x8007000d?

Microsoft documents it as a fix for this code: stop the Windows Update service, delete the contents of C:\Windows\SoftwareDistribution, then start the service again. Windows downloads what it needs on the next check.

I see 0x8007000d in dsregcmd output, not Windows Update. Is it the same problem?

The code is the same general "invalid data" error, but the cause differs. In a Microsoft Entra hybrid join it usually means a response could not be parsed, which is a different troubleshooting path from a failed update.

  • 0x800f081f (Windows Update)

    Error 0x800f081f means Windows could not find the source files it needed, during an update, a DISM repair or a .NET Framework 3.5 install. Here are the documented fixes.

  • 0x80073712 (Windows Update)

    Error 0x80073712 means the Windows component store is damaged, so a file Windows Update needs is missing. Repair it with DISM and SFC, then update again.

  • 0x80070002 (Windows Update)

    Windows Update error 0x80070002 means a file the update needs could not be found. Restart, run the troubleshooter, free space, then repair the update files.

  • 0x800f0922 (Windows Update)

    Error 0x800f0922 means an update could not install, most often because of low disk space, a VPN blocking the update servers or a full System Reserved partition.

Not your code?

Search the error code library, or report a code we don't cover. Spotted something out of date on this page? Report a correction.