| Previous | Next |
| STATUS_APPEXEC_NO_DONOR |
STATUS_APPEXEC_HOST_ID_MISMATCH
The operation encountered an unexpected host identity
The public status text reports a host-ID mismatch but does not publish the identifier format or the complete set of objects bound to it. Diagnosis requires both values: the host ID expected by the request and the one actually encountered. Logging only the final status loses the evidence needed to find stale routing or mixed request state.
Hosted-app manifests also use HostRuntime and HostId values, so those declarations are relevant context when the failure occurs during packaged-app activation. However, an internal AppExec host ID should not be assumed to be identical to a manifest field unless the returning component documents that relationship.
What to inspect
- Record expected and observed host IDs, the returning component, request ID, user, package, and process ID.
- Check caches, routing tables, and asynchronous callbacks for state retained from an earlier request or host instance.
- Compare package manifest host declarations when the failure belongs to a hosted-app activation path.
- Recreate the operation from one current host context rather than replacing only the ID field.
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.