| Previous | Next |
| SDIAG_E_CANCELLED | SDIAG_E_POWERSHELL |
SDIAG_E_SCRIPT
SDIAG_E_SCRIPT means that a detection, resolution, or verification PowerShell script failed while WTP was executing the pack.
The contract behind the HRESULT
A troubleshooting pack has distinct initialization, detection, resolution, and verification phases. Keep the ordinary result report together with the debug report, and identify whether the pack script, PowerShell host, managed host, resource loader, trust check, or verifier produced the first failure.
SDIAG_E_POWERSHELL points to the PowerShell runtime interaction; SDIAG_E_SCRIPT points to the pack script’s execution path.
Diagnostic worksheet
- Pack ID/version/publisher, script name, phase, exception, line, and invocation parameters
- WTP debug report and hosted PowerShell output
- Execution identity/elevation, working directory, culture, and resource paths
- State changes completed before the exception
Reproduce the condition safely
- Run the script logic with the same inputs in an isolated signed test pack.
- Add terminating error handling around the smallest failing command.
- Compare interactive and unattended execution with identical answer data.
Nearby states and false leads
Read the comparison results in this order for troubleshooting-pack script failure:
Closing the incident
A defensible correction is specific to the evidence: Correct the script, make resolver actions idempotent, validate inputs/resources, and sign/rebuild the pack after changes.
Close the incident only when detect, resolve, and verify phases complete for positive and negative cases, and injected command failures produce a controlled report.
Technical references
Looking for a different code? Search another status or error code.