| Previous | Next |
| ERROR_CORRUPT_LOG_DELETED_FULL | ERROR_ORPHAN_NAME_EXHAUSTED |
ERROR_CORRUPT_LOG_CLEARED
chkdsk cleared a corruption log and its former records are no longer current.
ERROR_CORRUPT_LOG_CLEARED means that this condition This status accompanies a maintenance transition in which chkdsk has processed or invalidated the previous corruption records. Consumers must stop treating those entries as an active list and obtain the new volume health state.
Where the result appears
- post-chkdsk file-system health reporting.
- management agents that cache corruption records.
- repair workflows comparing pre-scan and post-scan state.
- volume monitoring immediately after offline maintenance.
What the result tells you
The value identifies a specific Windows state, but it does not by itself identify the component that introduced that state. Preserve the original this result value, the API or subsystem that produced it, and the object being operated on. A wrapper that replaces it with a generic exception or Boolean failure removes the distinction needed to choose the correct recovery path.
Diagnostic evidence to collect
- the complete chkdsk result and whether repairs succeeded.
- the new volume dirty and health state.
- fresh scan results after remount.
- which cached corruption entries were invalidated.
Correlate the result evidence on one timeline. The first event that changes the state associated with this result is usually more valuable than later retries returning the same code. Record process and thread identity, session, timestamp, API parameters, and the immediately preceding successful operation.
Handling and recovery
Refresh health information from the volume and archive the old list only as historical evidence. If chkdsk reported failures, follow those results; the fact that the log was cleared does not override an unsuccessful repair.
Retry after this result only when the evidence shows that an external condition can change. When it is caused by malformed input, revoked authority, unsupported state, hardware damage, or an offline maintenance requirement, an unchanged retry adds noise and can overwrite the earliest useful diagnostics.
Common misinterpretation
“Cleared” describes the tracking log. It should not be simplified to “all storage problems are fixed” without checking the chkdsk outcome.
Guidance for developers
Keep it in its Win32/LRESULT domain in structured telemetry. When converting it to an HRESULT, exception, RPC response, or JSON field, retain the source domain and numeric value alongside the human-readable text. Do not branch on the localized message string for it.
A it test should construct the specific state, assert the exact result, and verify that partial resources are released. The recovery test for it should prove that the operation is either deferred until a measurable state change or fails without an uncontrolled retry loop.
References
Looking for a different code? Search another status or error code.