Take the energy report on battery
The analysis watches the machine for sixty seconds and writes an HTML file. Pulled power and idle load make the findings meaningful; on the charger half of them disappear.
powercfg /energy /duration 60
The two built-in reports that name the driver, device or app keeping the machine awake, and what to do with the entries they list.
Run **powercfg /energy** and **/sleepstudy**, open the HTML reports, and act on the top entries: they name the device, driver or application that keeps the CPU or the radio busy.
The analysis watches the machine for sixty seconds and writes an HTML file. Pulled power and idle load make the findings meaningful; on the charger half of them disappear.
powercfg /energy /duration 60
The report files findings in two sections. Errors are real defects such as a device that fails to enter a low power state; warnings are mostly tuning notes and can wait.
C:\Windows\system32\energy-report.html
Sleep study records what happened during standby instead of guessing: sessions, wake sources and the drain per hour. On machines with classic S3 sleep the command refuses with an unsupported message.
powercfg /sleepstudy /output C:\Temp\sleep.html
Design capacity against full charge separates a short runtime caused by a worn cell from one caused by a process. Two different problems with two different fixes.
powercfg /batteryreport /output C:\Temp\battery.html
The wake list shows what is armed. A mouse that twitches in a bag or a network card set to wake on magic packet keeps a laptop out of standby without any visible activity.
powercfg /devicequery wake_armed
Repeat the energy run and compare the error count, then watch the reported drain over one standby session. A change that does not move those numbers did not help.
powercfg /energy /duration 60
The machine uses classic S3 sleep. Use the battery report and the energy report instead.
Sixty seconds on a busy machine hides idle behaviour. Close applications, unplug the charger and run it again.
Keyboard, mouse or network adapter. Disarm them one at a time and check the wake history.
Battery wear, not a process. Compare design capacity with full charge in the battery report.
The analysis commands are read-only. They write an HTML file and nothing else.
After a firmware or driver update, and whenever standby stops working as it used to.
A disarmed wake device is restored with powercfg /deviceenablewake and the same name. The HTML reports are ordinary files you can delete.
Free · no account needed · tracks your progress