What does HRESULT 0x87C51037 (UTC_E_UNABLE_TO_RESOLVE_SESSION) mean?

 
Previous Next
UTC_E_FAILED_TO_RESOLVE_CONTAINER_ID UTC_E_THROTTLED

UTC_E_UNABLE_TO_RESOLVE_SESSION

Map the code to the scenario graph: Windows session resolution

The code UTC_E_UNABLE_TO_RESOLVE_SESSION (0x87C51037) belongs to platform capability and identity resolution, inside the Universal Telemetry Client/DiagTrack workflow. A reliable investigation preserves the producing action before any cleanup runs. It identifies Windows session resolution and reports that the API invocation could not determine the interactive or service session in which the action should run; it does not by itself prove that all Windows diagnostic data collection is unavailable.

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.

Data needed for triage

UTC diagnostic fieldValue
Producing layerplatform capability and identity resolution
Owning state or objectWindows session resolution
Evidence to collectcaller token, process/session IDs, active sessions, target user, logon/logoff timing and request ID
Narrow comparisonspecify or resolve a known active session and compare with the ambiguous invocation
Do not confuse withUTC_E_FAILED_TO_RESOLVE_CONTAINER_ID concerns application/container scope

Reproduce without collateral changes

  1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
  2. Capture caller token, process/session IDs, active sessions, target user, logon/logoff timing and request ID. Do this before restarting the service or deleting any working directory.
  3. Perform this one-variable comparison: specify or resolve a known active session and compare with the ambiguous invocation.
  4. After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created.

Nearby result: UTC_E_FAILED_TO_RESOLVE_CONTAINER_ID — concerns application/container scope.

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.

Fix the contract

Perform the operation in the intended session and handle session changes explicitly.

Technical references


Looking for a different code? Search another status or error code.