| 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. The symbolic name points to a narrow UTC contract that can be tested directly. The relevant state is Windows Error Reporting logger capability: the current system/configuration does not expose the WER logging mode UTC requested. This identifies a specific UTC/DiagTrack condition, not a general service failure.
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.
Capture checklist
| UTC diagnostic field | Value |
|---|---|
| Producing layer | diagnostic logger initialization |
| Owning state or object | Windows Error Reporting logger capability |
| Evidence to collect | 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 |
Comparison with a passing case
- Associate this result with one request, one scenario version and one service process ID.
- Save Windows edition/build, WER service and policy state, UTC feature flags and initialization trace and the first lower-level HRESULT if one exists.
- 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.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_SQM_INIT_FAILED — means another diagnostic logger failed to initialize.
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.
Resolution and regression test
Choose a supported logging destination or correct WER policy; avoid forcing unsupported private interfaces.
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.