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. 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.

Diagnostic record

Isolate one changing condition

1. Associate this result with one request, one scenario version and one service process ID.
2. Save API identifier/version, Windows build/SKU, capability query, destination and caller contract and the first lower-level HRESULT if one exists.
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.
4. Compare the produced artifacts and operational events, not only the top-level return value.

Nearby result: UTC_E_SIF_NOT_SUPPORTED — is a narrower missing platform capability.

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.

Operational response

Feature-detect and choose a supported operation; retries cannot add an absent API implementation.

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