| Previous | Next |
| ERROR_STATE_WRITE_SETTING_FAILED | ERROR_STATE_QUERY_SETTING_FAILED |
ERROR_STATE_DELETE_SETTING_FAILED
A state setting could not be deleted
ERROR_STATE_DELETE_SETTING_FAILED means the repository could not remove the named value. This is not equivalent to the value already being absent; callers should check the API contract and underlying result.
Investigation
- Verify the container and exact setting name.
- Check for concurrent readers, writers, or migration work.
- Confirm the repository and profile are writable.
- Inspect storage and State Repository events.
Handling
After a failure, read the value again before deciding whether cleanup is complete. For privacy or credential removal, treat an unverifiable delete as a serious failure and avoid claiming that data was erased.
Security-sensitive deletion
When the value contains credentials, consent, or personal information, verify removal through the same authoritative API. Deleting a cached copy while the persistent record remains is not sufficient.
Idempotent cleanup
Cleanup code should treat a confirmed missing value as success, but it should preserve storage and permission failures. This distinction allows repeated uninstall or reset operations without concealing genuine data-retention problems.
References
Looking for a different code? Search another status or error code.