| Previous | Next |
| STATUS_PLATFORM_MANIFEST_NOT_SIGNED | STATUS_APPEXEC_HANDLE_INVALIDATED |
STATUS_APPEXEC_CONDITION_NOT_SATISFIED
The request failed its own precondition
The public NTSTATUS definition establishes that a condition supplied with the app-execution request evaluated as unsatisfied and that Windows did not perform the request. It does not identify the condition, the component that evaluated it, or the exact activation path. This should therefore be diagnosed as a rejected precondition, not automatically as a process crash or executable-loading failure.
When the caller is working with a packaged or hosted app, useful context can include package family, application ID, user and session, activation kind, and manifest host information. Those fields help correlate events, but they are not all guaranteed parts of the internal AppExec contract.
What to inspect
- Record the component and API that returned the status, the request ID, and any condition data exposed by that component.
- Capture package family, application ID, user, session, activation kind, and host identifier when available.
- Find the earliest broker, deployment, policy, or activation event that explains why the condition evaluated false.
- Retry only after the relevant state or condition has changed; an identical request should not be expected to succeed.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
- Microsoft: create hosted apps
- Microsoft: Windows application activation APIs
Looking for a different code? Search another status or error code.