| Previous | Next |
| UTC_E_TRACERS_DONT_EXIST | UTC_E_SCENARIODEF_SCHEMAVERSION_MISMATCH |
UTC_E_WINRT_INIT_FAILED
Interpret the result in context: thread or process WinRT initialization
The code UTC_E_WINRT_INIT_FAILED (0x87C51017) belongs to platform capability and identity resolution, inside the Universal Telemetry Client/DiagTrack workflow. Start by locating the exact scenario-engine boundary that emitted this value. It identifies thread or process WinRT initialization and reports that the UTC component could not initialize the Windows Runtime apartment needed by the requested path; 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.
Build a minimal evidence set
| UTC diagnostic field | Value |
|---|---|
| Producing layer | platform capability and identity resolution |
| Owning state or object | thread or process WinRT initialization |
| Evidence to collect | thread ID, apartment model, prior COM/WinRT initialization calls, returned HRESULT and shutdown ordering |
| Narrow comparison | run the same API on a fresh thread with the required RoInitialize mode |
| Do not confuse with | UTC_E_API_NOT_SUPPORTED is a capability decision after API dispatch, not a WinRT startup failure |
Run an A/B check
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: thread ID, apartment model, prior COM/WinRT initialization calls, returned HRESULT and shutdown ordering.
- Use a passing control on the same Windows build, then run the same API on a fresh thread with the required RoInitialize mode.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_API_NOT_SUPPORTED — is a capability decision after API dispatch, not a WinRT startup failure.
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.
Safe remediation
Make apartment initialization and uninitialization balanced and preserve the first failure code.
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.