| Previous | Next |
| UTC_E_INVALID_AGGREGATION_STRUCT | UTC_E_FILTER_MISSING_ATTRIBUTE |
UTC_E_ACTION_NOT_SUPPORTED_IN_DESTINATION
Separate cause from final symptom: action-to-destination capability matrix
UTC_E_ACTION_NOT_SUPPORTED_IN_DESTINATION has the unsigned value 0x87C51044. In UTC it comes from platform capability and identity resolution, where action-to-destination capability matrix owns the decision. The first diagnostic step is to separate configuration, policy and runtime state. The immediate contract failed because the action is recognized by UTC but cannot run for the selected destination, ring or collection target, 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.
High-value observations
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | action-to-destination capability matrix |
| Producing layer | platform capability and identity resolution |
| Do not confuse with | UTC_E_API_NOT_SUPPORTED means the API operation itself is unavailable on the device |
| Evidence to collect | action type, destination identifier, client build, policy/capability result and scenario configuration |
| Narrow comparison | run the same action against a supported local destination while holding inputs constant |
A focused experiment
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: action type, destination identifier, client build, policy/capability result and scenario configuration.
- Use a passing control on the same Windows build, then run the same action against a supported local destination while holding inputs constant.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_API_NOT_SUPPORTED — means the API operation itself is unavailable on the device.
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.
Recovery criteria
Select a compatible destination or replace the action; repeated retries do not change the matrix.
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.