Fix Windows 10 Troubleshooter Not Working

If the Windows 10 troubleshooter won’t open, runs but finds no problems, or crashes mid-scan, the fix usually involves resetting the troubleshooting service, clearing its cache, or running it from the Settings app instead of the Control Panel. Below are the exact steps to get it working again, plus the common causes and what to do when the built-in tool still fails.

Why the Troubleshooter Stops Working

The Windows 10 troubleshooter is a built-in diagnostic tool that scans for and automatically fixes common system problems, like broken network connections, audio output issues, Windows Update errors, and printer setup faults. It relies on a background service called the Diagnostic Policy Service (DPS), plus a set of PowerShell scripts and cached data stored under C:\ProgramData\Microsoft\Diagnosis.

When it fails, it’s usually one of these:

• The Diagnostic Policy Service is disabled or stuck.
• Corrupted cache files in the Diagnosis folder.
• Third-party antivirus or a group policy blocking the tool.
• Outdated Windows 10 build (the tool is updated via Windows Update).
• Conflicts with the Control Panel version of the troubleshooter.

Quick Fix: Restart the Diagnostic Service

The most common reason a troubleshooter won’t start is that the Diagnostic Policy Service isn’t running. Here’s how to check and restart it:

1. Press Win + R, type services.msc, and press Enter.
2. Scroll down to Diagnostic Policy Service. Right-click it and select Restart (if it’s not running, select Start).
3. Also check Diagnostic Service Host and Diagnostic System Host – set them to Automatic and start them if they’re stopped.
4. Close the window and try the troubleshooter again.

If the service won’t start, double-click it, go to the Log On tab, and make sure Local System Account is selected. Then try starting it manually.

Clear the Troubleshooter Cache

Corrupted cache files are another frequent culprit. The troubleshooter stores temporary data that can become stale or broken after a failed run. Clearing it forces the tool to rebuild from scratch.

1. Open File Explorer and navigate to C:\ProgramData\Microsoft\Diagnosis.
2. Select all files and folders inside (press Ctrl + A), then delete them. If some are in use, skip them and reboot, then try again.
3. Press Win + R, type cmd, and run as administrator.
4. Type msdt.exe -ep WindowsHelp and press Enter – this resets the troubleshooter’s internal database.

Alternatively, you can use the built-in Disk Cleanup tool to clear the “Diagnostic data” cache, but the manual deletion above is more thorough.

Run It from the Settings App (Not Control Panel)

Windows 10 has two versions of the same troubleshooter: the old one in Control Panel and the newer one in Settings. The Settings version is more reliable and includes extra troubleshooters. If the Control Panel version fails, try the Settings one:

1. Open Settings (Win + I).
2. Go to Update & Security > Troubleshoot.
3. Select the relevant troubleshooter (e.g., Internet Connections, Audio) and click Run the troubleshooter.

If the Settings page itself won’t open or the troubleshooters are missing, you may need to repair the Settings app. Run PowerShell as administrator and execute:

Get-AppxPackage Microsoft.Windows.Settings | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

This re-registers the Settings app without losing personal data.

Use the Windows Update Troubleshooter as a Test

Sometimes the issue is specific to one troubleshooter, not the whole tool. The Windows Update troubleshooter is the most complex and the most likely to fail. If it works, your problem is isolated. If it doesn’t, the core service is broken.

To run it: Settings > Update & Security > Troubleshoot > Windows Update > Run the troubleshooter. It will check for pending updates, corrupted update files, and service misconfigurations.

If it fails with an error, note the error code. Common ones like 0x80070002 or 0x800f081f usually point to missing or corrupt system files. In that case, run the System File Checker:

1. Open Command Prompt as administrator.
2. Type sfc /scannow and press Enter. Let it finish (it can take 15–20 minutes).
3. If it finds issues but can’t fix them, run DISM /Online /Cleanup-Image /RestoreHealth and then rerun SFC.

When the Troubleshooter Finds Nothing

If the troubleshooter runs but reports “no problems found,” that doesn’t always mean your system is fine. The tool only checks for specific, known issues. For example, the network troubleshooter won’t detect a faulty DNS server if your IP configuration is valid – it just sees “connected.”

In those cases, try the following:

• Restart your router and modem.
• Run ipconfig /flushdns and ipconfig /renew in Command Prompt.
• Check if the issue occurs in Safe Mode – if not, a third-party app is interfering.
• Use the Event Viewer (under Windows Logs > System) to look for error warnings around the time the problem started.

If the troubleshooter is for audio and it finds nothing, check your default playback device (right-click the speaker icon > Sounds > Playback tab) and ensure the correct device is set as default.

Reset the Entire Troubleshooting Infrastructure

If none of the above works, you can reset the whole diagnostic framework. This is a bit more advanced but safe:

1. Open an elevated PowerShell (right-click Start > Windows PowerShell (Admin)).
2. Run the following commands one by one:

net stop dps
net stop wdi\systemhost
net stop wdi\servicehost
net stop wdi\log

Then delete the contents of C:\ProgramData\Microsoft\Diagnosis again, and restart the services:

net start dps
net start wdi\systemhost
net start wdi\servicehost
net start wdi\log

Finally, restart your PC. This clears all diagnostic state and forces the system to recreate the necessary files.

Frequently Asked Questions

Why does the troubleshooter close immediately after opening?

This usually means the Diagnostic Policy Service is not running or the cache is corrupted. Follow the service restart steps first, then clear the Diagnosis folder. If it still closes, run msdt.exe -ep WindowsHelp from an admin command prompt to reset the tool.

Can I download a standalone troubleshooter?

Yes, Microsoft offers standalone troubleshooters for specific issues (like Windows Update or network) on its official support site. They are .diagcab files that run without the Settings app. However, they rely on the same underlying services, so if the built-in tool is broken, these may fail too.

Will resetting Windows fix the troubleshooter?

Often, yes, because it resets all system files and services. But before doing that, try the steps above. A full reset is time-consuming and will remove installed apps unless you choose “Keep my files.” It should be a last resort.

Why does the troubleshooter say “troubleshooting couldn’t identify the problem”?

This generic message means the tool ran but didn’t find any known issue. It’s not a failure of the tool itself. Check the specific logs (Event Viewer) or try a different troubleshooter. For network issues, try the “Network Adapter” troubleshooter in addition to “Internet Connections.”

Does the troubleshooter fix everything?

No. It’s designed for common, well-defined problems. For deeper issues like driver corruption or malware, you’ll need other tools like Device Manager, SFC, or a dedicated antivirus scan. The troubleshooter is a first step, not a magic bullet.

Related

• Error 910 on Google Play Store: Fixes That Work
• How to Set Personalized Spatial Audio on AirPods
• Fix Network Security Key Isn’t Correct in Windows 11