4 Windows Commands That Reveal Your PC’s Real Health Before It Fails

🩺 4 Windows Commands That Reveal Your PC’s Real Health

Many people only find out that their hard drive is dying, their SSD is at the end of its life or their laptop battery has already lost half its capacity when the problem is already on screen — blue screens, freezes, battery life cut in half. The good news is that Windows already ships with built-in tools, no third-party software needed, that show these warning signs weeks or even months in advance.

In this guide I’ll show you 4 real commands — two for drives, one for an overall system diagnosis and one for the battery — explaining the exact syntax, what each output means and when to use each one.

🧭 Why Use Built-in Commands Instead of Third-Party Programs

There are dozens of very good hardware monitoring programs — and if you already use one, great: the commands in this post don’t compete with them, they complement them. The advantage of built-in commands is that they need no installation, show no ads, don’t ask for excessive permissions and work on any Windows 10 or 11 with no prior setup.

That’s especially useful in three situations: when you’re working on someone else’s PC and don’t want to install anything extra, when the PC is already slow and you don’t want to burden it with a heavy program running in the background, or when you simply want a quick answer without opening any graphical interface.

If you like working in PowerShell and want to go deeper into what the system reports about your hardware, also see the msconfig myth: commands to check your CPU and memory. Here the focus is more surgical: specific commands that answer one precise question about the health of your drive, the system as a whole or the battery.

🔬 S.M.A.R.T.: the Foundation of It All

Both wmic diskdrive get status and Get-PhysicalDisk rely on a technology called S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology), present in practically every hard drive and SSD made in the last 20 years. The drive internally monitors dozens of its own indicators — reallocated sectors, temperature, power-on hours, read error counts — and exposes a summarized verdict that Windows can read without having to understand every raw metric. That summarized verdict is what the commands in this post show you.

It’s important to understand one real limitation of S.M.A.R.T.: it detects gradual wear very well, but it doesn’t predict 100% of sudden failures (a burned-out electronic component, for example). Even so, data published by large cloud storage providers shows that most drives that fail give some S.M.A.R.T. warning before dying for good — which makes these commands a cheap, fast way to catch the problem early.

💽 wmic diskdrive get status: the Quick Drive Thermometer

wmic (Windows Management Instrumentation Command-line) is a long-standing Windows command-line tool. To check the health of every installed drive, open Command Prompt (it doesn’t need to be as administrator) and type:

The output is short and to the point. If you have two drives (for example, an SSD and a secondary hard drive), you’ll see one line for each, in the order Windows detects them. The possible values are:

• OK — the drive is working normally, with no S.M.A.R.T. warning.
• Pred Fail (short for “Predicted Failure”) — the drive is predicting its own failure soon. It’s the most serious signal this command can give: back up immediately and plan to replace the drive.
• Unknown — Windows couldn’t read the drive’s S.M.A.R.T. status (common with some external USB SSDs whose controller doesn’t pass that information through).

The limitation of wmic diskdrive get status is that it only gives you that one-word verdict — no temperature, no indication of which S.M.A.R.T. attribute triggered the warning, no distinction between hard drive and SSD. For that level of detail, the next command is more complete.

🖥️ Get-PhysicalDisk: the Modern, More Complete Version

Get-PhysicalDisk is a PowerShell cmdlet (part of the Storage module, included by default in every Windows 10 and 11) that does basically the same check as wmic, but with a lot more context in the output. Open PowerShell (no admin needed for the basic query) and just type:

A typical output looks like this:

The field that matters most is HealthStatus, which has four possible values according to Microsoft’s official documentation for the Storage module:

• Healthy — everything normal, the drive is operating as expected.
• Warning — some indicator has started to degrade, but it isn’t critical yet. Worth checking more often.
• Unhealthy — confirmed, significant degradation. Equivalent to wmic’s “Pred Fail”, but with an intermediate level (Warning) that wmic can’t tell apart.
• Unknown — Windows couldn’t determine the state, usually because of a limitation in how the drive is connected.

A practical advantage of PowerShell here is filtering right in the query. To see only drives with problems, for example, the command becomes Get-PhysicalDisk | Where-Object HealthStatus -ne "Healthy" — if the list comes back empty, all is well; if a line appears, that’s the one that needs attention.

⚖️ Comparing the Two Drive Commands

In practice, if you just want a quick yes-or-no answer (“is my drive OK or not?”), wmic still does the job. If you want to understand how serious the problem is before deciding whether to replace the drive, Get-PhysicalDisk is worth the effort of typing a slightly longer command — and it’s the path Microsoft itself is pushing for the future.

If one of your drives shows a warning, also run the 2-minute test that reveals whether your SSD is dying and, for a deeper look, how to use Victoria HDD/SSD.

📋 perfmon /report: the Complete System Check-up

Unlike the previous commands, which focus only on drives, perfmon /report starts the Windows Performance Monitor to collect data about the entire system for about 60 seconds and generate a complete HTML report, with an automatic diagnosis of CPU, memory, disk, network and general configuration.

When you run the command, Windows opens a window saying “Collecting data for 60 seconds…” — during that time it’s best to leave the PC doing something close to normal use (it doesn’t need to sit idle, but it isn’t the ideal moment to open 20 heavy programs at once, because that skews the reading). Once collected, the report opens automatically.

🔍 How to Read the Perfmon Report

The report is split into sections, and the most important one for anyone who just wants a quick verdict is right at the top: Diagnostic Results, with warnings and errors already highlighted, each with a plain-language explanation of what was found — for example, an outdated driver, a service failing to start or a drive close to full capacity. After that come more technical, detailed sections:

• Software Configuration — Windows version, uptime, list of installed services.
• Hardware Configuration — processor model, amount of RAM installed and in use, network information.
• CPU — the processes using the most processing power during the collection.
• Network — active network adapters and traffic statistics.
• Disk — drive response time and free space per volume.
• Memory — physical memory and paging (swap) usage at the time of the collection.

Keep in mind that this report is a snapshot — it reflects what was happening during those specific 60 seconds, not a history over time. If the problem is intermittent (it only freezes now and then, for example), you may need to run the command more than once, at different times, to catch the symptom in the act.

🔋 powercfg /batteryreport: Your Battery’s Real Health

If you use a laptop, this is probably the most valuable command on this list, because it answers a question most users can never answer precisely: “how much of its original capacity has my battery already lost?”. Windows natively keeps a history of battery usage over time — and powercfg /batteryreport turns that history into a complete HTML report.

After running the basic command, go to the folder shown in the message and open battery-report.html with any browser — no special program needed, it’s a regular web page. To skip that manual search, use the combined version from the table above: it saves the file straight to your desktop and opens it in your default browser automatically.

📊 How to Read the Battery Report

The report has several sections, but the two numbers that answer the key question — “how worn is my battery?” — are in the Installed batteries summary at the top and in the Battery capacity history table:

• Design Capacity — the battery’s original factory capacity, measured in mWh (milliwatt-hours).
• Full Charge Capacity — the maximum capacity the battery can hold today, given its current wear.

The math is simple: divide Full Charge Capacity by Design Capacity and multiply by 100 to get the current health percentage. For example, a battery with a Design Capacity of 50,000 mWh and a Full Charge Capacity of 41,000 mWh is at 82% health — in other words, it has already lost 18% of its original capacity.

The report also includes a Recent usage section and a Battery life estimates table comparing estimated runtime across different periods — useful to see whether the drop in battery life was gradual (normal wear) or sudden (possibly a specific defect).

🎯 When to Use Each Command in Practice

And if the drive commands point to corrupted system files rather than a failing drive, the next step is the SFC and DISM repair.

🗓️ A Simple Preventive Check Routine

There’s no need to run these commands every day — that would be overkill and the result doesn’t change from one check to the next in just a few days. A reasonable schedule for most home users:

1. Monthly: wmic diskdrive get status or Get-PhysicalDisk — a quick check that takes less than 10 seconds.
2. Every 2–3 months, or whenever you notice slowness: perfmon /report — to catch any general performance degradation early.
3. Every 3–6 months, if you use a laptop: powercfg /batteryreport — to follow the battery’s wear curve over time, not just a single number.

If you use your PC for work or keep important files without a cloud backup, cut those intervals in half — running a free command costs practically nothing compared to losing files to a drive that had been warning you all along.

👂 Warning Signs No Command Can Detect on Its Own

As useful as these 4 commands are, they don’t replace paying attention to physical and behavioral signs that sometimes appear before any software warning:

• Clicking or grinding noises coming from the case — typical of a mechanical hard drive with a read-head problem, often before any S.M.A.R.T. warning appears.
• A laptop bulging near the battery — a serious physical sign of a degraded lithium-ion battery that requires immediate replacement for safety reasons, regardless of what powercfg shows.
• A burning smell or abnormal overheating — never wait for a command to confirm this; turn the device off and take it for a technical inspection.
• Files getting corrupted for no apparent reason — it can be a sign of a degrading drive even while S.M.A.R.T. still says “OK”, because not every failure is captured by the monitored attributes.

Also remember that a PC that’s healthy in hardware can still be compromised by malicious software running in the background, eating CPU and disk without showing up in any of the reports in this post — see how trojans work and how to protect yourself.

🚧 Limitations: What These Commands DON’T Do

To avoid false expectations, here’s what these 4 commands can’t do:

• They don’t measure component temperatures in real time (CPU, GPU, drive) — for that you need a dedicated sensor monitoring program.
• They don’t run stress tests or performance benchmarks — they show a snapshot of the current state, not maximum capacity under heavy load.
• S.M.A.R.T. (used by the drive commands) doesn’t predict 100% of failures — some kinds of sudden electronic defects give no prior warning.
• powercfg /batteryreport doesn’t replace battery calibration in rare cases of incorrect percentage readings — if the battery shows 100% and shuts off suddenly, the problem may be something else (driver, manufacturer firmware).

📈 When It’s Worth Going Beyond the Built-in Tools

The commands in this post handle one-off diagnostics and routine preventive checks well. But if you want continuous monitoring with real-time temperature graphs, sound alerts when a sensor crosses a limit, or a detailed history of every component over weeks, it’s worth trying a more robust free tool — dedicated hardware monitoring programs are the natural next step once you’ve mastered the built-in commands in this post.

For drives specifically, a bench tool like the one in the Victoria HDD/SSD guide goes attribute by attribute and even tests the surface of the disk.

📖 Quick Glossary

• S.M.A.R.T.: a technology built into hard drives and SSDs that internally monitors wear indicators and exposes a health verdict the operating system can read.
• wmic: Windows Management Instrumentation Command-line, an older Windows command-line tool used to query system information.
• Cmdlet: the name for PowerShell’s built-in commands (like Get-PhysicalDisk), in Verb-Noun format.
• HealthStatus: a property returned by Get-PhysicalDisk indicating the drive’s health (Healthy, Warning, Unhealthy or Unknown).
• Perfmon: short for Performance Monitor, Windows’ built-in tool for collecting system performance metrics.
• mWh (milliwatt-hour): the unit Windows uses to measure the energy a laptop battery can store.
• Design Capacity: a battery’s original factory capacity, before any wear from use.
• Full Charge Capacity: the real maximum capacity the battery can hold today, reflecting accumulated wear.

FAQ