| Previous | Next |
| ERROR_CANTREAD | ERROR_REGISTRY_RECOVERED |
ERROR_CANTWRITE
A configuration registry write could not be completed
Registry write operations change a value, key, or other configuration state and may fail after the target key has already been opened successfully. ERROR_CANTWRITE therefore points at the write stage rather than name resolution or key opening.
Inspect the access mask used to open the key, the value type and byte count passed to the write API, and the ownership of the configuration branch. RegSetValueEx requires the appropriate set-value right; callers should also avoid writing volatile runtime data into persistent system configuration merely because a key is available. If the same hive reports I/O, log-space, quota, or corruption errors, treat this status as a symptom of the broader registry storage problem. Retrying the same write without changing the underlying condition can create a noisy loop without preserving configuration.
What to inspect
- Verify KEY_SET_VALUE or the specific required access was requested.
- Log value type and byte length exactly as passed to the registry API.
- Correlate the failure with hive I/O, quota, or recovery events.
References
Looking for a different code? Search another status or error code.