Scripted Diagnostics Native Host (sdiagnhost.exe): What It Is and How to Stop It Safely

Scripted Diagnostics Native Host is the Windows process sdiagnhost.exe. It shows up in Task Manager while a Windows troubleshooter runs, because it hosts the scripts that do the troubleshooter’s checks and fixes. It’s normal, it stops when the troubleshooter is done, and you can end it safely if it gets stuck.

This guide covers Windows 10 and Windows 11: what the process does, how to confirm it’s the real Windows file, how to stop it, and how to fix the “Scripted Diagnostics Native Host has stopped working” error.

What Scripted Diagnostics Native Host does

Classic Windows troubleshooters (audio, network, printer, Windows Update and others) are built on the Windows Troubleshooting Platform (WTP). Microsoft’s documentation describes how they work:

• Each troubleshooting pack is a set of Windows PowerShell scripts plus a manifest. Detection scripts look for known causes, resolver scripts try to fix them, and verifier scripts check that the fix worked.
• WTP runs those scripts in a hosted PowerShell runtime that lives in a separate process. Microsoft says this is “for reliability to ensure that WTP does not experience any side effects caused by poorly written scripts.”
• WTP only runs troubleshooting packs that are signed by a trusted certificate.

On Windows, that separate host process is sdiagnhost.exe. Windows’ own crash reports name it “Scripted Diagnostics Native Host” with the path C:\Windows\System32\sdiagnhost.exe when a troubleshooter fails.

A user doesn’t always start it. Microsoft notes that an application can also start a troubleshooter when it can’t finish a task, for example when it can’t reach a network share.

Why you see it in Task Manager

What you see	What it means	What to do
sdiagnhost.exe while a troubleshooter window is open	The troubleshooter’s scripts are running	Nothing; let it finish
High CPU for a short time during a troubleshooter	Detection or repair scripts are working	Wait, or close the troubleshooter
sdiagnhost.exe still running after you closed every troubleshooter	The process didn’t exit cleanly	End it (see below)
“Scripted Diagnostics Native Host has stopped working”	A troubleshooter script or a file it needs crashed	Repair Windows (see below)
sdiagnhost.exe running from a folder other than System32	Not the Windows copy	Scan for malware

Troubleshooters are moving to Get Help

Microsoft is retiring the legacy inbox troubleshooters and the Microsoft Support Diagnostic Tool (MSDT) that runs them. On Windows 11 releases after 22H2, some troubleshooters are redirected to the Get Help app and the rest are removed. Microsoft says Windows 11 22H2 and earlier, Windows 10 and older versions aren’t affected and keep the legacy troubleshooters.

So on a current Windows 11 PC you may see sdiagnhost.exe less often, while Windows 10 PCs still use it for every classic troubleshooter.

How to check sdiagnhost.exe is genuine

Run these in PowerShell while the process is running. Use Run as administrator if it doesn’t show the path.

Get-Process -Name sdiagnhost -FileVersionInfo

This shows the version and the full file name of the running process. It should be C:\Windows\System32\sdiagnhost.exe.

Get-AuthenticodeSignature C:\Windows\System32\sdiagnhost.exe

This checks the file’s digital signature. A Status of Valid with a Microsoft certificate is what you want.

Tip: In Task Manager, the Details tab lists every process. Right-click a column header and choose Select columns to add more information about each process.

If the file runs from somewhere else or the signature isn’t valid, open Windows Security > Virus & threat protection, run a full scan, then run Scan options > Microsoft Defender Antivirus (offline scan).

How to stop Scripted Diagnostics Native Host safely

Stopping it ends the troubleshooter that’s using it. That’s fine; you can run the troubleshooter again later.

1. Close the troubleshooter first. Select Close or Cancel in the troubleshooter or Get Help window then check Task Manager again. If sdiagnhost.exe is gone, you’re done.
2. End it in Task Manager. Press Ctrl + Shift + Esc, open Details, select sdiagnhost.exe and choose End task.
3. Or use PowerShell:

Stop-Process -Name sdiagnhost

Important: Don’t delete, rename or block sdiagnhost.exe. It’s a Windows system file, and troubleshooters stop working without it. It isn’t a service, so there is no startup setting to disable.

If the PC is slow even when no troubleshooter is running, sdiagnhost.exe isn’t the cause. Our guide to why your computer is so slow shows how to find the real bottleneck.

How to fix “Scripted Diagnostics Native Host has stopped working”

When a troubleshooter crashes with this message, the problem is usually a damaged Windows file or something interfering with the scripts. Work through these in order.

Fix 1: Install Windows updates and restart

Go to Settings > Windows Update (Windows 11) or Settings > Update & Security > Windows Update (Windows 10), select Check for updates, install everything and restart.

Fix 2: Repair system files with DISM and sfc

Important: Run these in an elevated Command Prompt. Our elevated command prompt guide shows how to open one.

DISM.exe /Online /Cleanup-image /Restorehealth

This repairs the Windows component store. Then run:

sfc /scannow

System File Checker replaces corrupted protected files. Restart and run the troubleshooter again.

Fix 3: Try a clean boot

Third-party services and startup apps can interfere. Open System Configuration (msconfig), hide all Microsoft services and disable the rest, disable startup apps in Task Manager, then restart and try the troubleshooter. Our guide to Rundll32 has stopped working walks through the full clean boot steps and how to undo them.

Fix 4: Use Get Help or the manual steps instead

You don’t need a crashing troubleshooter to fix the original problem. On Windows 11, go to Settings > System > Troubleshoot > Other troubleshooters, or open the Get Help app and search for the troubleshooter by name. You can also follow the manual steps in guides such as sound not working on Windows 11 or Wi-Fi not working on a laptop.

Is it a security risk?

The Windows file itself isn’t. In 2022 attackers abused the MSDT URL protocol (CVE-2022-30190) to run code through crafted documents. Microsoft fixed it in the Windows updates released on June 14, 2022. Keeping Windows updated is the protection; disabling troubleshooters isn’t necessary on a patched PC.

If it still doesn’t work

• Read the crash event. In Event Viewer > Windows Logs > Application, look for Application Error event 1000 with sdiagnhost.exe as the faulting application. The faulting module name points to the file that failed.
• Check the CBS log if sfc couldn’t repair everything. Microsoft’s sfc article shows how to extract its entries to a text file.
• Work PCs: troubleshooters can be restricted by Group Policy, so ask IT before changing anything.
• Still stuck? Back up your files and contact Microsoft Support or a repair shop. More fixes are in PC repairs.