| Previous | Next |
| UTC_E_INTENTIONAL_SCRIPT_FAILURE | UTC_E_NO_WER_LOGGER_SUPPORTED |
UTC_E_SQM_INIT_FAILED
Map the code to the scenario graph: SQM logger setup
UTC_E_SQM_INIT_FAILED has the unsigned value 0x87C51014. In UTC it comes from diagnostic logger initialization, where SQM logger setup owns the decision. A reliable investigation preserves the producing action before any cleanup runs. The immediate contract failed because the SQM logging backend named by UTC could not be initialized for this process or scenario, so diagnosis should remain at that boundary until a controlled comparison crosses it.
UTC can initialize more than one diagnostic/reporting backend. A logger failure is distinct from ETW provider failure and should be diagnosed from the logger-specific policy, service and storage prerequisites while preserving the nested HRESULT.
Data needed for triage
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | SQM logger setup |
| Producing layer | diagnostic logger initialization |
| Do not confuse with | UTC_E_NO_WER_LOGGER_SUPPORTED concerns WER capability rather than SQM initialization |
| Evidence to collect | service state, initialization HRESULT chain, policy, storage path, account context and first operational-log event |
| Narrow comparison | initialize a minimal UTC scenario with tracing disabled to isolate logger startup from ETW startup |
Reproduce without collateral changes
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: service state, initialization HRESULT chain, policy, storage path, account context and first operational-log event.
- Use a passing control on the same Windows build, then initialize a minimal UTC scenario with tracing disabled to isolate logger startup from ETW startup.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_NO_WER_LOGGER_SUPPORTED — concerns WER capability rather than SQM initialization.
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.
Fix the contract
Repair the logger prerequisite or policy and retain the underlying HRESULT; do not clear unrelated ETL sessions.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for diagnostic logger initialization while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for diagnostic logger initialization while interpreting it.
- Microsoft: About Windows Error Reporting
- Microsoft: Event Tracing for Windows
Looking for a different code? Search another status or error code.