| Previous | Next |
| ERROR_DISK_REPAIR_REDIRECTED | ERROR_CORRUPT_LOG_OVERFULL |
ERROR_DISK_REPAIR_UNSUCCESSFUL
the requested volume repair did not complete successfully.
ERROR_DISK_REPAIR_UNSUCCESSFUL means that this condition A file-system repair operation ran but could not correct all targeted damage. Remaining corruption, unreadable media, insufficient workspace, conflicting opens, or a deeper storage failure may prevent completion.
Where the result appears
- chkdsk, online scan, or file-system self-healing results.
- storage-management software collecting repair outcomes.
- boot-time repair of a system volume.
- cluster or virtual-disk maintenance where underlying storage remains unhealthy.
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 full chkdsk or file-system repair log, not only the final code.
- bad-cluster, unreadable-sector, and storage-controller events.
- free space, volume snapshot state, and open handles.
- post-repair dirty bit and a second read-only scan result.
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
Protect data first. Capture the repair log, run hardware diagnostics, clone or back up readable data, and escalate to an offline repair or storage replacement as indicated. Repeatedly running repair on failing media can increase stress without restoring missing data.
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
An unsuccessful repair is not equivalent to a harmless “no changes needed” result. It means the requested corrective work did not reach a successful conclusion.
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 this Win32 error.
A test should construct the specific state, assert the exact result, and verify that partial resources are released. The recovery test for this Win32 error 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.