Run a Troubleshooter for PC Issues Windows: Nine Built-In Tools That Actually Find the Fault

Windows ships with its own diagnostic utilities, and running one properly means opening the matching tool for the symptom rather than clicking a generic "fix it" button — Settings > System > Troubleshoot > Other troubleshooters in Windows 11, or Control Panel > Troubleshooting in Windows 10. The built-in troubleshooters work best on sound, network, printer, and update faults; they can't repair a failing drive or a corrupted Windows installation. This guide covers which tool maps to which fault, how to run each one, and when to stop troubleshooting and gather logs instead.

Which Built-In Troubleshooter Matches Your Windows Symptom

Start by naming the symptom, because Windows buries its troubleshooters in two separate places and each one only looks at a narrow slice of the system. In Windows 11, open Settings and go to System > Troubleshoot > Other troubleshooters. In Windows 10, the list lives in Control Panel under System and Security > Troubleshooting. Both open the same underlying engines, so the launcher matters less than the choice of tool.

The mapping is fairly literal. No sound from speakers or headphones → Playing Audio. A printer that sits in the queue → Printer. A Wi-Fi or Ethernet connection that drops or shows a yellow triangle → Network and Internet. Windows Update failing with an error code → Windows Update. Battery draining faster than expected → Power. These five cover most everyday faults and each finishes in roughly one to three minutes.

If your symptom isn't on that table — a blue screen, a disk that clicks, a PC that won't boot — no built-in troubleshooter will fix it. Those need Event Viewer, Windows Memory Diagnostic, or the manufacturer's drive tool, covered further down. According to Microsoft's support documentation, the troubleshooters are designed for "common problems" and explicitly cannot repair hardware damage or replace corrupted system files.

Pick the closest match and run only that one first. Running every troubleshooter in sequence generates a pile of "no problems found" results that tells you nothing and wastes twenty minutes. One fault, one tool, one set of results.

How to Run a Troubleshooter in Windows 11 Step by Step

Work through this sequence in order; each step takes under a minute and the whole run finishes in about three to five minutes for most tools. Keep a note of any error code the tool displays, because the code is the actual diagnostic output even when the troubleshooter reports it couldn't fix anything.

1: Press Windows + I to open Settings. 2: Select System in the left pane, then scroll to Troubleshoot. 3: Click Other troubleshooters. Every available tool appears with a Run button beside it. 4: Click Run next to the tool matching your symptom. A progress window opens and the tool begins checking. 5: If asked to choose a device — a specific speaker, printer, or network adapter — select the one that's failing, not the one Windows lists first. 6: Read the result screen. "Troubleshooting couldn't identify the problem" means the tool found nothing; "Fixed" means it applied a change; an error code means it found a fault but couldn't repair it automatically. 7: Click View detailed information or View history at the bottom of the Other troubleshooters page to see what was changed, including registry or service modifications the tool made.

If the tool reports a fix, test the symptom immediately before closing the window. Windows sometimes applies a change that requires a restart to take effect, and the tool will tell you when that's the case. If it reports a failure with a code, write the code down — do not run the same troubleshooter repeatedly, because it will return the same result.

The failure handling matters more than the happy path. A troubleshooter that runs for several minutes and then times out usually means the underlying service it depends on isn't responding; restart the PC and try once more, then move to manual diagnosis. A tool that closes instantly with no message often indicates a corrupted troubleshooter package, which you can reset by running the Microsoft Store Apps troubleshooter or the msdt.exe command from a Command Prompt with administrator rights.

Running the Legacy msdt Troubleshooters from Command Prompt

Windows still accepts direct launches of its diagnostic engine through the msdt.exe command, which lets you open a specific troubleshooter without hunting through menus — useful on Windows 10 machines where the Control Panel list is cluttered, and on Windows 11 systems where the modern Settings page occasionally fails to load. Open Command Prompt as administrator (search "cmd", right-click, Run as administrator) and type the command for your fault.

msdt.exe -id AudioPlaybackDiagnostic — sound output msdt.exe -id NetworkDiagnosticsWeb — internet connectivity msdt.exe -id PrinterDiagnostic — printer queue and spooler msdt.exe -id WindowsUpdateDiagnostic — update failures msdt.exe -id PowerDiagnostic — battery and power plan msdt.exe -id DeviceDiagnostic — hardware and driver faults

Each command opens the same wizard interface you'd reach through Settings, so the results are identical. The advantage is speed and the ability to script the launch. Microsoft has been gradually moving these diagnostics into the Settings app, and on some Windows 11 builds the msdt.exe identifiers still work while the Settings entry is missing — if a command returns "the troubleshooting wizard can't continue," the package isn't installed on that build and you should use Settings instead.

Don't confuse msdt.exe with msdtc, which is the Distributed Transaction Coordinator service and has nothing to do with consumer troubleshooting. Typing the wrong one is a common source of confusion in forum threads.

If a command launches and immediately asks for elevation, accept it; several diagnostics need administrator rights to read service states. If it runs but finds nothing, the result is genuine — the tool checked its known-fault list and your system didn't match. That's information, not failure, and it tells you to move to Event Viewer or the manufacturer's tools.

Windows Update Troubleshooter: What It Fixes and What It Hides

The Windows Update troubleshooter clears a defined set of blockers: it restarts the Windows Update and Background Intelligent Transfer Service (BITS) services, resets the SoftwareDistribution download cache, and checks that the update components are registered. In practice this resolves the most common update failures, including error 0x80070002 (missing or corrupted update files) and 0x80070643 (installation failure). A full run usually takes two to four minutes.

What it doesn't do is tell you why the update failed in the first place. The tool reports a generic result, applies its fixes, and moves on. If you want the actual cause, open Event Viewer (search "Event Viewer", expand Windows Logs > System) and filter for the WindowsUpdateClient source around the failure time — the event entry names the specific update and error. That record survives even after the troubleshooter clears the cache.

One edge case deserves attention: on systems where the update failure is caused by insufficient disk space, the troubleshooter will run and report success while the next update attempt fails again. Microsoft's own guidance lists roughly 20 GB of free space as a practical floor for feature updates, and the troubleshooter checks for space but doesn't always flag a marginal shortfall. Check free space on the system drive before trusting a "fixed" result.

If the troubleshooter loops — fixes, restarts, fails again on the same update — stop after two attempts and use the manual reset instead: stop the Windows Update and BITS services, rename the SoftwareDistribution folder, restart both services, and retry. That sequence is documented by Microsoft and goes further than the automated tool. The troubleshooter is a first pass, not a guaranteed repair.

Network, Sound, and Printer Troubleshooters in Practice

These three tools share a design: they enumerate the relevant devices, test each one, and apply a small set of known fixes. The Network and Internet troubleshooter resets the adapter, renews the IP address, flushes the DNS cache, and checks the default gateway. On a Wi-Fi drop, it will often report "the default gateway is not available" and reset the adapter — a real fix for a stuck DHCP lease, and useless if the router itself is offline.

The Playing Audio troubleshooter checks that the audio service (Windows Audio) is running, that the correct playback device is set as default, and that the driver reports no errors. It cannot fix a physically disconnected speaker or a headphone jack with a broken contact. If it reports "audio device is disabled," open Device Manager, find the device under Sound, video and game controllers, and enable it.

The Printer troubleshooter restarts the Print Spooler service, clears stuck print jobs, and checks the driver. The single most common printer fix it applies is clearing the spooler queue — if a job is wedged, the printer shows "offline" even when it's connected. A run takes about a minute.

Run these tools once each when the symptom matches. If all three return "no problems found" and the faults persist, the cause sits outside Windows — in the router, the cable, the speakers, or the printer's own firmware — and no amount of re-running the troubleshooter will change that. The tool's honest negative result is your cue to test the hardware directly.

When Troubleshooters Find Nothing: Event Viewer and Reliability Monitor

A troubleshooter that returns "no problems found" is not a dead end; it's a handoff. The two native tools that pick up where it stops are Event Viewer, which holds the raw log of every system event, and Reliability Monitor, which presents crashes and application failures on a timeline. Both are already installed and both are free. Reliability Monitor is the faster starting point: search "Reliability" in the Start menu, open "View reliability history," and look for red X entries in the days the fault appeared.

Event Viewer rewards a targeted approach. Open it, expand Windows Logs > System, and use Filter Current Log to narrow by level (Critical and Error) and by time. A disk fault shows as Event ID 7 or 51 from the disk source; a driver crash shows as Event ID 41 with a bugcheck code; a memory fault may appear as Event ID 46. Copy the event ID and source into a search alongside your Windows version — the combination is specific enough to find a real answer.

Reliability Monitor's advantage is chronology. It plots application failures, Windows failures, and warnings against a calendar, so if the faults began the day after a driver or update installed, the timeline shows it in one glance. Microsoft introduced the tool with Windows 7 and it remains unchanged in Windows 11, which means the interface you find in a tutorial from 2012 still matches what you'll see today.

Neither tool fixes anything. They generate evidence. The practical rule: if two different troubleshooters return no result on the same symptom, stop running troubleshooters and spend five minutes in Event Viewer instead. The event log almost always names a component, and a named component is something you can act on.

Hardware Faults Troubleshooters Cannot Repair

No built-in Windows troubleshooter can diagnose failing RAM, a dying drive, or a power supply that's dropping voltage. The Hardware and Devices troubleshooter checks driver status and device enumeration; it does not test the silicon. When a PC blue-screens randomly, freezes under load, or loses files, the diagnostic tools you need are different, and they're still built into Windows or available free from the manufacturer.

Windows Memory Diagnostic tests RAM. Search "Windows Memory Diagnostic," choose "Restart now and check for problems," and the PC reboots into a blue test screen that runs for roughly 10–30 minutes depending on RAM size. Results appear after Windows restarts; check Event Viewer under Windows Logs > System for the MemoryDiagnostics-Results source. A single passing run is reasonable evidence; intermittent faults sometimes need a second run.

For storage, run chkdsk C: /f /r from an elevated Command Prompt — the /r flag locates bad sectors and recovers readable data, and a full pass on a large drive can take several hours. For drive health beyond surface errors, use the manufacturer's own tool: Samsung Magician for Samsung SSDs, Crucial Storage Executive for Crucial drives, Western Digital Dashboard for WD drives. These read the drive's S.M.A.R.T. attributes, which Windows exposes only partially.

The hard boundary: if a drive reports reallocated sectors or a rising pending-sector count, back up immediately and replace the drive. Troubleshooting a failing disk in place risks the data. That's a stop condition, not a step in a sequence.

Built-In Diagnostics That Do More Than the Troubleshooters

Three less-known Windows tools outperform the troubleshooters for specific faults, and each is already on the machine. DirectX Diagnostic Tool (dxdiag) reports display, sound, and input device status and exports a text report you can share with support. System Information (msinfo32) lists every hardware and software component with versions and states. Windows Performance Monitor logs resource use over time and can prove whether a slowdown is CPU, disk, or memory bound.

The dxdiag report is the single most useful file to attach when asking for help on a graphics or audio problem, because it names the exact driver version and the display adapter model. Run it by typing dxdiag in the Start menu search, wait for the progress bar to finish, then click "Save All Information." The output is a plain text file.

msinfo32 answers "what's actually in this PC" questions in one screen — BIOS version, motherboard model, installed RAM, and every running service. When a troubleshooter result mentions a component you don't recognize, this is where you identify it. It also lists problem devices with a yellow flag, which is often faster than opening Device Manager.

Performance Monitor takes more setup but repays it. Add counters for Processor > % Processor Time, PhysicalDisk > % Disk Time, and Memory > Available MBytes, then watch under load. A disk pegged at 100% while CPU sits idle points to a storage bottleneck; available memory falling below a few hundred megabytes points to a RAM shortfall. These are measurements no troubleshooter makes. According to Microsoft's documentation for Performance Monitor, the tool has shipped with every consumer Windows release since Windows NT, which makes it the most durable diagnostic in the box.

Reading Troubleshooter Results and Building a Support Bundle

The result screen is short, and most of its value hides behind the "View detailed information" link. That page lists every check the tool performed, the state of each, and any change it made — including registry edits you might want to undo. Screenshot it before closing the window; the history view in Settings retains only a summary.

When a fault survives two troubleshooters and Event Viewer shows a repeating error, you're at the point where gathering a bundle beats further clicking. A useful bundle has four parts: the dxdiag text file, a Reliability Monitor report (the "Save reliability history" option produces an HTML file), the relevant Event Viewer log exported via "Save All Events As," and the exact Windows build number from Settings > System > About. That set gives anyone helping you the machine's identity and the fault's history without a single follow-up question.

Check the build number first. Windows 11 updates change the layout of Settings and sometimes relocate troubleshooters, and instructions written for build 22621 can misdescribe a build 26100 screen. The About page names the version (for example 24H2) and the OS build; quote both when you ask for help, because a fix that works on one build can fail on another.

Store the bundle in a folder you can find, and keep the original files rather than screenshots of them. Text and HTML exports are searchable; images are not. The whole gathering process takes about ten minutes and routinely saves an hour of back-and-forth.

FAQ

Does Windows still have a single "fix it" button for all problems?

No. Microsoft retired the old Fix it solution center, and the modern equivalent is the list under Settings > System > Troubleshoot > Other troubleshooters, where each entry targets one fault category. There is no universal repair button, and any third-party tool that claims to be one should be treated with suspicion. The closest thing to a general repair is the System File Checker command, sfc /scannow, run from an elevated Command Prompt.

Why does my troubleshooter close immediately after I click Run?

An instant close usually means the troubleshooter package is corrupted or the diagnostic engine can't start, not that your PC is healthy. Restart the machine and try once more; if it still closes, run the Microsoft Store Apps troubleshooter from the same list, which can repair the underlying framework. On Windows 11 builds where the Settings entry misbehaves, launching the same tool through msdt.exe -id from an elevated Command Prompt frequently bypasses the fault.

Can a troubleshooter fix a blue screen crash?

Only indirectly. The Blue Screen troubleshooter was removed from recent Windows versions, and the modern troubleshooters don't analyze crash dumps. A blue screen records a bugcheck code at the moment of failure, and you find that code in Event Viewer under Windows Logs > System as Event ID 41, or in the memory dump file at C:\Windows\Minidump. Use the code to identify the failing driver, then update or roll back that driver through Device Manager.

Is the Windows Update troubleshooter safe to run repeatedly?

Running it once or twice is safe, but repeated runs mostly repeat the same service restarts and cache clears without new effect. If two runs don't resolve an update failure, switch to the manual reset: stop the Windows Update and BITS services, rename the SoftwareDistribution folder, restart both services, and retry the update. That procedure reaches components the automated tool leaves alone, and Microsoft documents it as the escalation path.

Do these troubleshooters work the same on Windows 10 and Windows 11?

The engines are shared, so results match, but the launchers differ: Windows 11 moved the list into Settings under System > Troubleshoot > Other troubleshooters, while Windows 10 keeps it in Control Panel under System and Security > Troubleshooting. A few individual tools were retired in Windows 11, including the Blue Screen and Speech troubleshooters. The msdt.exe command identifiers work on both versions where the packages remain installed.

How long should a troubleshooter take before I give up on it?

Most built-in troubleshooters finish within one to three minutes; the Windows Update tool occasionally runs five. If one sits on the same progress step for more than ten minutes, cancel it, restart the PC, and try a different diagnostic path rather than waiting longer. A hang that reproduces after the restart points to a service the tool depends on, and that service state is visible in Event Viewer or under Services in Administrative Tools.