| Previous | Next |
| ERROR_CORRUPT_LOG_UNAVAILABLE | ERROR_CORRUPT_LOG_CLEARED |
ERROR_CORRUPT_LOG_DELETED_FULL
a corruption log was deleted while it still contained unresolved records.
ERROR_CORRUPT_LOG_DELETED_FULL means that this condition Known corruption entries were present when the tracking log was removed. Windows can no longer use that list to drive targeted repair, but the underlying volume still contains damage that requires a scan.
Where the result appears
- administrative clearing of file-system health metadata.
- repair tooling that recreates a log prematurely.
- recovery after log deletion or metadata rollback.
- storage management software reporting loss of pending repair records.
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
- who or what deleted or reset the log.
- the last exported corruption records, if available.
- volume scan and repair history.
- current dirty state, health state, and a fresh complete scan.
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
Treat the volume as having unresolved corruption. Back up important data and run a complete supported scan so Windows can rediscover damage rather than relying on the deleted record set.
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
Removing the record of corruption does not remove corruption. This status explicitly warns that unresolved entries existed at deletion time.
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.