| Previous | Next |
| ERROR_MEMORY_HARDWARE | ERROR_INSUFFICIENT_RESOURCE_FOR_SPECIFIED_SHARED_SECTION_SIZE |
ERROR_DISK_REPAIR_DISABLED
the attempted operation required self-healing to be enabled.
ERROR_DISK_REPAIR_DISABLED means that this condition Windows file systems can perform selected repairs while a volume remains online. This result means the requested repair depended on that self-healing path, but policy, volume state, or file-system configuration had disabled it.
Where the result appears
- a file-system control request that asks the volume to repair detected corruption.
- storage management software that invokes online repair facilities.
- a service reacting to corruption records without taking the volume offline.
- maintenance code running under a policy that disables automatic healing.
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 affected volume GUID, drive letter, file-system type, and dirty-bit state.
- the command or FSCTL that requested repair and the caller token.
- self-healing and repair policy settings in effect on the machine.
- NTFS, ReFS, or storage event-log entries immediately before the failure.
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
Do not repeatedly submit the same repair request. Determine why online healing is disabled, then either enable the supported policy or schedule an offline scan and repair during a controlled maintenance window. Back up important data first when corruption is already known.
Retry after it 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
This status does not prove that the disk surface is physically damaged. It specifically says that the chosen repair mechanism is unavailable; the underlying corruption may still be logical.
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.