How to run Troubleshooter in Windows 10 from the command line

You can run a built-in Troubleshooter in Windows 10/8/7 from the command line. Microsoft Support Diagnostic Tool or MSDT.exe can be used to invoke and launch any Windows Troubleshooting Pack or Troubleshooter from the command line.

How to run Troubleshooter in Windows 10

In this post, we will see how to run Hardware, Audio or Sound, Power, Network, Windows Update, System Maintenance, App, and several other Troubleshooters in Windows from the command line using MSDT.exe, via Settings or using FixWin.

Run built-in Windows Troubleshooter from the command line

To run any Troubleshooter open an elevated command prompt and run these commands:

To invoke built-in Troubleshooters, use this command:

msdt.exe /id <diagnostic_id>

To run a custom-built troubleshooter stored locally use this command line:

msdt.exe /path <path_to_troubleshooter>

To run a troubleshooter which is in a .diagcab file format, use this:

msdt.exe /cab <path_to_diagcab>

For instance, if you want to bring up the built-in Power Troubleshooter to troubleshoot problems relating to power or battery, run this command:

msdt.exe /id PowerDiagnostic

Once you hit Enter, you will see the Power Troubleshooter pop-up. Similarly, if you know the Diagnostic Pack ID of any Troubleshooter, you will be able to invoke it using the command line.

How to run Troubleshooter in Windows 10

Here is a list of some Troubleshooting Pack ID’s sourced from TechNet, for your ready reference

Troubleshooting Pack ID Description Application or Feature Dependency
AeroDiagnostic Troubleshoots problems displaying Aero effects like transparency. Aero Display Theme installed
NetworkDiagnosticsDA Troubleshoots problems connecting to a workplace network over the Internet using Direct Access. Direct Access installed
DeviceDiagnostic Troubleshoots problems using hardware and access devices connected to the computer.
HomeGroupDiagnostic Troubleshoots problems viewing computers or shared files in a homegroup. HomeGroup installed
NetworkDiagnosticsInbound Troubleshoots problems with allowing other computers to communicate with the target computer through Windows Firewall.
NetworkDiagnosticsWeb Troubleshoots problems connecting to the Internet or to a specific Web site.
IEDiagnostic Helps the user prevent add-on problems and optimize temporary files and connections. Internet Explorer installed
IESecurityDiagnostic Helps the user prevent malware, pop-ups, and online attacks. Internet Explorer installed
NetworkDiagnosticsNetworkAdapter Troubleshoots problems with Ethernet, wireless, or other network adapters.
PerformanceDiagnostic Helps the user adjust settings to improve operating system speed and performance.
AudioPlaybackDiagnostic Troubleshoots problems playing sounds and other audio files. Audio output device installed
PowerDiagnostic Helps the user adjust power settings to improve battery life and reduce power consumption.
PrinterDiagnostic Troubleshoots problems printing.
PCWDiagnostic Helps the user configure older programs so that they can run in the current version of Windows.
AudioRecordingDiagnostic Troubleshoots problems recording audio from a microphone or other input source. Audio input device installed
SearchDiagnostic Troubleshoots problems with search and indexing using Windows Search. Search enabled
NetworkDiagnosticsFileShare Troubleshoots problems accessing shared files and folders on other computers over the network.
MaintenanceDiagnostic Helps the user clean up unused files and shortcuts and perform other maintenance tasks.
WindowsMediaPlayerDVDDiagnostic Troubleshoots problems playing a DVD using Windows Media Player. Windows Media Player installed
WindowsMediaPlayerLibraryDiagnostic Troubleshoots problems with adding media files to the Windows Media Player library. Windows Media Player installed
WindowsMediaPlayerConfigurationDiagnostic Helps the user reset Windows Media Player settings to the default configuration. Windows Media Player installed
WindowsUpdateDiagnostic Troubleshoots problems that prevent Windows Update from performing update tasks.

Run Troubleshooters via Settings

Troubleshoot page in Windows 10

You can also access the Troubleshooters via Windows Settings. Press Win+I to open Settings > Update & security > Troubleshoot. Here you will see all the Troubleshooters. More on this at – Run Troubleshooters using the Troubleshoot page.

Run Troubleshooters using FixWin

Although most of us access these Troubleshooters via Settings or the Taskbar search, there is an easy way! Use our FixWin 10 to open them with a click!

Previously, one could access Troubleshooters via the Control Panel > Troubleshooting applet or download them from the Microsoft website. However, Microsoft is now providing quite the same functionality within the Windows 10 Settings app.


Posted by on , in Category Windows with Tags
Anand Khanse is the Admin of, a 10-year Microsoft MVP Awardee in Windows (2006-16) & a Windows Insider MVP. Please read the entire post & the comments first, create a System Restore Point before making any changes to your system & be careful about any 3rd-party offers while installing freeware.


  1. DFWDraco76

    I’ve found on a number of our Windows 10 machines I’m having to run the Windows Update Troubleshooter monthly in order to get updates to install.
    The command line is great, but I’m wondering if there’s a way to run this silently and have it automatically apply fixes? At the rate I’m going now I can’t get any of my projects knocked out because I’m in a neverending loop of getting Windows Updates installed.

  2. Derp

    Have you looked at running a .bat file to do it for you? Create a scheduled task to run the .bat file that instructs it to update windows from the command line.

  3. DFWDraco76

    Yes, that’s the idea — once I figure out the command to run it silently and have it automatically apply the fixes…

  4. Odoyle

    Did you find the command to run it silently? I have the same issue you describe in our environment.

  5. DFWDraco76

    No, but I’m not having the problem on 1703. It was just the previous build that seemed to be flaky with updates…

  6. Odoyle

    Thanks for the reply! Good to know 1703 is less flaky.

  7. Erik

    msdt.exe /cab is great. Or, I could just double click it. What we need is how to build the Answer file to use with the /af parameter.

Leave a Reply

Your email address will not be published. Required fields are marked *

8 + 8 =