You type powercfg /batteryreport into a terminal, hit Enter, and… nothing. No file appears. Or a file appears but it’s empty. Or you get an error about permissions or an “unable to perform operation” message. On Windows 11 24H2, this handy diagnostic command trips over a handful of new gotchas that didn’t exist on older builds.

The battery report is the single most useful battery diagnostic Windows offers — it shows design capacity, full charge capacity, cycle count, and weeks of usage history. Getting it working is worth ten minutes of your time, and the fix is usually embarrassingly simple. Even if you’ve never opened a terminal as administrator before, the steps below walk through everything click by click, so don’t let the command-line nature of the tool put you off.

Why this happens

  • The terminal isn’t elevated. powercfg /batteryreport needs administrator rights to read the battery telemetry store; without them it silently fails or errors out.
  • Windows can’t write to the output path. Long usernames, OneDrive-redirected profile folders, and controlled folder access can all block the default save location.
  • The Diagnostic Policy Service is stuck. This background service feeds data to powercfg; after the 24H2 update it sometimes hangs and serves nothing.
  • The battery driver isn’t reporting. If the ACPI battery driver is broken, there is no telemetry for the report to include, so it comes out blank.
  • Corrupt power telemetry store. The underlying energy estimation database can corrupt during a major update, leaving powercfg with nothing to read.
  • Controlled Folder Access is blocking the write. Windows Security’s ransomware protection silently blocks unfamiliar programs — including powercfg — from writing HTML files to protected folders.
  • You’re looking in the wrong folder. The command succeeds but saves to C:\Windows\System32 or your user profile, and the “missing” report was never actually missing.

How to fix it

Work through these in order. Fix 1 and Fix 2 resolve the overwhelming majority of cases.

Fix 1: Run it elevated with an explicit output path

Nine times out of ten, this single command variation fixes everything.

  1. Press Win + X and choose Terminal (Admin) — not the regular Terminal.
  2. Run: powercfg /batteryreport /output "C:\battery-report.html"
  3. You should see “Battery life report saved to file path C:\battery-report.html.”
  4. Open that exact path in your browser. Using C:\ avoids every profile-folder and OneDrive permission quirk at once. If you want to master the report’s contents afterward, our guide to generating and reading battery reports breaks down each section.

Fix 2: Check where the file actually went

Before assuming failure, verify the file isn’t sitting somewhere unexpected.

  1. Open File Explorer and check C:\Users\YourName\ for battery-report.html — the default location.
  2. Also check C:\Windows\System32\ if you ran the command from an elevated prompt that defaulted there.
  3. Use File Explorer search for battery-report.html across C:\ to be thorough.
  4. If you find an old one, delete it and re-run with the explicit path from Fix 1 so you always know where the fresh report lands.

Fix 3: Restart the Diagnostic Policy Service

This service collects the telemetry that powercfg reads; restarting it unclogs the pipeline.

  1. Press Win + R, type services.msc, and press Enter.
  2. Find Diagnostic Policy Service, right-click it, and choose Restart.
  3. Also restart Diagnostic Service Host and Diagnostic System Host while you’re there.
  4. Set all three to Automatic startup type if they aren’t already, then re-run the battery report command.

Fix 4: Reinstall the ACPI battery driver

No driver data means no report data — a blank report usually traces back here.

  1. Open Device Manager (Win + X), expand Batteries.
  2. Uninstall Microsoft ACPI-Compliant Control Method Battery and any duplicate.
  3. Shut down fully, wait ten seconds, and boot so Windows reinstalls the driver.
  4. Wait five minutes for telemetry to accumulate, then run powercfg /batteryreport /output "C:\battery-report.html" again.

Fix 5: Allow powercfg through Controlled Folder Access

Windows Security can silently eat the output file, making it look like the command failed.

  1. Open Windows Security > Virus & threat protection > Ransomware protection.
  2. If Controlled folder access is on, click Allow an app through Controlled folder access > Add an allowed app > Recently blocked apps.
  3. Look for anything powercfg-related in the blocked list and allow it — or temporarily toggle Controlled folder access off, generate the report, and turn it back on.
  4. Re-run the command and confirm the file appears.

Fix 6: Repair the power telemetry store

When the underlying energy database is corrupt, powercfg has nothing to report on.

  1. In an elevated Terminal, run sfc /scannow and let it complete — this repairs protected system files including power components.
  2. Then run DISM /Online /Cleanup-Image /RestoreHealth to fix the component store SFC depends on.
  3. Restart the laptop and run the battery report command once more.
  4. If the report now generates but shows odd numbers, give it 24 hours of normal use — the telemetry store rebuilds its history gradually. You can sanity-check the results against our battery health checking guide .

Fix 7: Reset power plans to defaults

A mangled power scheme can break the reporting pipeline in rare cases.

  1. In an elevated Terminal, run powercfg -restoredefaultschemes to rebuild all power plans from scratch.
  2. Restart the laptop.
  3. Run powercfg /batteryreport /output "C:\battery-report.html" one final time.
  4. If it still fails after all seven fixes, run powercfg /energy instead — it performs a live 60-second trace and often succeeds where the historical report fails, giving you usable diagnostic data through a different path. Save its energy-report.html from the same folder and review the errors section, which flags the specific processes and devices wasting power.

Closing

The battery report command itself is rock solid on 24H2 — it just needs admin rights, a writable path, and healthy driver and service plumbing underneath. Once you’ve generated that first good report, save the command somewhere handy; you’ll want it again the next time a battery question comes up.

Frequently asked questions

Why does powercfg /batteryreport do nothing on 24H2?
Most often it’s running without administrator rights, or Windows can’t write to the default output folder. Sometimes the battery data service itself is stuck after the 24H2 update. All three are fixable in minutes with the steps below — the command itself works fine on 24H2.
Where does the battery report actually get saved?
By default, to your user profile folder: C:\Users\YourName\battery-report.html. Many people run the command successfully but never find the file because they look in System32. Specify a full path like powercfg /batteryreport /output C:\battery-report.html to control exactly where it lands.
The report generates but it's blank or shows no data. Why?
A blank report means Windows couldn’t collect battery telemetry — usually a driver problem or a stuck power service. Reinstalling the ACPI battery driver and restarting the diagnostic policy service typically restores data collection.
Do I need a battery for the report to work?
Yes — powercfg /batteryreport requires a battery to be present and detected. On desktops or laptops running without a battery installed, the command completes but produces an empty report. That’s expected behavior, not an error.