This error occurs if one of the following conditions exists:

• Downloaded update files in the %windir%\SoftwareDistribution\Download folder are corrupted.
• The Windows component store (in the %windir%\WinSxS folder) contains corrupted manifests or files.
• The system volume is corrupted (for example, the disk might have bad sectors or file system errors).
• An antivirus or security application interferes when Windows Update extracts files from downloaded update packages.
• The update files are truncated or partial because the download process was interrupted.

Note

%windir% represents the Windows system folder. The default folder name and location is "C:\Windows."

Microsoft guidance: 0x80070570 (ERROR_FILE_CORRUPT) untested here · 0 fixed, 0 not

Error text on Microsoft's page: The file or directory is corrupted and unreadable. Component Store corruption

Repair the component store by running Dism RestoreHealth, or manually repair by using the payload from the partially installed component. In an elevated Command Prompt window, run these commands: Dism.exe /Online /Cleanup-Image /Restorehealth Sfc.exe /Scannow Restart the device. For more information, see Troubleshoot Windows Update error 0x80070570.

Log how it went

(Enterprise subscription only)

Resolution: Troubleshoot Windows Update Error 0x80070570 untested here · 0 fixed, 0 not

Important

Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see About Azure Virtual Machine restore.

Step 1: Clear the Windows Update cache

To delete corrupted download files and force Windows Update to download new copies, open a Command Prompt window, and then run the following commands:

net stop wuauserv
net stop bits
rd /s /q %windir%\SoftwareDistribution\Download
net start bits
net start wuauserv

After you run these commands, restart the computer, and try again to install the update. If the update still doesn't install, go to step 2.

Step 2: Repair the component store

To repair the component store, run the following command at the command prompt:

DISM /Online /Cleanup-Image /RestoreHealth

Note

By default, DISM uses Windows Update as a repair source. For information about how to specify a different repair source, see Repair a Windows Image.

After you run this command, restart the computer, and try again to install the update. If the update still doesn't install, go to step 3.

Step 3: Check system file integrity

To verify the integrity of the system files, run the following command at the command prompt:

sfc /scannow

If this command identifies issues, see Use the System File Checker tool to repair missing or corrupted system files.

After this command finishes without errors, restart the computer. Try again to install the update. If the update still doesn't install, go to step 4.

Step 4: Check disk integrity

To check for disk issues, follow these steps:

1. On the affected computer, open a Command Prompt window, and run the following command:

   chkdsk C: /f /r
   

2. When prompted, confirm that you want to scan the operating system disk when the computer restarts.

3. Restart the computer. The tool automatically repairs any problems that it finds.

   Important

   If the affected computer is an Azure VM, and you use the Azure portal to monitor and remediate disk health, go to the next step of this procedure. You still have to restart the VM that uses the disk.

4. After the tool finishes, restart the computer, and try again to install the update. If the update still doesn't install, take one of the following actions:

   • If the affected computer is a VM, go to step 5.
   • Contact Microsoft Support for assistance.

Step 5: Use the Run Command reset tool (Azure)

If the previous steps don't resolve the issue on an Azure VM, try the Azure VM Windows Update Reset Tool. You can run the tool directly from the VM's Azure portal page by using Operations > Run command. When you use this method, you don't have to sign in to the VM.

This tool resets the Windows Update servicing stack. This action clears memory-related lock states in the update agent.

After you run the tool, try again to install the update. If it still doesn't install, go to step 6.

Step 6: Use a repair VM (Azure)

If the reset tool doesn't fix the issue, or the VM can't start:

1. Create a repair VM by using Azure VM repair commands.

2. Attach the affected operating system disk to the repair VM.

3. Make sure that you have an offline operating system image available, and then run the following command at the command prompt:

   DISM /Image:<Drive>:\ /Cleanup-Image /RestoreHealth
   

   Note

   • In this command, <Drive> represents the drive letter of the affected operating system disk.
   • By default, DISM uses Windows Update as a repair source. For information about how to specify a different repair source, see Repair a Windows Image.

4. Run the following command at the command prompt:

   chkdsk <Drive>: /f /r
   

   Note

   In this command, <Drive> represents the drive letter of the affected operating system disk.

5. To verify the integrity of the system files, run the following command at the command prompt:

   sfc /scannow /offwindir \<Drive>:%windir%
   
   
   

6. Reattach the repaired disk to the original VM.

7. Try again to install the update. If the update still doesn't install, contact Microsoft Support for assistance.

Log how it went

(Enterprise subscription only)

Repair-WindowsComponentStore untested here · 0 fixed, 0 not

Repair the Windows component store. Runs DISM ScanHealth, CheckHealth and RestoreHealth, then sfc /scannow.