Windows users often reach for the Settings app first when troubleshooting. But for stubborn issues—battery that drains faster than it should, Wi-Fi that drops intermittently, or applications that crash without warning—Settings frequently shows only a sanitized snapshot, not the underlying evidence. Five built-in command-line tools, highlighted this week in a MakeUseOf guide, expose the details that Settings omits: a battery’s actual capacity history, protected system file integrity, an inventory of every installed driver, a timeline of wireless connection events, and the logical health of your NTFS volumes. You don’t need to be a power user to run them, and the insight they provide can turn a vague complaint into a specific, fixable problem.
What Actually Changed? Nothing—and That’s the Point
None of these commands are new. They’ve been part of Windows for years, some dating back to the NT era. The news isn’t a fresh feature release; it’s a reminder that the command line remains the place where Windows keeps its most detailed diagnostics. Microsoft’s Settings app gets sleeker with every update, but it’s designed for control, not deep investigation. It shows you the current battery percentage, but not how much capacity the battery has lost since you bought the laptop. It tells you a device is “working properly” without revealing that its driver was built in 2016. For problems that develop gradually or flare up intermittently, the high-level view isn’t enough.
These five commands—powercfg /batteryreport, sfc /scannow, driverquery, netsh wlan show wlanreport, and chkdsk /scan—fill that gap. They collect evidence rather than just a status, and they’ve been quietly supported in Windows 11 because Microsoft knows that power users, IT pros, and even determined home users still need that level of detail.
What It Means for You
The usefulness of these commands depends on who you are and what problem you’re trying to solve.
Everyday home users will get the most immediate value from powercfg /batteryreport and chkdsk /scan. If your laptop used to last all day but now dies by 2 p.m., the battery report tells you whether the actual capacity has shrunk—and by how much. That can save you from blaming Windows or your apps and let you decide whether it’s time for a battery replacement or a new machine. Similarly, when files start acting glitchy or an update fails, a quick chkdsk /scan can rule out file-system corruption before you waste time reinstalling drivers or apps.
Power users who tinker with hardware or install beta software will lean on driverquery and sfc /scannow. Having a complete list of drivers with dates and signatures helps you spot outdated or mismatched versions that might be destabilizing your system. And sfc with the DISM fallback is the standard first move when Windows itself starts misbehaving—missing DLLs, crashing system dialogs, or failing cumulative updates.
IT professionals have long kept these commands in their mental toolkit. Generating reports via netsh wlan show wlanreport can resolve a user’s “Wi-Fi keeps dropping” complaint by showing that the adapter itself is resetting—not the router. Running driverquery on remote machines (with the right parameters) can streamline an audit. And teaching users to run a battery report before requesting a new laptop turns a subjective “it doesn’t last” into an objective capacity-loss percentage.
In all cases, the commands give you evidence. That’s the difference between guesswork and a targeted repair.
How We Got Here: A Brief History of Windows’ Diagnostic CLI
These tools were born in an era when Windows configuration meant editing .ini files and the Registry. chkdsk goes back to DOS; sfc arrived in Windows 98 as a system-file checker. netsh debuted in Windows 2000, and powercfg matured alongside modern sleep states. Microsoft has wrapped fancier interfaces around most of them—you can scan for disk errors from File Explorer, and Device Manager has its own driver view—but the GUI versions rarely offer the same depth. A battery icon in the system tray can’t tell you that your 60,000-mWh design capacity is now 42,606 mWh. Device Manager won’t spit out a CSV of every driver with digital-signature status.
The Settings app, especially in Windows 11, is intentionally simplified. Microsoft’s design philosophy draws a line between “manage” and “diagnose.” That’s why these commands persist: they live closer to the operating system’s internals and the Component Store, the driver stack, and the wireless service. They were never meant to disappear—they were only meant to be used by people who need them.
What to Do Now: A Practical Guide to Five Essential Commands
Here’s when to use each tool, how to run it, and what to look for in the output.
powercfg /batteryreport: Measure Battery Wear
Run this from Command Prompt (no admin needed) when your laptop’s runtime feels shorter than it used to be. The command generates an HTML file, usually in your user folder. Open it in a browser and find Design Capacity and Full Charge Capacity. The former is what the battery could hold when new; the latter is what it holds now. A simple subtraction: (Design − Full) ÷ Design × 100 = the percentage of capacity you’ve lost. My own battery had dropped from 60,002 mWh to 42,606 mWh—a 29% loss. No wonder Netflix had to end sooner.
Other useful sections include Cycle Count (if reported), Recent Usage, and Battery Capacity History to see the decline over time. But be cautious: if the battery is physically swollen, stop using the laptop immediately and get it serviced. No command can fix that.
sfc /scannow: Check System File Integrity
When Windows features break—apps won’t open, a DLL error appears, or an update fails repeatedly—run sfc /scannow from an elevated Command Prompt or Terminal. It scans protected Windows files and replaces corrupt versions with cached copies from the Component Store.
The result will say one of three things:
- No integrity violations: Your system files are fine.
- Violations found and repaired: Corrupt files were fixed.
- Violations found but couldn’t be repaired: The repair source (local cache) is itself damaged.
If you get that third result, don’t just rerun SFC. Instead, repair the cache with DISM /Online /Cleanup-Image /ScanHealth to check for image corruption, then DISM /Online /Cleanup-Image /RestoreHealth to fix it. By default, the repair pulls fresh files from Windows Update. After that, run sfc /scannow again. This combination resolves most system-file issues without an in-place upgrade.
driverquery: Inventory Every Driver
Device Manager might say “This device is working properly” even when your Bluetooth mouse disconnects or your audio crackles. That message only means Windows can communicate with the hardware—not that the driver is current or bug-free. driverquery lists all installed drivers with names, types, and link dates. Add /v for verbose mode, /si to include digital-signature info, or /fo csv > drivers.csv to export a spreadsheet.
When troubleshooting, use the link date to spot ancient drivers tied to a problematic device. A Wi-Fi driver from 2018 might need an update if you’re seeing drops after waking from sleep. But don’t blindly update everything: some Microsoft-supplied drivers are intentionally old because they’re stable. Correlate the date with the specific symptom, then check Windows Update’s optional updates or your PC manufacturer’s support page for a newer version.
netsh wlan show wlanreport: Reconstruct Wi-Fi Failures
Wi-Fi drops are infuriating because the evidence disappears the moment the connection recovers. The netsh wlan show wlanreport command (run as admin) generates an HTML report, saved to C:\\ProgramData\\Microsoft\\Windows\\WlanReport\\, covering about three days of activity. It includes disconnect events, signal quality graphs, driver events, and session summaries.
Open the report when a failure occurs and look for patterns: Did the adapter reset just before the drop? Does the signal dip at a specific time? Does a driver event align with the disconnection? This can save you from blaming the router if the issue is actually a flaky adapter or a bad driver update. One caution: the report includes SSIDs and network history, so be mindful before sharing screenshots.
chkdsk /scan: Inspect File-System Consistency
When files become unreadable, apps crash while saving, or the system behaves oddly after an improper shutdown, your NTFS volume might have logical errors. Run chkdsk /scan from an admin prompt to perform a read-only check. It looks for file-table corruption and structural inconsistencies without making any changes.
If it reports errors, schedule a repair with chkdsk C: /f. Because the system volume is usually locked, you’ll be asked to schedule the fix for the next reboot. Important: /f only repairs logical file-system issues. It does not test for physical disk failure—bad sectors or a dying SSD need a vendor tool or SMART monitoring. And avoid using /r (which scans for physical bad sectors) routinely; it’s a heavy operation that takes hours and can stress the drive. Reserve it for cases where you suspect surface damage.
Outlook: The CLI’s Staying Power
Microsoft continues to polish Windows 11’s graphical tools, and some diagnostic data—like battery usage over time—is slowly making its way into Settings. But the deep, timestamped logs and raw inventories these commands produce aren’t likely to surface in a consumer-friendly app anytime soon. They remain a bridge between “something’s wrong” and “here’s what to fix.” As long as Windows runs on desktops, laptops, and corporate fleets, these five commands will be worth memorizing.