| Previous | Next |
| ERROR_CORRUPT_LOG_OVERFULL | ERROR_CORRUPT_LOG_UNAVAILABLE |
ERROR_CORRUPT_LOG_CORRUPTED
the volume corruption log is itself damaged and must be recreated.
ERROR_CORRUPT_LOG_CORRUPTED indicates this condition: The structure used to record file-system corruption can no longer be trusted. Because the log may have lost or misrepresented entries, Windows warns that the volume can contain additional damage not reflected in the surviving records.
Where the result appears
- file-system health checks that open the corruption log.
- online repair infrastructure after metadata damage.
- storage telemetry following an unclean shutdown or I/O failure.
- maintenance operations that attempt to enumerate pending corruptions.
What to collect
- the file-system event describing why the log was rejected.
- volume dirty state and scan history.
- underlying disk, controller, and power-loss events.
- results of a complete read-only scan after the log is recreated.
Handling and recovery
Recreate the log through the supported file-system maintenance path, then scan the entire volume. Back up data before invasive repair, especially when other metadata errors or storage faults are present.
Common misinterpretation
Recreating the corruption log restores tracking, not necessarily the files or metadata that were already damaged.
References
Looking for a different code? Search another status or error code.