| Previous | Next |
| SDIAG_E_POWERSHELL | SDIAG_E_NOVERIFIER |
SDIAG_E_MANAGEDHOST
SDIAG_E_MANAGEDHOST means that the managed host that coordinates scripted diagnostics failed outside the pack’s direct root-cause logic.
What the status narrows down
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.
Script exceptions and managed-host failure are separate layers; preserve the host crash/initialization evidence.
Evidence worth preserving
- Managed-host event/error, process lifetime, CLR/runtime state, and WTP phase
- Pack identity/signature and whether other packs fail in the same host
- Crash dump, .NET runtime events, and loaded extensions
- Resource pressure, policy restrictions, and service dependencies
A controlled diagnostic sequence
- Run a built-in pack to test the shared managed host.
- Launch the original pack after a clean host restart while preserving logs.
- Reproduce in a clean user profile or machine image.
How to read the outcome
Read the comparison results in this order for Scripted Diagnostic Managed Host:
Correction and proof
A defensible correction is specific to the evidence: Repair the shared diagnostic host/runtime or isolate the extension that destabilizes it before changing pack logic.
Close the incident only when multiple packs execute sequentially and concurrently without host recycle, crash, or lost result reports.
Technical references
The following documentation is most relevant when checking the code against the actual Windows contract for Scripted Diagnostic Managed Host:
Looking for a different code? Search another status or error code.