| 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. This result becomes useful only after it is tied to one request generation for this HRESULT. 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 for this HRESULT.
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 |
| Decisive evidence | 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 |
The AllStat message names the immediate condition as “A RunExeWithArgs action contains a binary which is not present on the targeted device” 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.
Prove the boundary
- 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 for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
- Perform this one-variable comparison: replace the reference with a known present signed test executable under the same policy for this HRESULT.
- After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created for this HRESULT.
The most informative neighbor is UTC_E_COMMAND_LINE_NOT_AUTHORIZED. The distinction is concrete: UTC_E_COMMAND_LINE_NOT_AUTHORIZED means the binary exists but the requested invocation is denied 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.
Child-action accounting
Keep process creation, job assignment, timeout, cancellation, exit code and output capture as separate timestamps for this HRESULT. That sequence reveals whether the child failed itself, was terminated by UTC or never started for this HRESULT.
Confirm the repair
Deploy the correct binary version or gate the scenario by device capability 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.
Deleting the working directory, killing all ETW sessions or retrying in a tight loop can suppress this result temporarily while leaving the underlying lifecycle defect intact 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 RunExeWithArgs executable resolution
- the nearby condition remains distinguishable: UTC_E_COMMAND_LINE_NOT_AUTHORIZED means the binary exists but the requested invocation is denied
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.