Command Prompt remains the fastest way to pull your battery’s health data on Windows 11 24H2. One command generates a detailed HTML report; this guide shows you the exact commands, where the file lands, and how to read every section that matters.

No software to install, no settings to hunt — just CMD and two minutes.

This guide is written for 24H2 specifically because that’s where most of the confusion lives: the update changed drivers, renamed power features, and left some users with empty reports. Every command below is tested against 24H2, with the 24H2-specific gotchas called out where they bite. By the end you’ll not only have the report — you’ll know exactly which numbers prove your battery’s condition and which ones you can safely ignore.

Why this happens

  • Settings hides the data: Windows 11 shows battery percentage but never the underlying health numbers. CMD is the only built-in route to them.
  • Silent failures confuse users: Without admin rights, the command appears to do nothing. Knowing the exact elevation requirement avoids the confusion.
  • Default path is unreachable: The report lands in System32 by default, so users think the command failed when the file is just hard to open.
  • 24H2 driver issues: The 24H2 update can leave battery drivers broken, producing empty reports that look like a CMD problem.
  • Misread numbers: Even when the report opens, users don’t know which figures matter. The guide below decodes them.

How to fix it

Work through these in order — run the command correctly, find the file, read it, and act on it.

Fix 1: Open CMD as administrator

Elevation is non-negotiable for this command.

  1. Press Win + S, type cmd.
  2. Right-click Command Prompt and choose Run as administrator.
  3. Click Yes on the UAC prompt.
  4. Confirm the title bar says Administrator: Command Prompt — if not, you’re not elevated.

Fix 2: Run the battery report command

The basic command plus the output redirect you’ll actually use.

  1. In the admin Command Prompt, type powercfg /batteryreport and press Enter.
  2. Look for the success message: Battery life report saved to file path C:\Windows\System32\battery-report.html.
  3. Now run it with a friendly output path: powercfg /batteryreport /output %USERPROFILE%\Desktop\battery-report.html.
  4. You should see the new path in the confirmation message.

Fix 3: Open and navigate the report

Know where the important sections are.

  1. Double-click battery-report.html on your Desktop — it opens in your browser.
  2. Scroll to Installed Batteries: read DESIGN CAPACITY, FULL CHARGE CAPACITY, and CYCLE COUNT.
  3. Check Recent usage (last 3 days) for abnormal drain patterns.
  4. Review Battery capacity history — a table of full-charge capacity over time that reveals the wear trend at a glance.
  5. Our design vs full charge capacity guide decodes these numbers in detail.

Fix 4: Generate a longer history with /duration

The default covers 3 days; a longer window shows trends.

  1. In the admin CMD, run powercfg /batteryreport /duration 14 /output %USERPROFILE%\Desktop\battery-14day.html.
  2. Open the file and check the extended Usage history table.
  3. Look for days where drain was far above your normal pattern — those point to specific events or apps.
  4. Save one of these per quarter to build a wear timeline.

Fix 5: Fix the empty-report problem on 24H2

When the HTML opens blank, the data source is broken — not CMD.

  1. Press Win + X, open Device Manager, expand Batteries.
  2. Right-click Microsoft ACPI-Compliant Control Method Battery and choose Uninstall device. Do the same for Microsoft AC Adapter.
  3. Shut down, unplug for 30 seconds, reconnect, and boot.
  4. Re-run the report command as admin — the tables should now populate.
  5. If the battery category is missing entirely, see our battery not detected guide .

Fix 6: Pair it with the energy report for drain diagnosis

When capacity looks fine but runtime is bad, find the drain.

  1. In the admin Command Prompt, run powercfg /energy.
  2. Wait 60 seconds while Windows observes the system.
  3. Open the generated energy-report.html and read the red Errors section first.
  4. Common findings: USB devices not suspending, display drivers blocking idle, CPU stuck at high frequency.
  5. Fix what’s listed, then re-run after a day of normal use to confirm improvement.

Fix 7: Automate monthly reports with Task Scheduler

Set it once and never think about the command again.

  1. Open Task Scheduler (Win + S, type Task Scheduler).
  2. Create a basic task named Monthly Battery Report, triggered monthly.
  3. Set the action to start powercfg.exe with arguments /batteryreport /output %USERPROFILE%\Documents\battery-monthly.html.
  4. Tick Run with highest privileges on the task’s General tab.
  5. You’ll accumulate a hands-free wear history. For official command documentation, see the Microsoft Windows support hub .

Fix 8: Verify the report data with WMIC as a cross-check

When you want a second opinion on the numbers without opening the HTML, WMIC gives a quick readout.

  1. In the admin Command Prompt, run wmic path Win32_Battery get EstimatedChargeRemaining, BatteryStatus.
  2. BatteryStatus 2 means charging; 1 means discharging. Compare the estimated charge with the taskbar icon.
  3. If WMIC and the taskbar disagree wildly, the shell’s battery indicator is misreading — the report’s numbers are the authoritative ones.
  4. For a deeper hardware check, compare against your manufacturer’s own battery app reading (Vantage, MyASUS, Dell Power Manager), which talks to the controller directly.

Closing

CMD gives you the battery truth in under a minute: run it elevated, point the output somewhere sensible, and read the Installed Batteries section. Do it quarterly and you’ll spot wear, driver glitches, and drain problems early — long before they become expensive or leave you stranded without warning. For a second opinion on the numbers, compare the report’s full charge capacity against what HWiNFO or BatteryInfoView shows — if all three agree, you can trust the reading completely.

Frequently asked questions

What is the CMD command for the battery report?
Open Command Prompt as administrator and run powercfg /batteryreport. Add /output followed by a path (e.g. powercfg /batteryreport /output %USERPROFILE%\battery.html) to save it somewhere easy to open. The report is an HTML file you view in your browser.
Why does CMD say the battery report command failed?
Almost always because Command Prompt wasn’t run as administrator. Right-click Command Prompt and choose Run as administrator, then retry. If it still fails, the battery drivers may be broken — reinstall them in Device Manager.
Can I see battery health directly in CMD without opening the HTML?
Not fully, but you can get a quick summary. The HTML report is the complete view. For a fast check, the report’s Installed Batteries section is what matters — design capacity vs. full charge capacity — and it takes seconds to read once the file is open.
Does this work the same on Windows 11 24H2 as older versions?
Yes, the command is identical. The only 24H2-specific wrinkle is that the update sometimes breaks the battery drivers, producing an empty report. Reinstalling the drivers fixes it. The report format itself is unchanged.