Scripted diagnostics native host has stopped working [Fix]

Reading time icon 4 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Scripted diagnostics native host has stopped working

The Scripted diagnostics native host has stopped working error message is one that can pop up for some users when utilizing troubleshooting utilities in Windows.

In addition, the error message states, A problem caused this program to stop working correctly. Some users have also stated that the error message pops up more randomly in Windows 10 every few hours. These are resolutions users have fixed the Scripted diagnostics error with.

What to do if Scripted diagnostics native host is not working?

  1. Run a System File Checker Scan
  2. Run the Check Disk Utility
  3. Clean boot Windows
  4. Open the Reliability Monitor
  5. Roll Back Windows Updates

1. Run a System File Checker scan

A few users have said that they fixed the Scripted diagnostics error with the System File Checker. The SFC utility will scan for and fix corrupted system files. Follow the guidelines below to run an SFC scan in Windows 10.

  1. Open Cortana’s search box by pressing the Windows key + Q hotkey.
  2. Enter the keyword cmd in the search box.
  3. Right-click Command Prompt and select Run as administrator.
  4. First, enter DISM.exe /Online /Cleanup-image /Restorehealth in the Prompt; and press the Enter key.
  5. To initiate a system file scan, enter sfc /scannow and press Return.sfc scannow Scripted diagnostics native host has stopped working
  6. The scan will probably take at least 30 minutes. Thereafter, restart Windows if the scan results say that WRP repaired files.

2. Run the Check Disk Utility

  1. Users have also confirmed that running the Check Disk utility fixed the Scripted diagnostics error for them. To do so, open the Cortana app.
  2. Enter cmd in Cortana’s search box.
  3. Open an elevated Command Prompt by right-clicking it and selecting Run as administrator.
  4. Next, input CHKDSK /R in the Command Prompt and press Return.chkdsk Scripted diagnostics
  5. If prompted for a restart, restart Windows as requested.

3. Clean boot Windows

The Scripted diagnostics error can often be due to third-party programs or services that users don’t really utilize themselves. Remember that the error message states, A problem caused this program to stop working correctly.

Clean-booting Windows will remove superfluous programs and services that might be generating the error. So, that’s another potential resolution for it. Users can clean boot Windows 10 as follows.

  1. First, launch Run with the Windows key + R keyboard shortcut.
  2. Input msconfig in Run’s text box, and click the OK button.
  3. Select the Services tab shown directly below.system configuration Scripted diagnostics native host has stopped working
  4. Select the Hide all Microsoft services option, which will exclude those services.
  5. Then press the Disable all button.
  6. Next, select the General tab on the System Configuration window.system configuration selective startup Scripted diagnostics
  7. Click the Selective startup radio button.
  8. Select both the Load system services and Use original boot configuration checkboxes.
  9. Deselect the Load startup items option.
  10. Click the Apply and OK buttons.
  11. Then click Restart on the dialog box that opens.system configuration restart native host has stopped working

4. Open the Reliability Monitor

The Reliability Monitor is a Control Panel utility that can come in handy for fixing the Scripted diagnostics error. That utility documents program & system crashes.

That utility might show users what program or process generated the Scripted diagnostics error message. Users can open the Reliability Monitor as follows.

  1. Open Run with its hotkey.
  2. Enter perfmon /rel in the Open box and click OK to open the Reliability Monitor shown directly below.performance monitor Scripted diagnostics
  3. Then select the red cross for the Scripted diagnostics error. That will show users what program or process stopped working within the Source box.
  4. Click View technical details to get further info that will include a path for the program.problem details Scripted diagnostics
  5. Users can uninstall any third-party program that generated the error via the Programs and Features Control Panel applet.
  6. If the Source box references a system process, users might need to disable the service for it via the Services or Task Manager windows.

5. Roll Back Windows Updates

The Scripted diagnostics error can also arise after Windows updates. Some users have even said that uninstalling certain Windows updates fixed the error for them.

So, the System Restore utility, which will roll back cumulative updates after a selected restore point, might fix the Scripted diagnostics error. Follow the guidelines below to roll back Windows.

  1. First, open the Run accessory.
  2. Input rstrui in the Open text box and click OK to open System Restore.
  3. Click Next and select Show more restore points.system restore native host has stopped working
  4. Choose a restore point that will roll back recent updates. Some of the restore points might even be listed as Windows Update.
  5. Click Next and select the Finish option to confirm.

Those are a few of the confirmed resolutions for the Scripted diagnostics error. However, there isn’t necessarily a guaranteed resolution for the issue.

RELATED ARTICLES TO CHECK OUT:

More about the topics: windows 10 fix