| Previous | Next |
| STATUS_SXS_ACTIVATION_CONTEXT_DISABLED | STATUS_SXS_VERSION_CONFLICT |
STATUS_SXS_KEY_NOT_FOUND
The context exists but has no matching keyed entry
STATUS_SXS_KEY_NOT_FOUND means that a lookup inside an active side-by-side context did not find the requested keyed entry. The context may be healthy and the relevant section may exist; the requested name, GUID or other lookup key simply does not map to an entry in the active context.
It differs from STATUS_SXS_SECTION_NOT_FOUND, where the entire queried section is absent. This distinction matters for COM, window-class and DLL-redirection lookups because it separates a missing registration from selecting the wrong kind of section.
What to inspect
- Record the lookup key after normalizing only where the corresponding API documents normalization; manifest element and attribute names are case-sensitive.
- Inspect the matching
file, COM, interface or window-class declaration that should contribute the entry. - Query the active context and its source assembly to determine whether another context was active on the calling thread.
References
Looking for a different code? Search another status or error code.