| Previous | Next |
| STATUS_ACPI_POWER_REQUEST_FAILED | STATUS_SXS_CANT_GEN_ACTCTX |
STATUS_SXS_SECTION_NOT_FOUND
A requested activation-context section is absent
STATUS_SXS_SECTION_NOT_FOUND is raised after an activation context is available but a caller asks it for a section that it does not contain. Sections hold different kinds of side-by-side data, such as DLL redirection, COM or window-class information. This is therefore not proof that the whole manifest failed to load.
It differs from STATUS_SXS_KEY_NOT_FOUND: here the requested section itself is unavailable; with KEY_NOT_FOUND, a section can exist while the requested entry within it does not. The useful question is which query information class or section lookup the caller requested, not whether the executable can merely be started.
What to inspect
- Record the exact API and query information class, plus whether the context came from the EXE, a DLL or an explicit
ACTCTXhandle. - Inspect the manifest for the feature that should populate the requested section: a
file, COM registration, type library or versioned window-class declaration. - Query the created context separately before changing deployment files; a missing section and a missing dependency are different failures.
References
Looking for a different code? Search another status or error code.
