Windows · Troubleshooting

Run Windows Troubleshooters

Troubleshoot gathers Windows' built-in automated diagnostic tools in one place, covering internet connections, audio playback and recording, printers, Bluetooth, Windows Update, and more. Each troubleshooter runs a scripted sequence of checks against the specific feature it targets and applies a fix automatically wherever it safely can, instead of requiring you to already know the underlying cause.

How to open Troubleshoot

  1. Open Settings → System → Troubleshoot.
  2. Click 'Other troubleshooters' to see the full list by category.
  3. Select the troubleshooter matching your issue and click 'Run'.
  4. Follow any on-screen prompts and review the summary once it finishes.

What you should know

  • Open 'Other troubleshooters' to browse every diagnostic tool grouped by category, such as Internet Connections, Printer, or Playing Audio.
  • Each troubleshooter reports what it checked, what it found, and whether it applied a fix automatically.
  • Some troubleshooters pause partway through to ask a clarifying question, like which specific device is affected.
  • 'Recommended troubleshooting' can let Windows run relevant troubleshooters automatically the moment it detects a matching problem.

A troubleshooter reporting 'no problems found' only means it didn't detect the specific conditions it's scripted to check for, not that your system is definitely problem-free.

Why it matters

Troubleshoot turns vague symptoms like 'my internet feels slow' or 'sound isn't working' into a structured diagnostic pass instead of guesswork, and it's often the fastest way to resolve common issues without searching forums for the right fix. Because these tools run the same checks Microsoft support agents would typically walk you through manually, running one first can save real time before escalating to a support call. For less technical users especially, it's a safe first step that rarely makes a problem worse and frequently resolves it outright.

Best practices

  • Run the specific troubleshooter that matches your symptom, like 'Playing Audio' for sound issues, rather than trying every one you see.
  • Read the troubleshooter's summary at the end even when it reports finding nothing, since it sometimes explains what it checked and what to try next.
  • Enable 'Recommended troubleshooting' at its default 'Ask me before running' level so you stay aware of what's being run automatically.
  • Restart the affected app or device after a troubleshooter applies a fix, since some changes don't take effect until then.
  • Treat a resolved troubleshooter result as a first fix, not a final diagnosis, if the same problem recurs shortly after.

Common problems and fixes

The troubleshooter closes immediately without showing any results.
Run it again from an administrator account, since certain troubleshooters, particularly ones touching system services, silently fail without elevated permissions.
A troubleshooter says it fixed the problem, but the issue immediately returns.
Restart the PC to let the applied fix fully take effect, and if it still recurs, treat that as a sign the actual cause needs deeper investigation, like Device Manager or Event Viewer.
'Other troubleshooters' doesn't list a tool for your specific problem.
Search directly for the classic Control Panel troubleshooter pack via 'Find and fix other problems' or check the specific feature's own settings page for a dedicated repair option.

Tips and tricks

  • Right-click the Start button and search 'troubleshoot' as a quicker way to jump straight into this page.
  • Check the audio, network, and Windows Update troubleshooters first for the most common everyday issues, since they cover the majority of typical complaints.

Frequently asked questions

Do troubleshooters ever make a problem worse?

It's rare — troubleshooters are designed to be conservative and generally only reset settings to known-good defaults, though resetting a customized configuration back to default is occasionally more disruptive than the original issue.

Can I see what a troubleshooter actually changed?

The results screen at the end lists what it checked and fixed in plain language, though it doesn't always show the exact technical setting it modified.

Should I run a troubleshooter before contacting support?

Yes, it's a reasonable first step for common issues and can resolve many problems immediately, though persistent or unusual issues still benefit from direct support afterward.

More Troubleshooting guides for Windows

See every Windows guide