| Previous | Next |
| UTC_E_UNAPPROVED_SCRIPT | UTC_E_SCENARIO_THROTTLED |
UTC_E_SCRIPT_MISSING
Interpret the result in context: RunScriptAction file resolution
When UTC_E_SCRIPT_MISSING (0x87C5103A) is returned, the producing layer is scenario action execution for this HRESULT. Start by locating the exact scenario-engine boundary that emitted this Value. The rejected object or state is RunScriptAction file resolution, and the specific boundary is that the scenario references a script that is not present on the device at execution time for this HRESULT. Later service errors should not replace this first result in the incident record 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.
Build a minimal evidence set
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | RunScriptAction file resolution |
| Producing layer | scenario action execution |
| Do not confuse with | UTC_E_UNAPPROVED_SCRIPT means a present script failed policy approval |
| Decisive evidence | configured/expanded path, package revision, file deployment state, architecture and scenario version |
| Narrow comparison | place a minimal approved script at the exact resolved path and repeat the action |
The AllStat message names the immediate condition as “The script referenced in DiagTrack scenario is not present on the system” 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.
Run an A/B check
- Export the relevant
Microsoft-Windows-UniversalTelemetryClient/Operationalevents and preserve their ActivityId or request correlation alongside this result. - Capture configured/expanded path, package revision, file deployment state, architecture and scenario version for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
- Perform this one-variable comparison: place a minimal approved script at the exact resolved path and repeat the action 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_UNAPPROVED_SCRIPT. The distinction is concrete: UTC_E_UNAPPROVED_SCRIPT means a present script failed policy approval 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.
Safe remediation
Fix package deployment or capability gating while preserving approval/signature requirements 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.
Avoid broad registry resets or global service-policy changes until the single-owner comparison has been run for this HRESULT. They can hide the original configuration generation without proving the contract was corrected 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 RunScriptAction file resolution
- the nearby condition remains distinguishable: UTC_E_UNAPPROVED_SCRIPT means a present script failed policy approval
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for scenario action execution while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis
- Microsoft: UniversalTelemetryClient operational-log guidance
- Microsoft: About Windows Error Reporting
Looking for a different code? Search another status or error code.