What does HRESULT 0x87C5103C (UTC_E_API_NOT_SUPPORTED) mean?

UTC_E_API_NOT_SUPPORTED

Read this as a lifecycle result: UTC API capability dispatch

UTC_E_API_NOT_SUPPORTED has the unsigned value 0x87C5103C. In UTC it comes from platform capability and identity resolution, where UTC API capability dispatch owns the decision. Treat this HRESULT as a state-machine report, not as a generic telemetry outage for this HRESULT. The immediate contract failed because the requested API operation is not implemented or enabled on this device/build/destination, so diagnosis should remain at that boundary until a controlled comparison crosses it for this HRESULT.

Diagnostic record

The AllStat message names the immediate condition as “The requested UTC API call is not supported on this device” for this HRESULT. In practice, the useful extension is to ask whether the request was rejected before any side effect, after partial setup, or during cleanup for this HRESULT. Verify the existence and ownership of the expected output—session, directory, process, result object or emitted event—rather than assuming the message describes the final system state for this HRESULT.

Isolate one changing condition

1. Associate this result with one request, one scenario version and one service process ID for this HRESULT.
2. Save API identifier/version, Windows build/SKU, capability query, destination and caller contract and the first lower-level HRESULT if one exists for this HRESULT.
3. Change no policy, provider set or destination except for this test: invoke a baseline supported API through the same client and compare returned capabilities for this HRESULT.
4. Compare the produced artifacts and operational events, not only the top-level return Value.

The most informative neighbor is UTC_E_SIF_NOT_SUPPORTED. The distinction is concrete: UTC_E_SIF_NOT_SUPPORTED is a narrower missing platform capability for this HRESULT. Keeping both symbolic names in logs prevents a broad “DiagTrack error” bucket from hiding whether the failure occurred during parsing, authorization, resource acquisition, execution or teardown for this HRESULT.

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 failed generation for this HRESULT.

Operational response

Feature-detect and choose a supported operation; retries cannot add an absent API implementation for this HRESULT. Apply that change only to the owning boundary for this HRESULT. A successful repair must make the controlled case cross this boundary while retaining the intended policy, trace providers, destination and security context for this HRESULT.

Deleting the working directory, killing all ETW sessions or retrying in a tight loop can suppress this result temporarily while leaving the underlying lifecycle defect intact for this HRESULT.

• the same request now produces its documented success or nonfatal status without a second hidden retry
• the operational log shows one coherent request lifetime and no orphaned action, timer, process or trace session
• teardown followed by a second run does not reuse stale state or recreate UTC API capability dispatch
• the nearby condition remains distinguishable: UTC_E_SIF_NOT_SUPPORTED is a narrower missing platform capability

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 it.
• Microsoft: UniversalTelemetryClient operational-log guidance
• Microsoft: RoInitialize

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