0X80070570
What it means
Windows found file system corruption — could be the drive itself, a bad copy operation, or a failing disk.
Also seen as: 0x80070570
Quick fix steps
- Run "chkdsk /f /r" on the affected drive and restart to let it complete.
- Retry the file operation after the scan completes.
- Back up important data if this recurs, as it can indicate a failing drive.
For the full step-by-step walkthrough, see "Disk Error" or "Windows Detected a Hard Disk Problem".
Frequently Asked Questions
Does "the file or directory is corrupted" mean I'm losing that file?
It means Windows can't currently read that specific file cleanly — running chkdsk can often repair the underlying issue and recover access, though severe corruption can sometimes mean the file itself is unrecoverable.
Is this a sign my whole drive is failing?
Not necessarily on its own — an isolated instance is often just an isolated file system error. Repeated occurrences across different files are more concerning and worth checking drive health for.
Other error codes
0X8007002C — Unspecified Error During Copy/Install
Often appears during large file copies or installs and points to file system errors or a flaky connection to an external/network drive.
0X80071AC3 — The File System Is Corrupted
A more explicit version of file system corruption, often seen on external or removable drives.
0X80070017 — The Cyclic Redundancy Check Failed
Data on the disk is corrupted and failed an integrity check — often points to physical drive damage or a bad copy/burn.
0X80070780 — The File Cannot Be Accessed by the System
A specific file is locked, corrupted, or the drive has a developing hardware issue preventing access.