How to Use the powercfg Energy Report to Find Battery Drains

What the energy report shows (and what it cannot)

The energy report is a snapshot, not a continuous monitor. During the trace powercfg records power management events, device states and CPU usage, then sorts the findings into three groups: Errors (red), Warnings (yellow) and Informational (blue). Only the red and yellow groups matter for battery life; the rest is context such as platform capabilities and the active power plan. Because the trace lasts just 60 seconds by default, a drain that only appears later — during sleep, for example — may not show up at all.

That limitation has a workaround: the /duration switch stretches the observation, and the companion command powercfg /batteryreport covers the long-term picture with capacity history and per-day usage. The two reports complement each other: /energy explains what is consuming power right now, /batteryreport shows how much runtime you have lost over months. Neither report changes any settings, so both are safe to run at any time.

• USB Suspend — a USB device (often a webcam, dock or mouse receiver) never entering selective suspend
• Platform Timer — high-resolution timer requests, usually from audio or a browser, keeping CPU wakeups high
• Processor Power Management — a driver or app preventing cores from parking or dropping to low frequency
• Power Policy — long display and sleep timeouts, or a High performance plan eating battery at idle
• Device Power State — a GPU, Wi-Fi adapter or drive stuck in D0 instead of a lower-power state
• High CPU Utilisation — a specific process burning CPU during the trace: TiWorker, antivirus, a browser tab

How to run the report and read it

Open Start, type cmd, right-click Command Prompt and choose Run as administrator. The report is created in the folder the prompt is open in, so switch somewhere readable first — for example cd %USERPROFILE%\Desktop. Then run powercfg /energy, wait about a minute for the trace to finish, and open the generated energy-report.html by double-clicking it: it loads in your default browser. For a longer observation window use powercfg /energy /duration 120 — a few minutes is enough to catch intermittent drains.

In the browser, read top to bottom: the Error count appears at the top of the summary, and the title line of each finding names the offending device, driver or process. Cross-check cryptic driver names against Device Manager to find out which hardware they belong to. Note the findings before changing anything — the report keeps no history, and each new run overwrites energy-report.html in the same folder.

Turning findings into battery hours

Fix the errors first, one change at a time, then re-run the trace to confirm the finding disappeared. USB devices that never suspend usually mean outdated chipset or vendor drivers, so update those; a GPU stuck in D0 often comes down to a browser or hardware-accelerated app running in the background. If a specific process shows high CPU, close it, disable its autostart or update it — TiWorker is Windows Update doing work and settles by itself. Also check Settings → System → Power & battery and switch Power mode to Best power efficiency when running on battery.

Repeat the report after every meaningful change, and run powercfg /batteryreport once a season to compare Full Charge Capacity against Design Capacity — a big gap is a worn battery, not a software problem. A cleanup tool such as Kleaner PRO helps from the other end: trimming startup programs and background apps removes the CPU wake-ups that keep the system from ever truly idling.

Questions and Answers

Read next

All articles · FAQ