| 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 for this HRESULT. 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 for this HRESULT.
UTC can initialize more than one diagnostic/reporting backend for this HRESULT. 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 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.
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 |
| Decisive evidence | 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 |
The AllStat message names the immediate condition as “Failed to initialize SQM logger” 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.
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 for this HRESULT.
- 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 for this HRESULT.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state for this HRESULT.
The most informative neighbor is UTC_E_NO_WER_LOGGER_SUPPORTED. The distinction is concrete: UTC_E_NO_WER_LOGGER_SUPPORTED concerns WER capability rather than SQM initialization 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.
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 failed generation for this HRESULT.
Fix the contract
Repair the logger prerequisite or policy and retain the underlying HRESULT; do not clear unrelated ETL sessions 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.
Deleting the working directory, killing all ETW sessions or retrying in a tight loop can suppress this result temporarily while leaving the underlying lifecycle defect intact 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 SQM logger setup
- the nearby condition remains distinguishable: UTC_E_NO_WER_LOGGER_SUPPORTED concerns WER capability rather than SQM initialization
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.