Windows has a reputation for acting up out of the blue. But before you pay someone to investigate your misbehaving PC, it might be worth giving Windows a chance to explain itself. Its built-in tools can expose storage reliability counters, battery capacity, standby activity, unexpected shutdowns, and system-file corruption.
These tools won’t diagnose everything, but they can help you narrow down a vague issue to something worth investigating. The best part? They’re all simple PowerShell commands you can run on any Windows PC. Run them in PowerShell as administrator.
When file transfers freeze, your SSD is the usual suspect
Wear, temperature, and uncorrected errors, from two PowerShell commands
If your PC keeps stalling while opening files or moving folders, chances are your storage is to blame instead of Windows. Start off with this command to identify your disks and retrieve any reliability concerns:
Get-PhysicalDisk | Select-Object DeviceId, FriendlyName, HealthStatus
Get-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId, Temperature, Wear, PowerOnHours, ReadErrorsUncorrected, WriteErrorsUncorrected
Match DeviceId between the results so you know which drive you’re examining. The command also shows you the current drive temperature in Celsius, which you can compare with the drive manufacturer’s operating specifications rather than guessing whether it’s optimal or not.
That said, the most important metric here is SSD wear. It shows the estimated wear consumed, not life remaining, and 100 means the estimated wear limit has been reached. Uncorrected read and write counters show errors the drive couldn’t correct. If your wear number is anywhere close to 100, it’s time to start backing up files before doing anything else.
Blank results don’t mean the drive is healthy either. Some drives, controllers, and connection paths don’t expose these measurements. Similarly, treat a healthy status reading as the storage provider’s assessment, not concrete proof that your drive is perfect. If your computer keeps freezing or files keep going unreadable on their own, it’s time to start considering an SSD swap.
Your battery is retiring, and Windows has the paperwork
Design capacity vs full charge capacity, in one HTML report
Windows laptops aren’t known for their amazing battery life. But if your battery counter looks more like a countdown than a battery percentage indicator, it’s time to generate a battery report.
powercfg /batteryreport /output "$env:USERPROFILEbattery-report.html"
This command will generate a full battery report as an HTML file you can open in any browser. Under the Installed batteries section, compare the Full charge capacity number with Design capacity. The former is the battery’s current maximum capacity and the latter is its original intended capacity from the factory. A substantial gap here supports battery degradation as an explanation for the shorter runtime, even when Windows tells you your battery is fully charged.
The report also gives you a battery capacity history that tells you whether capacity has declined over time rather than judging one reading in isolation. Battery life estimates reflect recorded usage, so treat them as context, not a promise of how long your laptop will last. This report is the fastest way to separate lost battery capacity from simply using more power.
Modern Standby drained your laptop overnight, and SleepStudy names the culprit
Top Offenders, three days of history, and a catch for older laptops
Windows Modern Standby is nothing short of a nightmare, and it has been for quite some time now. Your laptop might be fully charged when you put it to sleep, but with the magic of Windows Modern Standby, it might be running on fumes when you get back to it the next day. Diagnosing this starts with generating a SleepStudy report with the following command:
powercfg /a
powercfg /sleepstudy /output "$env:USERPROFILEsleepstudy.html"
The first command checks available sleep states. If you see Standby (S0 Low Power Idle), you’ve got modern standby support. SleepStudy isn’t a universal sleep diagnostic for traditional S3-only machines, so this approach will only work on newer Windows laptops.
Open the report and focus on long battery-powered sessions with high drain, then inspect their detailed Top Offenders entries. These identify active components, including devices, networking, and software activity, which can massively help narrow your target for further troubleshooting. The default report covers three days, which can be extended, for example to seven days, by adding /duration 7.
Random restarts leave a paper trail, if you know to read Event 41
Kernel-Power logs, BugCheckCode, and why the timestamp lies
Sudden PC restarts can indicate serious problems with your PC hardware. The best place to start diagnosis in such cases is to pull recent Kernel-Power events directly from the system log:
Get-WinEvent -FilterHashtable @{ LogName="System" ProviderName="Microsoft-Windows-Kernel-Power" Id=41 StartTime=(Get-Date).AddDays(-14) } | Select-Object TimeCreated, Id, Message | Format-List
This command will filter the last two weeks instead of making you scroll through unrelated events. However, Event 41 means Windows detected an unclean shutdown, not necessarily a problem with your hardware. Crashes, power interruptions, and forced shutdowns can all produce it.
Windows records this event at the next startup, so don’t mistake its timestamp for the exact time of failure. Use it to locate the relevant reboot, then inspect nearby events in Event Viewer. A nonzero BugCheckCode in the event’s details can point toward a blue-screen investigation. Zero doesn’t prove a power-supply fault either. As for critical temperatures, Windows may log a warning, so keep an eye out for one while scrolling through the logs.
Before you reinstall Windows, make DISM and SFC earn their keep
ScanHealth, RestoreHealth, and sfc /scannow, in the right order
If Windows itself is the problem, it might be worth checking the component store before you torture yourself with a full reinstall. Start by running a simple DISM command:
DISM.exe /Online /Cleanup-Image /ScanHealth
In this command /Online targets the running Windows installation, while /ScanHealth checks for component-store corruption without repairing it. If it reports repairable corruption, run this:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Once done, follow up to check protected system files:
sfc /scannow
Unlike DISM’s /ScanHealth, SFC attempts repairs as it scans. Its final message distinguishes no detected integrity violations, successful repairs, and corruptions it couldn’t fix, so let verification reach 100% before closing the window. DISM repair normally uses Windows Update, although a separate repair source may be needed when that isn’t available.
Given how often internal Windows components can break, running these commands is also a good routine maintenance practice for any Windows PC. Run them every once in a while to stay on top of any surprise corruptions that might be headed your way.
Windows can’t fix everything, but it can finally explain itself
Save the reports, note the symptoms, and show up with evidence
You don’t have to become a Windows expert to make these commands useful. The goal is to replace guesswork with evidence. A worn battery, suspicious drive counters, excessive standby activity, or random file corruptions are all issues Windows is capable enough to recognize with the right tools.
Just remember that a report is a starting point, not the final verdict. An unexpected shutdown doesn’t automatically mean a bad power supply or thermal issues, and clean system scans don’t explain every freeze. Save your results, note when the symptoms appear, and back up important files. If you still need professional help, you’ll have something far more useful to bring along than “my PC has been acting weird.”