| Previous | Next |
| UTC_E_FORWARDER_PRODUCER_MISMATCH | UTC_E_SQM_INIT_FAILED |
UTC_E_INTENTIONAL_SCRIPT_FAILURE
Separate cause from final symptom: script-defined termination signal
The code UTC_E_INTENTIONAL_SCRIPT_FAILURE (0x87C51013) belongs to scenario action execution, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. The first diagnostic step is to separate configuration, policy and runtime state for this HRESULT. It identifies script-defined termination signal and reports that the approved script deliberately returned the failure used to stop the current escalation path; it does not by itself prove that all Windows diagnostic data collection is unavailable for this HRESULT.
Scenario actions run under service-controlled identity, timeout and cancellation rules for this HRESULT. The useful evidence is the exact action instance and its child process or script state, not a later generic service event for this HRESULT. stdout, stderr and native exit values should be retained separately from the UTC HRESULT for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.
High-value observations
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario action execution |
| Owning state or object | script-defined termination signal |
| Decisive evidence | script hash/version, documented sentinel exit code, action branch, stdout/stderr and subsequent action suppression |
| Narrow comparison | run the script with inputs that select its success branch and then its intentional-stop branch |
| Do not confuse with | UTC_E_CHILD_PROCESS_FAILED covers an ordinary nonzero child exit that was not an intentional UTC sentinel |
The AllStat message names the immediate condition as “RunScriptAction failed intentionally to force this escalation to terminate” 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.
A focused experiment
- Export the relevant
Microsoft-Windows-UniversalTelemetryClient/Operationalevents and preserve their ActivityId or request correlation alongside this result. - Capture script hash/version, documented sentinel exit code, action branch, stdout/stderr and subsequent action suppression for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
- Perform this one-variable comparison: run the script with inputs that select its success branch and then its intentional-stop branch 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_CHILD_PROCESS_FAILED. The distinction is concrete: UTC_E_CHILD_PROCESS_FAILED covers an ordinary nonzero child exit that was not an intentional UTC sentinel 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.
Recovery criteria
Handle the sentinel as scenario control flow and do not relabel it as a script-engine crash 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.
Do not treat this result as permission to bypass collection policy, script approval, path restrictions or trace arbitration for this HRESULT. A repair that only weakens those controls is not a valid regression result 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 script-defined termination signal
- the nearby condition remains distinguishable: UTC_E_CHILD_PROCESS_FAILED covers an ordinary nonzero child exit that was not an intentional UTC sentinel
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 this result.
- Microsoft: UniversalTelemetryClient operational-log guidance — reference for scenario action execution while interpreting it.
- Microsoft: About Windows Error Reporting
Looking for a different code? Search another status or error code.