How to Run a Troubleshooter for PC Issues in Windows 11 and 10 (Complete 2026 Guide)

To run a troubleshooter for PC issues in Windows 11, open Settings (Win+I), click System, then Troubleshoot, then Other troubleshooters, and click Run next to the relevant tool. In Windows 10, go to Settings > Update and Security > Troubleshoot > Additional troubleshooters. The Get Help app now powers most troubleshooters as Microsoft phases out the legacy MSDT platform.

Most users open a troubleshooter, click through the wizard, and assume the problem is fixed when the tool reports success. Then the same issue appears again an hour later. The reason is almost always the same: they ran the wrong troubleshooter, ran it in the wrong order, or skipped three basic checks that would have resolved the issue without any tool at all.

This Axeetech guide fixes that. It covers which troubleshooter to run for each specific problem, all three methods to access them in Windows 11, the Windows 10 path, command-line access for advanced users, what MSDT deprecation means for your current setup, and exactly what to do when a troubleshooter reports success but the problem persists.

Which Troubleshooter Should You Run? (Symptom Quick Reference)

Pick your symptom from the table below before touching any settings menu. Running the right tool first saves significant time.

Your Problem	Troubleshooter to Run	Where to Find It	Key Tip
Internet or Wi-Fi not working	Internet Connections, then Network Adapter if that fails	Other troubleshooters (Win 11) or Additional troubleshooters (Win 10)	Run Internet Connections first. Run Network Adapter only if the first tool does not fix it.
No sound from speakers	Playing Audio	Other troubleshooters	This tool handles speaker output only. For microphone problems, run Recording Audio instead.
Microphone not working	Recording Audio	Other troubleshooters	Completely separate from Playing Audio. Run this specifically when voice input fails.
Windows Update failing	Windows Update	Other troubleshooters (Win 11) or Additional troubleshooters (Win 10)	This resets update components and clears the download cache.
Printer not found or not printing	Printer	Other troubleshooters	The printer must be powered on and connected before running or the tool cannot detect the device.
Bluetooth not connecting	Bluetooth	Other troubleshooters	For hardware-level Bluetooth issues, also check Device Manager after running.
Slow PC	Power, then System Maintenance	Control Panel > Troubleshooting > System and Security	No single slow PC troubleshooter exists. Run Power first, then System Maintenance.
Apps not opening	Windows Store Apps	Other troubleshooters	Works for Microsoft Store apps specifically. For non-Store apps, use Control Panel > Troubleshoot > Programs.

How to Run a Troubleshooter For PC Issues in Windows 11 (Step-by-Step)

Windows 11 offers three distinct paths to access troubleshooters. The Settings path is fastest for most users. The Get Help app is the direction Microsoft is actively pushing all troubleshooting toward. The Control Panel path remains essential for tools that Microsoft removed from Settings but did not fully replace.

Method 1: Via Settings (Fastest Method)

1. Press Win+I to open Settings.
2. Click System on the left side.
3. Click Troubleshoot on the right side.
4. Click Other troubleshooters.
5. Find the troubleshooter matching your problem in the list.
6. Click Run next to it.
7. Follow the instructions in the Get Help app that opens.

Tip: The Other troubleshooters page lists all available manual troubleshooters. Scroll down to see the full list. If your problem does not have a matching tool, try the Control Panel path or the command-line method described in the next section.

Method 2: Via the Get Help App

1. Press the Start button and search for Get Help.
2. Open the Get Help app.
3. In the search bar, type the name of your problem (for example, “audio not working” or “printer not found”).
4. If a troubleshooter is available for your problem, the app offers to run it automatically.
5. Click Yes or Allow to let the app apply the diagnostic.

Tip: In the Get Help app, broad search terms often return help articles rather than the diagnostic tool. Type specific phrases like “Run the Windows Update troubleshooter” rather than just “update” to reach the correct tool directly.

Method 3: Via Control Panel (For Removed and Legacy Troubleshooters)

1. Press Win+R, type control, and press Enter.
2. Click System and Security.
3. Click Troubleshooting.
4. Click View all in the left pane.
5. Select the troubleshooter you want and follow the prompts.

Tip: Control Panel is the only remaining graphical path for troubleshooters Microsoft removed from the Settings menu. The Power troubleshooter and System Maintenance troubleshooter both live here exclusively. If a tool does not appear under Settings > System > Troubleshoot, check Control Panel before assuming it does not exist.

How to Run a Troubleshooter in Windows 10

1. Press Win+I to open Settings.
2. Click Update and Security.
3. Click Troubleshoot in the left pane.
4. You will see two sections: Recommended troubleshooters, and Find and fix other problems.
5. Click Additional troubleshooters to see the full list.
6. Click the troubleshooter matching your issue.
7. Click Run the troubleshooter.

Tip: Windows 10 reached end of support on October 14, 2025. Microsoft no longer provides free security updates for Windows 10. Troubleshooters still work on Windows 10, but upgrading to Windows 11 is the recommended path for continued security coverage and access to the newer Get Help troubleshooting platform.

If your Windows PC shows a system-level message about repairs during startup rather than a troubleshooter result, that is a different scenario covered in the system repairing itself guide on AxeeTech, which explains what that message means and how to resolve it.

How to Run a Troubleshooter from the Command Line

The command-line method gives faster access for repeated use and reaches troubleshooters that the Settings menu no longer lists. This method is primarily useful for IT administrators and advanced users managing multiple machines.

Using msdt.exe (Legacy, Being Phased Out)

Open an elevated Command Prompt or PowerShell window and run these commands:

msdt.exe -id NetworkDiagnosticsWeb

Opens the Internet Connections troubleshooter.

msdt.exe -id WindowsUpdateDiagnostic

Opens the Windows Update troubleshooter.

msdt.exe -id AppsDiagnostic

Opens the Windows Store Apps troubleshooter.

msdt.exe -id DeviceDiagnostic

Opens the Hardware and Devices troubleshooter. This tool no longer appears in Settings on current Windows 11 builds but remains accessible via command on older builds.

msdt.exe -id AudioPlaybackDiagnostic

Opens the Playing Audio troubleshooter.

Warning: msdt.exe is being deprecated by Microsoft. On Windows 11 builds running 23H2, 24H2, and 25H2, these commands now redirect to the Get Help app instead of opening the legacy dialog boxes. On Windows 11 22H2 and older, and on Windows 10, the legacy MSDT interface still appears. Confirm your Windows version before relying on these commands in a script or automation workflow.

Using GetHelpCmdLine (The 2026 Replacement)

Microsoft introduced GetHelpCmdLine as the enterprise command-line replacement for both MSDT and SaRA. As of March 10, 2026, SaRA was removed from all in-support Windows updates, including Windows 10 22H2, Windows 11 23H2, 24H2, and 25H2, and Windows Server 2022 and Windows Server 2025. GetHelpCmdLine is a self-contained diagnostic tool that runs at the command line or through PowerShell scripts. It preserves the automation and scripting use case that SaRA previously served, in a more secure and maintained package than the legacy MSDT architecture.

Tip: If you are an IT administrator who relied on SaRA for diagnosing Outlook, Office, or Windows issues across managed devices, GetHelpCmdLine is now the correct replacement path. Microsoft’s official deprecation notice covers the full transition details.

Understanding MSDT Deprecation: What Changed in 2026

The Microsoft Support Diagnostic Tool (MSDT) powered most Windows troubleshooters for years through the msdt.exe process. Microsoft began phasing it out primarily because of the Follina vulnerability (CVE-2022-30190), which allowed the ms-msdt: protocol to be abused to execute malicious code delivered through Word and Excel documents. The deprecation followed a structured timeline.

Year	What Happened
2023	Microsoft began redirecting some legacy troubleshooters to the Get Help app
2024	Microsoft completed troubleshooter redirection and removed remaining legacy tools
2025	MSDT platform deprecated on current Windows 11 builds running 23H2 and later
March 2026	SaRA command-line utility removed from all in-support Windows updates
Now (2026)	Get Help app and GetHelpCmdLine are the primary troubleshooting platforms

What this means practically in 2026:

On Windows 11 running 23H2, 24H2, or 25H2, most legacy troubleshooters now open Get Help instead of the old MSDT dialog box. On Windows 11 22H2 and older, and on Windows 10, the legacy MSDT troubleshooters still work normally. Some troubleshooters were removed entirely with no Get Help replacement, including the Keyboard troubleshooter, Speech troubleshooter, and the Blue Screen troubleshooter (which Microsoft removed earlier in Windows 10 v1809).

Troubleshooters that remain available live in the C:\Windows\diagnostics\index folder on machines where MSDT is still active. This folder is the underlying source that msdt.exe reads when launching a diagnostic package.

Tip: If you see the message “Troubleshooters have moved and this tool will be retired” when clicking a troubleshooter, your device runs a version of Windows 11 where MSDT is being phased out. Use the Get Help app or the Settings > System > Troubleshoot > Other troubleshooters path instead.

Windows 11 Troubleshooter Settings: Critical vs Recommended

Windows 11 runs two types of troubleshooting in the background without requiring you to manually launch anything. Understanding the difference helps you configure the system correctly for your use case.

Critical Troubleshooting (Automatic, Always On)

Critical troubleshooting runs automatically and silently in the background. It repairs corrupt settings that prevent essential services from running, makes hardware-level adjustments, and applies system changes required for Windows to function correctly with your installed software and hardware. Critical troubleshooting cannot be turned off and does not notify you when it activates or when it completes a fix.

Recommended Troubleshooting (Requires Permission)

Recommended troubleshooting handles non-critical problems that affect your experience but do not prevent Windows from running. Unlike critical troubleshooting, recommended troubleshooting requires your permission before applying any fix because the changes may affect settings you have customized. You configure how Windows handles recommended troubleshooting through three auto-run modes:

Mode	What It Does	Best For
Run automatically, don’t notify me	Applies recommended fixes silently without any interaction	Shared or managed devices where silent operation is preferred
Run automatically, then notify me	Applies the fix first, then shows a notification confirming what changed	Home users who want fast fixes and a record of changes
Ask me before running (default)	Shows a prompt before applying any fix, giving you full approval control	Users who want complete control over every system change

To change this setting, go to Settings > System > Troubleshoot, then select your preferred mode.

How to View Troubleshooter History

Automatic troubleshooting history shows what recommended fixes Windows applied without your direct involvement. Go to Settings > System > Troubleshoot > Recommended troubleshooter history to review past automatic actions. Note that manually triggered troubleshooters (the ones you run yourself from Other troubleshooters) do not appear in this history log, only the automatic recommended fixes do.

What to Do When the Troubleshooter Does Not Fix the Problem

Troubleshooters resolve most common Windows problems, but they are not guaranteed to fix every issue. When a troubleshooter reports success but the problem returns, or when it reports it could not fix the issue, escalate in the following order:

Step	Action	Command or Path	When to Use
1	Check Windows Update	Settings > Windows Update > Check for updates	Always do this first. Many issues disappear after a pending update installs.
2	Run SFC to repair system files	Elevated Command Prompt	After a troubleshooter fails to fix suspected file corruption
3	Run DISM to restore the component store	Elevated Command Prompt	After SFC fails or finds errors it cannot repair
4	Roll back a recently installed driver	Device Manager > right-click device > Properties > Driver > Roll Back	After recent hardware changes or driver updates introduced the problem
5	Use System Restore	Control Panel > Recovery > Open System Restore	After multiple repair attempts fail; reverts to a known working state

Run SFC first:

sfc /scannow

Then run DISM if SFC does not fully resolve the issue:

DISM /Online /Cleanup-Image /RestoreHealth

Warning: Always run SFC before DISM. If SFC repairs errors, run it a second time to confirm the repair completed fully. DISM is the next step only when SFC either cannot repair the errors it found or returns a clean result but the underlying problem continues.

For specific problem areas, dedicated guides cover the full escalation path. If Windows Update errors persist after running the Windows Update troubleshooter, the complete Windows Update fix guide covers every escalation step including manual component resets. If audio issues remain after running Playing Audio, the default playback device configuration guide covers driver, format, and exclusive mode fixes. If printer problems persist after running the Printer troubleshooter, the default printer settings guide covers the Printing Preferences vs Printing Defaults distinction that the troubleshooter does not address.

For microphone issues where the Recording Audio troubleshooter does not resolve the problem, the microphone privacy settings troubleshooting guide covers the Windows privacy toggle, registry fix, and Group Policy path that the built-in tool cannot access.

A Pre-Troubleshooter Checklist That Saves Time

Running a troubleshooter before checking the basics wastes time because the underlying issue often blocks the diagnostic tool from identifying the real cause. Before clicking Run on any troubleshooter, confirm these three points:

1. Run Windows Update first. Many PC problems resolve entirely after a pending update applies. Go to Settings > Windows Update > Check for updates, install any available updates, and restart the PC before running a troubleshooter.
2. Check physical connections. For internet problems, verify the Ethernet cable is fully seated or that Wi-Fi is connected to the correct network. For printer problems, confirm the printer is powered on and connected before launching the Printer troubleshooter, because the tool cannot detect an offline device. For audio problems, verify the output device is plugged in and confirm the volume is not muted in the taskbar.
3. Restart the PC. A fresh restart resolves a large number of issues caused by temporary software states, hung services, or cached errors. Many problems that seem to require a troubleshooter disappear after a single reboot.

Frequently Asked Questions

How do I run a troubleshooter in Windows 11?

Press Win+I to open Settings, click System, click Troubleshoot, click Other troubleshooters, and click Run next to the troubleshooter matching your problem. The Get Help app opens and guides you through the diagnostic. If the troubleshooter you need does not appear in Settings, try Control Panel > Troubleshooting > View all as an alternative path.

How do I run a troubleshooter in Windows 10?

Press Win+I to open Settings, click Update and Security, click Troubleshoot in the left pane, and click Additional troubleshooters to see the full list. Click the troubleshooter for your issue and click Run the troubleshooter. Windows 10 reached end of support on October 14, 2025, so upgrading to Windows 11 is recommended for continued security updates.

What troubleshooter should I run for internet problems?

Run the Internet Connections troubleshooter first from Settings > System > Troubleshoot > Other troubleshooters. If that tool does not resolve the issue, run the Network Adapter troubleshooter from the same location. Do not run both at the same time. Always run Internet Connections first, then Network Adapter only if the first tool fails.

What troubleshooter should I run for audio problems?

Run Playing Audio from Settings > System > Troubleshoot > Other troubleshooters for speaker and headphone output problems. For microphone input problems, run Recording Audio instead. These are separate tools that fix separate audio pathways. Running the wrong one wastes time without addressing the actual issue.

Why is my Windows troubleshooter not working?

The most common causes are running the wrong troubleshooter, a missing physical connection that blocks the tool from detecting the device, or running MSDT-based commands on a Windows 11 23H2 or later build where MSDT now redirects to Get Help. Also confirm that the PC ran all available Windows Updates before attempting the troubleshooter, as pending updates often resolve the underlying problem.

Where is the Hardware and Devices troubleshooter in Windows 11?

Microsoft removed the Hardware and Devices troubleshooter from the Settings menu in Windows 11, but it remains accessible on older builds via the command line. Open an elevated Command Prompt and run msdt.exe -id DeviceDiagnostic to launch it. On Windows 11 23H2 and later, this command redirects to Get Help. You can also find hardware-related tools through Control Panel > Troubleshooting > View all.

What is MSDT and why is Microsoft removing it?

MSDT stands for Microsoft Support Diagnostic Tool, the underlying engine that powered most Windows troubleshooters through the msdt.exe process. Microsoft began removing it primarily because of the Follina vulnerability (CVE-2022-30190), which allowed the ms-msdt: protocol to execute malicious code delivered through Office documents. The Get Help app is the replacement platform as of 2026.

What replaced MSDT after its deprecation?

The Get Help app replaced the MSDT platform for graphical troubleshooting on Windows 11. For command-line and enterprise scripted troubleshooting, Microsoft introduced GetHelpCmdLine as the direct replacement after removing SaRA on March 10, 2026. GetHelpCmdLine supports the same automation use cases that SaRA previously handled for diagnosing Outlook, Office, and Windows issues.

What should I do when a troubleshooter says it fixed the issue but the problem persists?

First, check Windows Update and install any pending updates. Then open an elevated Command Prompt and run sfc /scannow to repair system files. If SFC finds errors it cannot fix, follow up with DISM /Online /Cleanup-Image /RestoreHealth. If the problem started after a recent driver installation, roll it back through Device Manager. As a final step, use System Restore to revert to a state before the problem began.

How do I change Windows 11 troubleshooter settings to run automatically?

Go to Settings > System > Troubleshoot. Under Recommended troubleshooter preferences, select “Run automatically, then notify me” to apply fixes without waiting for approval and receive a notification after each fix. The default setting is “Ask me before running,” which requires your approval before any recommended fix is applied. Critical troubleshooting always runs automatically regardless of this setting and cannot be disabled.