What does HRESULT 0x87C51028 (UTC_E_API_RESULT_UNAVAILABLE) mean?

UTC_E_API_RESULT_UNAVAILABLE

Separate cause from final symptom: asynchronous UTC API result slot

UTC_E_API_RESULT_UNAVAILABLE has the unsigned value 0x87C51028. In UTC it comes from Universal Telemetry Client API coordination, where asynchronous UTC API result slot owns the decision. The first diagnostic step is to separate configuration, policy and runtime state. The immediate contract failed because the API operation did not complete successfully, so no valid result object is available to retrieve, so diagnosis should remain at that boundary until a controlled comparison crosses it.

UTC API requests may cross an RPC boundary and complete asynchronously even when exposed through a synchronous wrapper. Request submission, waiting, cancellation and result retrieval are separate stages, so one request ID should tie the evidence together.

High-value observations

A focused experiment

1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
2. Capture request ID, initial submission result, completion state, cancellation/timeout, callback and underlying failure. Do this before restarting the service or deleting any working directory.
3. Perform this one-variable comparison: complete a known supported request and retrieve its result only after its completion event.
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_RPC_TIMEOUT — identifies one possible transport/manager failure that prevented completion.

Request-lifetime note

Assign a correlation identifier before submission and retain it through wait, callback, cancellation and result retrieval. This prevents a late completion from being mistaken for the response to a newer request.

Recovery criteria

Fix the primary operation and gate result access on success; never parse an uninitialized output buffer.

Technical references

• Microsoft Open Specifications: Windows error-code registry — reference for Universal Telemetry Client API coordination while interpreting this result.
• Microsoft: Universal Telemetry Client configuration diagnosis — reference for Universal Telemetry Client API coordination while interpreting this result.
• Microsoft: Remote Procedure Call documentation — reference for Universal Telemetry Client API coordination while interpreting it.
• Microsoft: WaitForSingleObject