| Previous | Next |
| STATUS_DIRECTORY_NOT_EMPTY | STATUS_NOT_A_DIRECTORY |
STATUS_FILE_CORRUPT_ERROR
STATUS_FILE_CORRUPT_ERROR indicates corruption affecting a particular file or directory. It is more specific than a general “file not found” or access error: the object was located, but the file system cannot read it reliably enough to complete the requested operation.
Why it should be treated as a data-protection event
Do not start by repeatedly writing to the affected volume. First preserve accessible data and collect the failing path, volume, and related system events. Microsoft describes chkdsk as a tool for checking file-system metadata and logical or physical errors, while its current troubleshooting guidance also calls for checking the underlying storage when corruption or disk errors recur.
Practical response
- Copy readable data to independent storage before repair work where possible.
- Run the appropriate file-system check in a maintenance window; the required options and downtime depend on the volume and file system.
- Review storage, controller, cable, virtual-disk, and network-path health when the error is not isolated.
- Do not assume a successful application retry proves the data is intact; validate important backups and application-level checksums.
STATUS_DISK_CORRUPT_ERROR is broader: it indicates that the file-system structure of the volume is corrupt and unusable. A file-corrupt result may be limited to a particular file or directory, but persistent cases can still point to a deeper storage problem.
See chkdsk, Microsoft data-corruption and disk-error guidance, and the NTSTATUS reference.
Looking for a different code? Search another status or error code.