Fix error 0x80070570
0x80070570 is ERROR_FILE_CORRUPT: the file or directory is corrupted and unreadable. Microsoft lists damaged update downloads, a corrupted component store, disk errors and security software interference as causes. Clear the SoftwareDistribution Download folder, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, then chkdsk C: /f /r.
Checked November 10, 2026 against the manufacturer's own pages.
The short version
What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.
Official files only, nothing bundled
Step by step
Back up anything important
Microsoft's own article starts with a backup of the system disk, because disk repair can touch damaged files. Copy your documents to another drive or to OneDrive first.
Empty the update download cache
Open Terminal (Admin) and run these one by one: net stop wuauserv, net stop bits, rd /s /q %windir%\SoftwareDistribution\Download, net start bits, net start wuauserv. Restart and try the update again.
Repair the component store
If the update still fails, run DISM /Online /Cleanup-Image /RestoreHealth in the same admin window. DISM uses Windows Update as its repair source by default. Restart afterward.
Check system file integrity
Run sfc /scannow. If it reports repairs, restart and retry. You can also run sfc /verifyonly first to scan without changing anything.
Check the disk with chkdsk
Run chkdsk C: /f /r and answer Y to schedule it at the next restart. Restart and let it finish; it can take a long time on a large drive. Then retry the update or file operation.
Download installers again
If the code comes from a program or game installer, delete the downloaded setup file and get a fresh copy. For Windows installation media, create a new USB stick with Microsoft's Media Creation Tool.
Faster option: let a PC tool do the clean-up
The steps above fix this error. Errors like this often come back on a PC full of junk files, broken registry entries and leftovers from removed programs. A maintenance tool clears those in one scan.
Scan and clean up Windows
Finds junk files, invalid registry entries, startup slowdowns and privacy traces, then fixes them in one click.
Auslogics BoostSpeed 14 · Free version · Windows 11, 10, 8, 7 · 30-day refund on Pro
What corrupted and unreadable means here
Win32 error 1392 has a direct message: the file or directory is corrupted and unreadable. Windows tried to open something and the data on disk, or the structure that points to it, did not make sense. With updates, the damaged item is usually a downloaded package or a manifest in the component store under C:\Windows\WinSxS. With file copies, it is more often the file system on the drive itself.
Update cache, component store or disk?
Microsoft’s troubleshooting article orders the fixes from lightest to heaviest, and that order also helps tell causes apart. If clearing the download folder fixes it, a partial or broken download was the cause. If DISM is needed, the component store held damaged files. If only chkdsk helps, the volume had file system errors or bad sectors. When chkdsk finds bad sectors more than once, the drive may be failing, so check it with the drive maker’s tool and plan a replacement.
A less common cause: truncated downloads from interrupted sessions
Microsoft also lists update files that are partial because the download was cut off. Laptops that sleep during updates, metered connections and flaky Wi-Fi can leave such files behind. Keep the PC plugged in and awake while updates download, and turn off Settings, Network and internet, Wi-Fi, your network, Metered connection if it is on and you have no data cap.
Questions
Which name is right: ERROR_FILE_CORRUPT or ERROR_FILE_OR_DIRECTORY_CORRUPTED?
Both appear on Microsoft pages for the same code. The Win32 error list names 1392 ERROR_FILE_CORRUPT, and Microsoft's update troubleshooting article shows ERROR_FILE_OR_DIRECTORY_CORRUPTED as it appears in CBS logs.
Can antivirus cause 0x80070570?
Microsoft lists security software that interferes while Windows Update extracts files as one cause. Keep Windows Security on. If you use another product, check its quarantine log and update it.
I get 0x80070570 when copying to a USB stick. What now?
The source file or the stick has damaged file system data. Run chkdsk E: /f on the stick, using its real letter, and try another port. If it repeats, copy the file from another source.
Where do I see more detail?
Microsoft points to WindowsUpdate.log and CBS.log in C:\Windows\Logs\CBS. Entries show the package that failed with HRESULT 0x80070570.