| Previous | Next |
| UTC_E_MULTIPLE_TIME_TRIGGER_ON_SINGLE_STATE | UTC_E_NETWORK_CAPTURE_NOT_ALLOWED |
UTC_E_BINARY_MISSING
Identify the owning component: RunExeWithArgs executable resolution
UTC_E_BINARY_MISSING has the unsigned value 0x87C51034. In UTC it comes from scenario action execution, where RunExeWithArgs executable resolution owns the decision. Correlate this HRESULT with the exact request attempt that returned it. The immediate contract failed because the authorized binary reference does not resolve to an existing executable on the target device, so diagnosis should remain at that boundary until a controlled comparison crosses it.
What to capture before retrying
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | RunExeWithArgs executable resolution |
| Producing layer | scenario action execution |
| Do not confuse with | UTC_E_COMMAND_LINE_NOT_AUTHORIZED means the binary exists but the requested invocation is denied |
| Evidence to collect | configured and expanded path, architecture, package/version, file existence, signer/hash and deployment logs |
| Narrow comparison | replace the reference with a known present signed test executable under the same policy |
Prove the condition
- Export the relevant
Microsoft-Windows-UniversalTelemetryClient/Operationalevents and preserve their ActivityId or request correlation alongside this result. - Capture configured and expanded path, architecture, package/version, file existence, signer/hash and deployment logs. Do this before restarting the service or deleting any working directory.
- Perform this one-variable comparison: replace the reference with a known present signed test executable under the same policy.
- After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created.
Nearby result: UTC_E_COMMAND_LINE_NOT_AUTHORIZED — means the binary exists but the requested invocation is denied.
Child-action accounting
Keep process creation, job assignment, timeout, cancellation, exit code and output capture as separate timestamps. That sequence reveals whether the child failed itself, was terminated by UTC or never started.
Confirm the repair
Deploy the correct binary version or gate the scenario by device capability.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for scenario action execution while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for scenario action execution while interpreting it.
- Microsoft: UniversalTelemetryClient operational-log guidance
- Microsoft: About Windows Error Reporting
Looking for a different code? Search another status or error code.