| Previous | Next |
| STATUS_SXS_IDENTITY_PARSE_ERROR | STATUS_SXS_FILE_HASH_MISMATCH |
STATUS_SXS_COMPONENT_STORE_CORRUPT
The shared side-by-side component store is corrupt
STATUS_SXS_COMPONENT_STORE_CORRUPT identifies a problem with the persisted store of shared side-by-side assemblies, commonly associated with the Windows component store, rather than with one private manifest beside an application. A valid application dependency can fail because its shared manifest or associated files are inconsistent in the store.
First establish the scope. If only one application fails and it uses a private assembly, an application-local package is more likely. If multiple unrelated applications fail while resolving shared identities, preserve the event details and use supported Windows servicing or recovery procedures rather than manually replacing files inside the component store.
What to inspect
- Determine whether the failing dependency is declared as shared or private and record the manifest path selected by the resolver.
- Check whether the same identity fails for a clean test application or only for one installed package.
- Do not delete or copy individual WinSxS files as a first response; preserve the component-store state for supported repair tools.
References
- Microsoft: application manifests
- Microsoft: assembly manifests
- Wine: activation-context implementation
Looking for a different code? Search another status or error code.