| Previous | Next |
| UTC_E_NETWORK_CAPTURE_NOT_ALLOWED | UTC_E_UNABLE_TO_RESOLVE_SESSION |
UTC_E_FAILED_TO_RESOLVE_CONTAINER_ID
Separate cause from final symptom: scenario container-context resolution
When UTC_E_FAILED_TO_RESOLVE_CONTAINER_ID (0x87C51036) is returned, the producing layer is platform capability and identity resolution. The first diagnostic step is to separate configuration, policy and runtime state. The rejected object or state is scenario container-context resolution, and the specific condition is that UTC could not map the requested escalation context to the container identifier needed for the action. Keep this first HRESULT even if a later service call reports another error.
Some UTC actions depend on platform capabilities, Windows Runtime setup, device identity, session/container resolution or destination support. Feature detection and stable identity evidence are more reliable than retries based only on the top-level HRESULT.
High-value observations
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | scenario container-context resolution |
| Producing layer | platform capability and identity resolution |
| Do not confuse with | UTC_E_UNABLE_TO_RESOLVE_SESSION concerns user/session identity rather than container identity |
| Evidence to collect | requested app/package/process, session, token, container metadata, lifecycle state and API request ID |
| Narrow comparison | repeat against a known running packaged/containerized target and then against the failing target |
A focused experiment
- Associate this result with one request, one scenario version and one service process ID.
- Save requested app/package/process, session, token, container metadata, lifecycle state and API request ID and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: repeat against a known running packaged/containerized target and then against the failing target.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_UNABLE_TO_RESOLVE_SESSION — concerns user/session identity rather than container identity.
Platform-state note
Capture capability and identity state at the moment this result is returned. Session, container, service and destination state can change asynchronously, so a later successful query does not describe the state at failure.
Recovery criteria
Resolve the target while it is alive and pass stable identity data; do not reuse an ID from another instance.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for platform capability and identity resolution while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for platform capability and identity resolution while interpreting this result.
- Microsoft: UniversalTelemetryClient operational-log guidance — reference for platform capability and identity resolution while interpreting it.
- Microsoft: RoInitialize
Looking for a different code? Search another status or error code.
