Windows 11 includes built-in troubleshooters — automated diagnostic tools that check for common problems, identify what’s wrong, and in many cases fix it automatically. Most users discover these after calling tech support and being walked through Settings → Troubleshoot. They’re worth knowing about beforehand, because they solve common issues faster than manual troubleshooting for the problems they cover. We go deeper on the whole subject in our Windows 11 How-To Guides.
The caveat worth stating upfront: troubleshooters address the most common causes of each problem type. For unusual configurations, corporate environments, or problems with specific hardware, they may say “no issues found” while something is clearly broken. In those cases, troubleshooters are still useful as a first-pass check — a “no issues” result tells you the problem isn’t in the common-cause category and points toward more specific investigation.
Where to find troubleshooters
Settings → System → Troubleshoot → Other troubleshooters. The full list appears here, organised by category. The “Recommended” section at the top shows troubleshooters for issues Windows has detected may be present on the current system.
Each troubleshooter has a “Run” button. After running: a results screen shows what was checked, what was found, and what was fixed (or what requires manual attention). Most complete in under two minutes.
The most useful troubleshooters — and when to use them
Internet Connections: for any connectivity problem — browser not loading pages, applications not connecting, intermittent connection drops. Checks adapter status, DNS resolution, gateway connectivity, and internet access. Fixes: resets adapter settings, renews DHCP lease, flushes DNS cache. Use first for any “internet not working” scenario.
Playing Audio: for no sound or distorted sound in applications. Checks which audio device is set as default, service status, driver state, and volume mixer settings. Fixes: resets audio services, changes default audio device if none is selected. Run before digging into Volume Mixer or driver settings manually.
Windows Update: for update errors, updates stuck at a percentage, or Windows Update showing errors. Checks update service status, update cache integrity, and component registration. Fixes: clears corrupted update cache, restarts Windows Update services, re-registers update components. This is the fastest first step for any Windows Update problem.
Printer: for printers not found, printing errors, or queue stuck. Checks printer queue status, spooler service, driver state, and physical connection. Fixes: clears stuck print jobs, restarts the spooler service, prompts for driver reinstall if needed.
Bluetooth: for Bluetooth devices not appearing, pairing failures, or Bluetooth toggle missing. Checks Bluetooth service status and adapter state. Fixes: restarts Bluetooth services, enables the adapter if it was disabled.
Windows Update specific troubleshooter
The Windows Update troubleshooter deserves special mention because Windows Update problems are among the most common and most frustrating Windows issues. When an update fails with an error code: run this troubleshooter before anything else. It addresses the most common update failure causes — corrupted update components, stopped services, incomplete previous updates — in a single automated pass.
After the troubleshooter runs: restart and try Windows Update again. Success rate for the troubleshooter resolving Windows Update failures is high for the common error codes (0x80070002, 0x80080005, 0x800F0922, etc.). For errors that survive the troubleshooter: the more involved DISM and SFC repair commands are the next step.
Running DISM and SFC alongside troubleshooters
The troubleshooters handle application-level and service-level issues. For deeper Windows component corruption that troubleshooters can’t fix: two command-line tools go further.
Admin Command Prompt → run in this order:
DISM /Online /Cleanup-Image /RestoreHealthThis repairs the Windows component store using files from Microsoft Update servers (requires internet). Takes 10-30 minutes. After it completes:
sfc /scannowSystem File Checker scans all protected Windows files and replaces corrupted ones with known-good copies. Uses the component store that DISM just repaired. Takes 15-30 minutes. Run DISM first, then SFC — doing it in reverse order means SFC may be using a corrupted component store to repair files, which produces incomplete results.
Our guide on Windows 11 Update management covers update troubleshooting in more depth, and our Task Manager guide covers diagnosing problems that troubleshooters might point to but can’t automatically fix. For a complete list of Windows troubleshooter commands and their functions, Microsoft’s Windows troubleshooting documentation covers both the GUI troubleshooters and the command-line repair tools with step-by-step guidance.
Less-used troubleshooters worth knowing about
- Power: checks power plan settings against recommended settings. Useful if the machine sleeps unexpectedly or doesn’t sleep when expected.
- Video Playback: for video that stutters, shows artefacts, or won’t play in specific applications. Checks codec availability, hardware decoding settings, and display driver state.
- Search and Indexing: for Windows Search returning incomplete results or no results. Checks the Windows Search service and index integrity — the automated version of the manual index rebuild.
- Keyboard: for keyboard input problems — keys not registering, wrong characters appearing, modifier keys behaving unexpectedly (often Sticky Keys or Filter Keys accidentally enabled).
- Camera: for webcam not appearing in applications. Checks privacy settings (which apps have camera permission), driver state, and camera service status.
When troubleshooters say “no issues found”
A troubleshooter result of “no issues found” when the problem is clearly present means the problem isn’t in the category that troubleshooter covers. This is useful information, not a failure of the troubleshooter. If the internet troubleshooter finds nothing but the browser can’t load pages: the browser specifically (not the connection) is the problem. If the audio troubleshooter finds nothing but one specific application has no sound: that application’s own audio settings are the issue, not the Windows audio system.
The “no issues found” result narrows the problem scope — from “something in Windows audio” to “something in this specific application’s audio configuration.” That’s a diagnostic outcome worth having even without a fix.
| Problem | Troubleshooter to run first |
| Internet not working | Internet Connections |
| No sound / wrong sound device | Playing Audio |
| Windows Update failing | Windows Update |
| Printer not working | Printer |
| Bluetooth device won’t pair | Bluetooth |
| PC sleeping unexpectedly | Power |
| Video stuttering or not playing | Video Playback |
| Windows Search finding nothing | Search and Indexing |
| Camera not appearing in apps | Camera |
| Keys registering wrongly | Keyboard |
Built-in troubleshooters are genuinely underused relative to their effectiveness. They’re fast (usually under two minutes), risk-free to run, and address the most common causes of the issues they cover with automated fixes that would take longer to apply manually. Making them the first step when something breaks — before searching for solutions, before calling support, before more invasive changes — is one of the better habits available for Windows problem-solving. They don’t fix everything, but they fix the common things quickly.
Event Viewer — when troubleshooters aren’t enough
For problems that troubleshooters can’t resolve: Windows Event Viewer provides detailed logs of what happened and when. Win+S → “Event Viewer” → Windows Logs → System and Application logs contain error and warning entries that describe what failed, which service or driver was involved, and at what time. This is harder to interpret than troubleshooter output, but it provides information that the automated tools don’t surface.
Practical approach: reproduce the problem → open Event Viewer immediately → Windows Logs → System → sort by Date and Time → look for Error (red) entries near the time the problem occurred. The Event ID and Source fields help identify the specific component that failed. Searching the Event ID online usually surfaces Microsoft documentation or community discussions about that specific failure mode.
Event Viewer is the gap-filler when automated tools say “no issues” but something is clearly wrong. The combination of troubleshooters (fast, automated, handles common cases) plus Event Viewer (detailed, manual, handles unusual cases) covers the diagnostic range from simple to complex Windows problems without needing external tools.
Reliability Monitor — the problem timeline
A less-known tool that’s often more readable than Event Viewer for everyday troubleshooting: Reliability Monitor. Win+S → “reliability history” → shows a calendar view of system stability with markers for application crashes, Windows errors, and informational events. Clicking any day shows what happened specifically — which applications crashed, which updates were installed, which hardware changes occurred.
Reliability Monitor is particularly useful for correlating problems with changes: “the PC started acting up on Tuesday” → Reliability Monitor shows a Windows Update installed on Monday → the update is potentially the cause. This timeline view makes the connection between changes and problems much clearer than Event Viewer’s flat log format.
Get Help app — the guided troubleshooting path
Win+S → “Get Help” opens Microsoft’s support application. For common Windows problems, it provides step-by-step guided troubleshooting: select the category of problem, answer questions about symptoms, and the app walks through relevant steps. For some problems, it connects directly to Microsoft support agents for chat assistance.
Get Help is positioned between “run the troubleshooter” and “call support” — it provides more guidance than automated tools while being more accessible than full technical documentation. For users who find the raw Event Viewer or command-line DISM instructions intimidating: Get Help’s guided approach covers many of the same diagnostic steps in a more guided format.
Windows Recovery Environment
For problems severe enough that Windows can’t boot properly: the Windows Recovery Environment (WinRE) provides troubleshooting tools outside of the normal Windows session. Access by holding Shift while clicking Restart, or by booting from Windows installation media → Repair your computer.
Recovery options available in WinRE: Startup Repair (fixes common boot problems automatically), System Restore (rolls Windows back to a previous restore point), Command Prompt (for manual repair commands), and System Image Recovery (restores from a full system backup). These cover the scenarios where the normal Settings troubleshooters can’t run because Windows itself isn’t loading correctly.
Startup Repair in WinRE is the recovery-environment equivalent of the troubleshooters — it checks for and fixes common boot-related problems automatically. Like the settings-based troubleshooters, it works well for the common cases (BCD corruption, missing boot files, driver issues) and provides clear results about what it found and what it fixed or couldn’t fix.
The Windows 11 troubleshooting ecosystem is layered from easiest to most involved: Settings troubleshooters → Get Help guidance → Event Viewer and Reliability Monitor for diagnosis → DISM/SFC for repair → Windows Recovery Environment for severe issues. Progressing through these layers in order, rather than jumping to the most invasive option first, saves time and avoids making changes that aren’t needed for the problem at hand.
System Restore and restore points
System Restore is a related but separate tool from the troubleshooters. It reverts Windows’ system files, registry, and some settings to a previous state (a “restore point”) without affecting personal files. Restore points are created automatically before Windows Updates and driver installations, and can be created manually. Settings → System → About → System Protection → System Restore.
When to use System Restore: after a change that made things worse — a driver update that caused crashes, a Windows Update that broke something, a software installation that altered system behaviour. Restoring to a point before the problematic change reverts the specific change while keeping documents, photos, and other personal files intact.
System Restore requires that System Protection is enabled for the drive (Settings → System → About → System Protection → configure → turn on protection). It’s off by default on some configurations. Enabling it proactively means restore points are available when needed — enabling it after something goes wrong doesn’t help because there’s nothing to restore to.
Third-party diagnostic tools
When Windows’ built-in tools aren’t sufficient: a few third-party diagnostics cover what the built-in tools miss:
- Windows Memory Diagnostic: built-in (Win+R → mdsched) but worth calling out specifically — tests RAM for errors. Hardware RAM failure is a cause of random crashes, blue screens, and application errors that the Settings troubleshooters can’t detect. Run if Windows is crashing unpredictably and other software fixes haven’t helped.
- CrystalDiskInfo (free): reads S.M.A.R.T. data from hard drives and SSDs, providing health status and warning of impending drive failure. Blue screen crashes caused by a failing drive look similar to software crashes — CrystalDiskInfo distinguishes hardware from software causes.
- HWiNFO (free): detailed hardware sensor monitoring — temperatures, voltages, fan speeds. Useful when performance problems are caused by thermal throttling that the Settings troubleshooters won’t diagnose.
These tools fill specific diagnostic gaps that Windows’ built-in troubleshooters don’t address — hardware health and thermal state. For software problems: the built-in troubleshooters and Event Viewer cover most cases. For hardware-related symptoms: these tools provide the data Windows can’t. See also Windows 11 Narrator for a related case.
