none
A problem is preventing the troubleshooter from starting?

    Question

  • Hey guys, I have been constantly getting this message whenever I use my troubleshooter...

    "An error occurred while troubleshooting
    A problem is preventing the troubleshooter from starting"

    Path:C:\Windows\diagnostics\system\networking
    Error code:0x80070426
    Source:engine
    Context:restricted

    The strange thing is that when I run SFC /SCANNOW it fixes it.....TEMPORARILY
    and gives me the same error whenever I restart or reboot my system.
    Is there a permanent fix for this?
    Sunday, February 26, 2012 9:41 PM

Answers

  • Hi,

    Does this issue occur with all troubleshooters or just networking troubleshooter? Have you tried to launch troubleshooters from different location? You can launch troubleshooters either from Control Panel, Action Center or Related Topic in Help. How about unchecking "Get the most up-to-date troubleshooters from the Windows Online Troubleshooting Service" and only use the local troubleshooter file? Moreover, based on my further research, please make sure there isn't any Group Policy setting blocking the launch of troubleshooters.

    First, I recommend you to check the following location in Local Group Policy Editor.


    Computer Configuration\Administrative Templates\System\Troubleshooting and
    Diagnostics\Scripted Diagnostics


    Second, Check these settings and make sure it isn't disabled:

    Troubleshooting: Allow users to access and run Troubleshooting Wizards

    Troubleshooting: Allow users to access online troubleshooting content on
    Microsoft servers from the Troubleshooting Control Panel (via the Windows
    Online Troubleshooting Service - WOTS)


    Third, you may also check the related registries (both keys are 0x00000001
    by default):
    HKLM\SOFTWARE\Policies\Microsoft\Windows\ScriptedDiagnostics!EnableDiagnostics
    HKLM\SOFTWARE\Policies\Microsoft\Windows\ScriptedDiagnosticsProvider\Policy!EnableQueryRemoteServer

    Fourth, please verity the Startup type of Diagnostic Policy Service is
    Automatic, the Startup type of Diagnostic Service Host and Diagnostic System
    Host is Manual.

    Ifthe issue persists, I recommend you to test the issue in Clean Boot Mode.

    For references:
    Built-in Troubleshooting Packs

    Hopethis helps.



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.



    Monday, February 27, 2012 10:00 AM
    Moderator