| Previous | Next |
| ERROR_CORRUPT_LOG_CORRUPTED | ERROR_CORRUPT_LOG_DELETED_FULL |
ERROR_CORRUPT_LOG_UNAVAILABLE
the volume corruption log cannot currently be accessed.
ERROR_CORRUPT_LOG_UNAVAILABLE means that this condition The log may exist but is unavailable because the volume state, file-system operation, lock, dismount, repair phase, or internal error prevents access. The result is about availability of the tracking mechanism, not a definitive count of corruptions.
Where the result appears
- health queries during mount, dismount, scan, or repair transitions.
- storage agents racing file-system maintenance.
- clustered volumes moving between owners.
- file-system control operations that require the corruption log.
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
- volume lifecycle state and ownership at the time of the request.
- active scan, scrub, repair, snapshot, or dismount operations.
- the original file-system status preceding this Win32 translation.
- whether the same query succeeds after the volume becomes stable.
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
Wait for the current volume transition or maintenance operation to finish, then query again. If unavailability persists in a stable state, collect file-system events and perform a controlled scan instead of assuming the volume is healthy.
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
“Unavailable” is not the same as “empty.” Absence of readable records does not prove absence of corruption.
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.