| Previous | Next |
| UTC_E_TRIGGER_NOT_FOUND | UTC_E_DELAY_TERMINATED |
UTC_E_SIF_NOT_SUPPORTED
Where the UTC workflow stopped: SIF capability check
UTC_E_SIF_NOT_SUPPORTED has the unsigned value 0x87C51024. In UTC it comes from platform capability and identity resolution, where SIF capability check owns the decision. The key question is which UTC object rejected the request. The immediate contract failed because the requested path requires the SIF capability named by UTC, but that capability is unavailable on this machine, so diagnosis should remain at that boundary until a controlled comparison crosses it.
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.
Evidence to preserve
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | SIF capability check |
| Producing layer | platform capability and identity resolution |
| Do not confuse with | UTC_E_ACTION_NOT_SUPPORTED_IN_DESTINATION rejects a particular destination even when the client supports the action elsewhere |
| Evidence to collect | Windows build/SKU, capability query, scenario requirement, destination and first unsupported-operation event |
| Narrow comparison | run the same scenario on a documented supported image without changing its filters |
Controlled reproduction
- Associate this result with one request, one scenario version and one service process ID.
- Save Windows build/SKU, capability query, scenario requirement, destination and first unsupported-operation event and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: run the same scenario on a documented supported image without changing its filters.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_ACTION_NOT_SUPPORTED_IN_DESTINATION — rejects a particular destination even when the client supports the action elsewhere.
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.
Correction and verification
Select a destination/action supported by the target or gate the scenario by capability.
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.