What does HRESULT 0x87C5102B (UTC_E_API_BUSY) mean?

UTC_E_API_BUSY

Where the UTC workflow stopped: serialized UTC API manager slot

The code UTC_E_API_BUSY (0x87C5102B) belongs to Universal Telemetry Client API coordination, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. The decisive question is which UTC object rejected the request for this HRESULT. It identifies serialized UTC API manager slot and reports that another request currently owns a resource that the API exposes as single-operation-at-a-time; it does not by itself prove that all Windows diagnostic data collection is unavailable for this HRESULT.

UTC API requests may cross an RPC boundary and complete asynchronously even when exposed through a synchronous wrapper for this HRESULT. Request submission, waiting, cancellation and result retrieval are separate stages, so one request ID should tie the evidence together for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.

Evidence to preserve

The AllStat message names the immediate condition as “The UTC API is busy with another request” 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.

Controlled reproduction

1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
2. Capture active and rejected request IDs, operation types, start times, completion callback and caller threads for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
3. Perform this one-variable comparison: wait for the first request to finish and submit the second exactly once for this HRESULT.
4. After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created for this HRESULT.

The most informative neighbor is UTC_E_ESCALATION_ALREADY_RUNNING. The distinction is concrete: UTC_E_ESCALATION_ALREADY_RUNNING is scenario-level concurrency, not general API-manager occupancy 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.

Request-lifetime note

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

Correction and verification

Serialize calls at the client boundary or use an asynchronous queue with cancellation 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.

Do not treat this result as permission to bypass collection policy, script approval, path restrictions or trace arbitration for this HRESULT. A repair that only weakens those controls is not a valid regression result 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 serialized UTC API manager slot
• the nearby condition remains distinguishable: UTC_E_ESCALATION_ALREADY_RUNNING is scenario-level concurrency, not general API-manager occupancy

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

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