powercfg /batteryreport is the most useful built-in tool on Windows for diagnosing laptop battery health and runtime. This technical guide shows how to generate the report, interpret every key section, run quick calculations (health %, average power draw, standby drain), and decide what to do next—calibration, configuration, or replacement.
Generate the report
- Open PowerShell (Admin) or Command Prompt (Admin).
- Run:
powercfg /batteryreport - Windows writes an HTML file and prints its path (e.g.,
C:\Users\you\battery-report.html). Open it in a browser.
Tip: To put it on your desktop with a specific name:
powercfg /batteryreport /output "%USERPROFILE%\Desktop\battery-report.html"
Report anatomy (what each section means)
1) Installed batteries
- Design capacity: The original capacity when new (e.g., 60,000 mWh).
- Full charge capacity: What your pack can currently hold at 100% (e.g., 38,500 mWh).
- Cycle count: Charge/discharge cycles reported by the controller (can be blank on some models).
- Chemistry: Li-Ion, Li-Po, etc.
Health formula: Health % = FullChargeCapacity / DesignCapacity × 100%
2) Recent usage
Chronological log of active time, charging state, and remaining capacity. Useful for spotting abnormal drain and verifying that “Connected standby” isn’t leaking too fast.
3) Battery usage (graph/table)
Daily energy consumption bars. Spikes indicate heavy sessions or background tasks running while the lid is closed.
4) Usage history (AC vs. battery)
Shows how often the machine ran on mains vs. battery. Helpful when deciding if charge caps make sense for docked users.
5) Battery capacity history
Trend of Full charge capacity over time. A smooth, gradual decline is normal; sudden drops suggest calibration or hardware issues.
6) Battery life estimates
- At full charge: Estimated runtime using today’s reduced capacity.
- At design capacity: What you might get if the pack were new; useful as a baseline.
Worked example (with real calculations)
The following is a fictional sample to demonstrate how to read and compute from the report.
INSTALLED BATTERIES
-----------------------------------
BATTERY 1
NAME : LNV-ABC123
MANUFACTURER : SMP
CHEMISTRY : Li-Ion
DESIGN CAPACITY : 60,000 mWh
FULL CHARGE CAPACITY : 38,500 mWh
CYCLE COUNT : 472
RECENT USAGE
-----------------------------------
START TIME STATE SOURCE CAPACITY REMAINING
2025-09-20 09:12 Active Battery 100 % 38,500 mWh
2025-09-20 10:22 Active Battery 72 % 27,700 mWh
2025-09-20 11:02 Active Battery 53 % 20,500 mWh
2025-09-20 11:05 Connected standby Battery 50 % 19,300 mWh
2025-09-20 14:05 Connected standby Battery 45 % 17,300 mWh
2025-09-20 14:10 Active AC 45 % 17,300 mWh
BATTERY CAPACITY HISTORY
-----------------------------------
DATE FULL CHARGE CAPACITY
2025-06-01 41,200 mWh
2025-07-01 40,300 mWh
2025-08-01 39,400 mWh
2025-09-01 38,700 mWh
2025-09-20 38,500 mWh
BATTERY LIFE ESTIMATES
-----------------------------------
AT FULL CHARGE : 4:03:00
AT DESIGN CAPACITY : 6:19:00
Calculations
- Health % = 38,500 ÷ 60,000 × 100% ≈ 64.2% (moderate wear).
- Average active power draw (09:12→10:22): used 10,800 mWh in 70 min → 10.8 Wh ÷ (70/60 h) ≈ 9.26 W.
- Average active power draw (10:22→11:02): used 7,200 mWh in 40 min → 7.2 Wh ÷ (40/60 h) = 10.8 W.
- Standby drain (11:05→14:05): used 2,000 mWh in 3 h → 2 Wh ÷ 3 h ≈ 0.67 W (reasonable for connected standby).
- Runtime cross-check: 38.5 Wh ÷ ~9.5 W ≈ ~4 h (matches the report’s 4:03 estimate).
What it means
- At ~64% health and ~472 cycles, expect visibly shorter runtime; consider replacement if mobile use is important.
- Standby drain is acceptable; if yours is >1 W consistently, audit background tasks and modern standby settings.
- Capacity history declines smoothly—typical aging. Sudden capacity cliffs may indicate a gauge issue or cell imbalance.
Interpreting results & thresholds (rules of thumb)
- >90%: Like-new. No action needed.
- 80–90%: Normal early wear. Monitor trends.
- 70–80%: Noticeable runtime loss. Consider charge caps for longevity.
- <70%: Heavy wear. Plan for replacement if you rely on battery.
Note: Cycle count is informative but not definitive. Thermal history, depth of discharge, and storage habits also affect aging.
Next steps: calibrate, configure, or replace
1) Calibrate when the percentage is “wrong”
If your gauge jumps around or sticks, perform a controlled calibration:
- Temporarily disable any charge caps (if your OEM tool supports them).
- Charge to 100% → use the machine to a low level (do not hard-drain to 0) → recharge to 100% without interruption.
- Regenerate the battery report and re-check capacity.
Calibration fixes the reading, not true capacity loss.
2) Reduce high-SoC dwell (for docked users)
- If your OEM utility supports it, set charge thresholds (e.g., start 60%, stop 80–90%).
- Keep the machine cool; heat accelerates aging more than almost anything else.
3) Replace when health is low and runtime matters
- Confirm the exact model / FRU before buying a pack.
- After replacement, run a fresh battery report to establish a new baseline.
Copy-and-keep workflows (2–5 minutes)
A) 5-minute health snapshot
- Run
powercfg /batteryreport, open the HTML. - Record Design, Full, and Health %.
- Scan Recent usage for odd drain and Capacity history for sudden drops.
B) Docked user setup
- Enable OEM charge caps (if available): e.g., start 60%, stop 80–85%.
- Schedule firmware/driver updates in a maintenance window.
- Re-run the report monthly to track wear.
C) Standby drain audit
- Close apps, sleep the device for 2–3 hours.
- Compare capacity before/after; >1% per hour suggests background activity to investigate.
FAQ
Why is Cycle Count blank?
Some batteries/firmware don’t expose it to Windows. Capacity trends are still valid for judging health.
My report is missing data or shows odd characters.
Re-run the command as Admin, ensure the default browser can open local HTML, and check regional/encoding settings if needed.
Should I always cap at 80–90%?
Only if you spend most days on AC power. Mobile users should prioritize runtime and charge as needed.
How do I compare two reports?
Place them side-by-side and compare Full charge capacity and Battery usage for like-for-like workloads. A small decline month-to-month is normal.
Is a sudden capacity drop always bad hardware?
Not always—try calibration first. If the drop persists, run OEM diagnostics and consider service.
Admin extras & related commands
:: Battery report to a specific path
powercfg /batteryreport /output "%USERPROFILE%\Desktop\battery-report.html"
:: Energy diagnostics (10-minute trace; generates energy-report.html)
powercfg /energy
:: Sleep/Modern Standby analysis (sleepstudy-report.html)
powercfg /sleepstudy
Note: /energy and /sleepstudy are excellent for tracking phantom drain and devices that refuse to idle.
Recommended battery purchase
When the report shows heavy wear and runtime matters, replacing the pack is the most impactful fix. Browse compatible models here: