Windows System Errors
File Corrupted
0x80070570Reviewed for reference consistency: August 11, 2026
the file or directory is damaged and cannot be read
What 0x80070570 Means
The 0x80070570 error on the Windows System Errors indicates file corrupted — the file or directory is damaged and cannot be read. This typically occurs due to component store files no longer match the structure servicing expects.
A read that comes back structurally damaged raises 0x80070570, Win32 error 1392, ERROR_FILE_CORRUPT — 'The file or directory is corrupted and unreadable'. Windows Update troubleshooting lists the code under component store corruption, with the documented repair being DISM RestoreHealth followed by System File Checker, and a dedicated guidance page for the code itself.
How to fix 0x80070570
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Repair the component store from update sources
RestoreHealth scans the store and replaces damaged components, using update sources or a supplied alternative for clean copies.
Dism.exe /Online /Cleanup-Image /RestoreHealthVerify protected system files afterwards
Running System File Checker after the store repair lets it draw on repaired references for any remaining mismatches.
sfc /scannow
Technical Background
Corruption here is structural: the bytes on disk no longer parse as the file system or the payload format expects. That is a stronger claim than a missing file, because the record exists and refuses to behave. The component store is a common site — thousands of hard-linked files whose consistency servicing depends on — which is why update failures and this code travel together so often.
The documented repair order has a logic to it. DISM RestoreHealth rebuilds the component store's damaged pieces from update sources, and System File Checker then verifies protected system files against that repaired store. Running them in the documented sequence matters because SFC draws its replacement copies from the store the first command repairs.
Common Causes
- Component store files no longer match the structure servicing expects
- File-system metadata damage makes stored files unreadable
- A partially installed or partially downloaded package left inconsistent content on disk
Typical Scenarios
- Installing a cumulative update fails because a file the servicing stack needs to read is damaged in the component store
- File copies from an aging drive fail mid-transfer with the corruption message
- DISM or SFC output records unreadable files that a later repair pass must replace
What to Know
Repeating failures across unrelated files point at the storage layer beneath the file system; a single stubborn payload file points at that package's copy on disk.
Frequently Asked Questions
Common questions about Windows 0x80070570 error
No. WinError.h assigns 1392 to ERROR_FILE_CORRUPT ('The file or directory is corrupted and unreadable'); ERROR_DISK_CORRUPT is 1393 and describes disk-structure damage. The two are neighbors with different scopes.
SFC verifies protected files against the component store, while DISM repairs the store itself. When the store is the damaged party, the documented sequence runs RestoreHealth first so SFC has an intact reference to compare against.
Anywhere a read returns structurally unusable content — copying from a failing drive, opening a damaged archive — the same constant surfaces, because the file system layer reports one corruption code to all callers.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Git's internal object database is missing or corrupted.
The operating system denied Git's request for more RAM during a heavy operation.
Git detected corruption inside one of its compressed data bundles (packfiles).
An uncompressed file in Git's internal database has an invalid checksum or zero bytes.