| Previous | Next |
| ERROR_CANTWRITE | ERROR_REGISTRY_CORRUPT |
ERROR_REGISTRY_RECOVERED
The most likely reason for this error is the computer restarting with the Reset button. But the problem could be more serious. For example, hardware problems with memory modules. If the problem persists, it makes sense to test the equipment. This problem can also be caused by virus infection and malfunctioning of disk drivers.
Where ERROR_REGISTRY_RECOVERED is returned
This result is Win32 system error 1014 (0x000003F6) from winerror.h. AllStat describes it as “One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.”. The code is useful only together with the API that failed, because multiple Windows components can reuse system-error values while imposing different retry and cleanup rules.
Diagnostic sequence
- Call GetLastError immediately after the failing API and save this result, the function name, all relevant flags, and the target path, handle, service, device, account, or policy object.
- Capture the component log that owns the registry / recovered operation and retain the original numeric value before a framework converts it to an HRESULT or exception.
- compare preconditions with the API documentation and reproduce with a minimal request before changing system-wide configuration.
Retry this result only after the resource or state named in “One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.” has changed. For invalid parameters, unsupported formats, missing objects, policy restrictions, and access failures, correct the input or configuration instead of immediately repeating the same call.
Official references
Looking for a different code? Search another status or error code.