If the Windows Troubleshooter won’t open, runs but does nothing, or fails with an error, the fix usually involves resetting the tool’s cache, running it from a different location, or repairing system files. This guide covers the most common causes and step-by-step fixes for Windows 10 and Windows 11.
Why the Troubleshooter Stops Working
The built-in Windows Troubleshooter is a diagnostic tool that checks for common problems with audio, network, printers, Windows Update, and other components. It relies on a set of background services and cached data to function. When it fails, the cause is often one of these:
- Corrupted cache files – The troubleshooter stores temporary data that can become outdated or damaged.
- Disabled services – The Diagnostic Policy Service or Windows Update service may be turned off.
- Group Policy restrictions – Some settings can block the tool from running.
- Outdated system files – Missing or corrupted Windows files can break the tool.
- Third-party conflicts – Security software can interfere with the diagnostic process.
First Steps: Restart and Run from Settings
Before diving into deeper fixes, try the simplest ones. Restart your PC – this clears temporary glitches. Then open the troubleshooter from the Settings app, not the Control Panel, because the Settings path is more reliable in recent Windows versions.
- Press Windows + I to open Settings.
- Go to System > Troubleshoot > Other troubleshooters (Windows 11) or Update & Security > Troubleshoot (Windows 10).
- Select the relevant troubleshooter and click Run.
- If it opens but shows no issues, click View detailed information to see what it actually checked.
If the tool doesn’t appear in the list, your Windows version may have removed it – some legacy troubleshooters are being phased out. In that case, use the Get Help app or the online Microsoft Support tool instead.
Reset the Troubleshooter Cache
A corrupted cache is the most common reason the tool fails to launch or hangs. Resetting it is safe and takes only a minute.
- Open File Explorer and navigate to:
C:\ProgramData\Microsoft\Diagnosis(you may need to enable hidden files). - Delete the DiagPkg and DiagScript folders (their contents will be rebuilt automatically).
- Alternatively, open Command Prompt as administrator and run:
msdt.exe -ep WindowsHelp– this resets the troubleshooting pack cache. - Reboot and try the troubleshooter again.
If you don’t see those folders, they may be hidden. In File Explorer, click View > Options > View and select Show hidden files.
Run System File Checker and DISM
If the cache reset doesn’t help, your Windows system files might be damaged. The System File Checker (SFC) and Deployment Imaging Service and Management Tool (DISM) can repair them.
- Open Command Prompt as administrator (right-click Start and choose Terminal (Admin) or Command Prompt (Admin)).
- Run
sfc /scannowand wait for it to complete (may take 10-15 minutes). - If SFC finds errors but can’t fix them, run
DISM /Online /Cleanup-Image /RestoreHealth. - Reboot and try the troubleshooter again.
Note: DISM requires an internet connection to download missing files. If you’re offline, it may fail – in that case, run it again after connecting.
Check the Diagnostic Policy Service
The Troubleshooter depends on the Diagnostic Policy Service (DPS). If this service is disabled, the tool won’t run. Here’s how to verify it:
- Press Windows + R, type
services.msc, and press Enter. - Scroll to Diagnostic Policy Service.
- Right-click it and select Properties.
- Set Startup type to Automatic and click Start if it’s not running.
- Click Apply and OK.
Also check Diagnostic Service Host and Diagnostic System Host – they should also be set to Automatic (or Manual is fine, as long as they’re not disabled).
Run the Troubleshooter in Safe Mode
Third-party software can interfere with the troubleshooter. Booting into Safe Mode loads only essential drivers and services, which helps isolate the problem.
- Open Settings > System > Recovery > Advanced startup and click Restart now.
- After reboot, choose Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 or 5 to enter Safe Mode (with or without networking).
- Try the troubleshooter there. If it works, a background app is the culprit – you’ll need to uninstall or disable it.
Use the Windows Update Troubleshooter Manually
If the troubleshooter fails specifically for Windows Update, you can download the dedicated tool from Microsoft’s website (search for “Windows Update Troubleshooter”). This standalone tool works independently of the Settings app and often fixes update-related issues.
Alternatively, reset the Windows Update components manually:
- Open Command Prompt as administrator.
- Run these commands one by one:
net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserverren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.oldnet start wuauservnet start cryptSvcnet start bitsnet start msiserver
- Reboot and try Windows Update again.
This resets the update cache without harming your system.
When All Else Fails: Create a New User Account
If the troubleshooter still won’t run, your user profile may be corrupted. Creating a new local administrator account is a quick test.
- Open Settings > Accounts > Other users > Add account.
- Choose I don’t have this person’s sign-in information and then Add a user without a Microsoft account.
- Create a new username and password.
- Log into that account and try the troubleshooter.
If it works, you can migrate your files or simply use the new account. This isn’t a permanent fix, but it confirms the issue is profile-related.
Frequently Asked Questions
Why does the troubleshooter open but immediately close?
This usually indicates a corrupted cache or a missing system file. Try the cache reset (delete DiagPkg and DiagScript folders) and then run SFC. If it still closes, check if your antivirus is blocking it – temporarily disable it and test.
Can I run the troubleshooter from Command Prompt?
Yes. You can launch specific troubleshooters using the msdt.exe command with a GUID (e.g., msdt.exe /id WindowsUpdateDiagnostic). However, in Windows 11, many of these GUIDs no longer work – Microsoft is moving to the Settings app. So this method is less reliable now.
Will resetting the PC fix the troubleshooter?
Usually yes, but it’s a last resort. Resetting Windows reinstalls the OS while keeping your files (if you choose that option). It clears all system-level corruption. Before doing that, try the other fixes – they solve the problem in most cases.
Is the troubleshooter the same as the Get Help app?
No. The built-in Troubleshooter is a set of diagnostic scripts. The Get Help app is a chat-based support tool that can also run diagnostics remotely. If the built-in tool fails, the Get Help app might still work because it uses a different engine.
Why does the troubleshooter say “Troubleshooting couldn’t complete”?
This error usually means the tool ran into an unexpected problem – often a corrupted cache or a service that stopped mid-run. Follow the cache reset and service check steps above. If it persists, run DISM to repair the system image.
Does the troubleshooter fix hardware issues?
It can diagnose some hardware problems (like audio or printer) but it cannot repair physical damage. It will suggest drivers or settings changes. For hardware failures, you’ll need to replace the component or contact the manufacturer.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Error 0x8007025d in Windows 10
- Fix Alexa App Stuck on Setup
- Android Camera for 7 Office Tasks: Step-by-Step
- Pair Phone to Pioneer Stereo After Bluetooth Reset
- Fix Windows Not Saving Remote Desktop Credentials
- Essential Tips for macOS Users Switching to Windows