| Previous | Next |
| STATUS_APPEXEC_UNEXPECTED_PROCESS_REGISTRATION | STATUS_APPEXEC_NO_DONOR |
STATUS_APPEXEC_INVALID_HOST_STATE
The host exists but cannot perform this request now
The documented status distinguishes an invalid host state from a missing host or an invalid request handle. The target host was found, but its current state does not support the requested execution operation. Microsoft does not publicly enumerate the internal AppExec state machine, so diagnostics should not assign a specific phase based on this code alone.
Capture the operation and the state reported by the component that owns the host. Concurrent activation, cancellation, shutdown, or replacement may be relevant, but the component's event sequence must establish the cause. A blind retry can repeat the same state conflict or act on a newer host incorrectly.
What to inspect
- Log the requested operation, host ID, generation or version token, request ID, and reported state.
- Find concurrent activation, cancellation, teardown, or replacement events around the failure.
- Verify that delayed callbacks still refer to the current host before applying their results.
- Follow the owning API's recovery path or create a fresh request instead of forcing a transition.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
- Microsoft: create hosted apps
- Microsoft: uap10 HostRuntime extension
Looking for a different code? Search another status or error code.