| Previous | Next |
| STATEREPOSTORY_E_NESTED_TRANSACTION_NOT_SUPPORTED | ERROR_VOLSNAP_BOOTFILE_NOT_VALID |
STATEREPOSITORY_ERROR_CACHE_CORRUPTED
Within Windows StateRepository, STATEREPOSITORY_ERROR_CACHE_CORRUPTED reports that StateRepository detected invalid derived cache data.
Facts that change the diagnosis
- Cache identity and generation.
- Authoritative repository validation.
- Build or servicing history.
- First operation detecting invalid cache.
Subsystem meaning
StateRepository is infrastructure for the Windows application model. The HRESULTs expose distinctions familiar from transactional stores: optimistic concurrency, an unfinished prepared statement, database-versus-table locking, shared-cache contention, recovery, schema compatibility, corruption, and service shutdown. These are not interchangeable reasons to delete the repository.
Cache corruption should be separated from corruption of authoritative dictionary or repository records. A supported cache rebuild may be appropriate only after provenance and integrity evidence show that underlying state is sound.
Inspect the StateRepository request, database connection, prepared statement, transaction, schema generation, or service lifecycle that rejected the operation.
Isolation workflow
- First: Preserve the invalid cache for diagnosis.
- Next: Validate underlying repository data on a copy.
- Then: Use the supported cache regeneration path.
- Finally: Verify no deployment tool restores the stale cache.
Avoid the tempting broad fix
DICTIONARY_CORRUPTED identifies repository dictionary structures; CACHE_CORRUPTED identifies derived acceleration data.
Do not delete the whole repository when only cache validation failed.
Expected branches
| Control | Interpretation | Hold constant |
|---|---|---|
| Same database copy, isolated connections | A change points to connection/statement/transaction ownership rather than stored content. | Use a copy and preserve schema plus repository generation. |
| Same operation, controlled environment | If the result follows one machine, account, volume, network, or device, environment matters. | Keep versions and identity explicit rather than comparing only the final message. |
Regression proof
Verify it with the original scenario, one boundary case, and one deliberate failure; success means regenerated cache remains valid across restart and produces the same authoritative application-model state.
Technical references
Looking for a different code? Search another status or error code.