| Previous | Next |
| UTC_E_SQM_INIT_FAILED | UTC_E_TRACERS_DONT_EXIST |
UTC_E_NO_WER_LOGGER_SUPPORTED
Locate the rejected contract: Windows Error Reporting logger capability
UTC_E_NO_WER_LOGGER_SUPPORTED (0x87C51015) is a Universal Telemetry Client result from the diagnostic logger initialization layer for this HRESULT. The symbolic name points to a narrow UTC contract that can be tested directly for this HRESULT. Here the relevant owner is Windows Error Reporting logger capability: the current system/configuration does not expose the WER logging mode UTC requested for this HRESULT. This is narrower than a generic failure of Connected User Experiences and Telemetry 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.
Capture checklist
| UTC diagnostic field | Value |
|---|---|
| Producing layer | diagnostic logger initialization |
| Owning state or object | Windows Error Reporting logger capability |
| Decisive evidence | Windows edition/build, WER service and policy state, UTC feature flags and initialization trace |
| Narrow comparison | enable a supported WER configuration in a controlled image and repeat the same UTC setup |
| Do not confuse with | UTC_E_SQM_INIT_FAILED means another diagnostic logger failed to initialize |
The AllStat message names the immediate condition as “Failed to initialize WER logger: This system does not support WER for UTC” 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.
Comparison with a passing case
- Associate this result with one request, one scenario version and one service process ID for this HRESULT.
- Save Windows edition/build, WER service and policy state, UTC feature flags and initialization trace and the first lower-level HRESULT if one exists for this HRESULT.
- Change no policy, provider set or destination except for this test: enable a supported WER configuration in a controlled image and repeat the same UTC setup for this HRESULT.
- Compare the produced artifacts and operational events, not only the top-level return Value.
The most informative neighbor is UTC_E_SQM_INIT_FAILED. The distinction is concrete: UTC_E_SQM_INIT_FAILED means another diagnostic logger failed to initialize 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.
Resolution and regression test
Choose a supported logging destination or correct WER policy; avoid forcing unsupported private interfaces 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.
Restarting Windows, clearing every ETL file or disabling diagnostic policy is not a justified first response to this result. Those actions destroy evidence and can change several independent UTC gates at once 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 Windows Error Reporting logger capability
- the nearby condition remains distinguishable: UTC_E_SQM_INIT_FAILED means another diagnostic logger failed to initialize
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.