| Previous | Next |
| STATUS_SXS_MANIFEST_PARSE_ERROR | STATUS_SXS_KEY_NOT_FOUND |
STATUS_SXS_ACTIVATION_CONTEXT_DISABLED
The context exists but cannot be activated
STATUS_SXS_ACTIVATION_CONTEXT_DISABLED is about activation state, not manifest discovery. The process attempted to make a context active, but that context was disabled, so it cannot become the active context for the thread and its side-by-side API calls.
That makes it different from STATUS_SXS_CANT_GEN_ACTCTX, where Windows could not construct a context from manifest data at all. Preserve the handle lifetime and the path that disabled or invalidated it; rebuilding or replacing a manifest does not explain a later state change on an already-created context.
What to inspect
- Trace creation, reference management, activation and disable/zombification calls for the same context handle.
- Check thread boundaries: the active context is thread-associated and nested activation changes which context is on top.
- Use the failure point to find the earlier state transition instead of repeatedly attempting to activate the same disabled handle.
References
- Microsoft: activation contexts
- Microsoft: ActivateActCtx
- Microsoft: DeactivateActCtx
- Wine: activation-context implementation
Looking for a different code? Search another status or error code.