How to Diagnose and Fix Your Windows PC Without Memorising a Single Command

Last updated: March 2026

Your PC is acting up. Maybe it lost power unexpectedly. Maybe the internet is dropping out for no obvious reason. Maybe it's just been running slow for weeks and you've been ignoring it. You know there are commands you could run to diagnose the problem — you've seen people on forums type things like sfc /scannow and netsh winsock reset — but you have no idea what those actually do, whether they're safe to run, or what the output means when it finishes.

So you do what most people do. You open a browser, search for something like "how to check Windows after power outage", and spend twenty minutes piecing together instructions from five different forum posts, none of which fully agree with each other.

There is a better way.

The problem with the Windows command line

The command line is genuinely powerful. Windows has hundreds of built-in diagnostic and repair tools accessible from CMD or PowerShell — tools that can check your disk for errors, scan for corrupted system files, flush your DNS cache, audit startup programs, pull a full hardware inventory, test your internet connection, and much more. Most of these tools don't require any third-party software. They're already on your machine.

The problem isn't that the tools don't exist. The problem is knowing which command to run, understanding what it actually does before you run it, and being confident you're not about to break something. For non-technical users, the command line is a wall. Even for freelancers and small business owners who are reasonably tech-savvy, it's a time sink. You have to look things up every time, the output is rarely explained in plain English, and there's no obvious way to know whether a given command is read-only or whether it's about to modify your system.

That's the gap I built Tom's Command Console to fill.

What Tom's Command Console actually does

Tom's Command Console is a free, portable Windows utility that gives you access to 190 system commands, diagnostic tools, and Google search operators — all organised into 20 categories, all labelled with plain-English descriptions of what they do, and all marked with a risk level before you run anything.

The core idea is simple. Instead of memorising commands or hunting through documentation, you browse a categorised list, click a command to read what it does, and then decide whether to run it. The tool explains what to expect, how long it will take, whether it's read-only or makes changes, and whether it needs Administrator privileges. None of that information is hidden or buried in tooltips. It's the first thing you see.

The app is a single portable EXE. No installer, no dependencies, no setup. Unzip it and run it. It weighs around 500 KB and works on Windows 10 and 11.

Why risk labels matter more than you think

Every command in the app carries one of three risk labels: Safe, Warning, or Advanced.

Safe commands are read-only. They display information, report system state, or run diagnostics without changing anything. You can click Run without worrying. Warning commands may modify system settings — things like flushing DNS cache or resetting network configuration. These ask for confirmation before they execute. Advanced commands make significant system changes, like running a full disk repair or resetting Windows networking stack components. These come with a strong warning before anything happens.

On top of the risk label, every command also shows a type indicator: Read Only or Modifies System. That distinction matters. A lot of people don't realise that running sfc /scannow to check system file integrity is safe and read-ish in practice, while chkdsk /f /r will schedule a disk repair that runs before the next boot. Both are useful commands. They're not the same kind of action.

Nothing runs without you clicking Run. The app never executes commands automatically. Every single command requires a deliberate action on your part. Risk labels and confirmation prompts exist on top of that, not instead of it.

The Quick Fixes that most people actually need

The most useful part of the app for most people isn't the full command library — it's the Quick Fixes category. These are pre-built diagnostic workflows that run multiple checks in a logical sequence, targeted at the most common situations where you'd reach for a command line in the first place.

The "Check PC After Power Outage" workflow is the one that prompted me to build this in the first place. When your machine loses power unexpectedly, the right thing to do is check your disk for file system errors, verify your system files are intact, review recent error logs, and check that Windows updates are current. Those are four separate commands across different categories, and most people either don't run them at all or run them in the wrong order. The Quick Fix handles the sequencing.

"Fix Internet Issues" covers the standard network reset sequence — flushing DNS, releasing and renewing your IP, resetting Winsock, and running a connectivity check — in the order that actually makes sense to try them.

"Full Security Check" runs through a set of diagnostics covering your firewall state, shared folders, active network connections, recently installed programs, and scheduled tasks, so you can spot anything that looks out of place without needing to know where each of those checks lives in the Windows interface.

There are more Quick Fix workflows than those three, but those are the ones that cover the situations most Windows users actually face.

The full command library, by category

Outside of Quick Fixes, the app organises commands into 19 other categories. Diagnostics, Network, Disk, Security, Performance, Hardware Info, Maintenance, Startup & Services, Update & Recovery, Troubleshooting, Advanced, Quick Access, Windows Tools, and Package Manager cover system commands. Then there are five Google Dorks categories — more on those below.

The search box (Ctrl+F from anywhere in the app) lets you find any command instantly across all categories. If you know the name of a command but not which category it's in, you don't need to browse — just search.

The breadth of coverage is one of the things that makes it genuinely useful as a reference tool rather than just a launcher. Hardware Info includes commands to pull your BIOS version, CPU details, RAM configuration, and battery health report. Startup & Services lets you review and manage what launches at boot. The Package Manager category covers winget commands for listing, exporting, and updating installed software — useful for anyone who manages their own machine and wants a clean inventory.

Terminal mode and Administrator handling

By default, command output appears inside the app. For most diagnostics, that's ideal — the output is captured, copyable, and saveable to a text file. But some commands produce live output that benefits from running in a real terminal window. Long operations like sfc /scannow or chkdsk show rolling progress that's easier to read in a visible terminal.

Tick "Show terminal" and the command runs in an external CMD window instead. The app stays open alongside it — use the pin-on-top mode to keep the app visible over the terminal so you can queue the next command without hunting for it.

Administrator handling is automatic. The app detects which commands require elevated privileges and checks the "Run as Admin" box for you. If you're not already running as Administrator, it will offer to restart itself with elevated privileges via UAC. You don't need to remember to right-click and "Run as administrator" before launching the tool.

Tip: If a command returns "Access Denied" and the Run as Admin box wasn't automatically ticked, tick it manually and run again. A small number of commands have privilege requirements that vary by Windows edition or configuration.

The Google Dorks section — a bonus for freelancers and SEO users

The last five categories in the app aren't system commands at all. They're Google Dorks — structured Google search operators that let you run targeted searches beyond what the standard search box offers.

There are five Dorks categories: Operators (the foundational syntax), SEO Research, File Discovery, Security Recon, and OSINT Research. Each dork is an editable search query that launches directly in your browser. You can modify them before running — change the domain, swap the file type, adjust the keyword — without needing to understand the full operator syntax from scratch.

For freelancers doing SEO work or competitive research, the SEO Dorks alone are worth having in a quick-access tool. For anyone doing security checks on their own website or digital footprint, the Security and OSINT categories surface things that are tedious to find through regular search.

It's an unusual addition to a Windows diagnostic tool, but the use case is real. A lot of the people who benefit from quick access to diagnostic commands are the same people who do their own SEO and want a way to run structured searches without rebuilding the query from memory every time.

Privacy and trust — what the app does and doesn't do

Because this tool runs system commands, it's worth being direct about what happens under the hood. The app runs entirely locally. There is no network activity, no analytics, no telemetry, no update checks, and nothing phoning home. The only commands that use the internet are the ones that explicitly say so in their descriptions — things like a network speed test or a winget package query.

Every command is visible before it runs. The app shows you the exact command string in the description panel. You can copy it to your own CMD window and run it there if you prefer. There's no hidden logic, no wrapped scripts with undocumented behaviour. What you see is what runs.

Windows SmartScreen may flag the EXE as unrecognised the first time you run it. This is a false positive that affects all new unsigned software — the app isn't in Microsoft's database yet simply because it's new. You can dismiss the SmartScreen prompt and proceed, or submit the file to Microsoft's false positive portal if you prefer. The full documentation covers this in detail.

Who this tool is actually for

Tom's Command Console is useful in a few different situations. If you're a non-technical Windows user who occasionally needs to troubleshoot your own PC, it removes the need to research commands from scratch every time something goes wrong. You open the app, find the workflow for your situation, read what each step does, and run it.

If you're a freelancer or small business owner managing your own machine — and maybe occasionally helping clients or family members with theirs — it functions as a well-organised reference tool with one-click execution. The time savings compared to looking up commands individually are real.

If you're doing your own SEO or security research and want structured Google operator searches on demand, the Dorks section is a practical shortcut.

What it isn't is a replacement for professional IT support when something is seriously wrong. The commands in the app are the same built-in Windows diagnostic and repair tools you'd use yourself or ask an IT person to run. The app makes them accessible and safe to use — it doesn't add capabilities that weren't there.

How to get it

Tom's Command Console is free, and that's not a trial or a freemium gate. There's no paid version, no registration, and no nag screen. Download the ZIP, unzip it, and run the EXE. It works on Windows 10 and 11 (64-bit).

The full documentation covers every feature, all keyboard shortcuts, the risk level system, and answers to the common questions people hit on first use — including what to do if Windows flags the EXE and what to do if winget commands don't work on your machine.

If you find it useful, the best thing you can do is share it with someone who spends time googling Windows commands. That's exactly who it was built for.

Looking for more free tools? Tom's Command Console is part of a small collection of free Windows utilities I've built. You can find the full list on the Free Tools page.