The Battery life estimates section near the bottom of a Windows battery report predicts runtime from battery drains the computer has already recorded. It can help explain whether recent use implied two hours, five hours or another approximate runtime, but it does not promise how long the next charge will last.
If you need the complete report layout first, start with our parent guide to reading a Windows battery report. This page focuses only on the estimates table so it can answer each column without duplicating the broader guide.
What “based on observed drains” means
Microsoft describes the battery report as including a battery-life estimate based on the PC's actual history. In practical terms, Windows looks at recorded battery discharge behavior and projects how long a full battery would last under comparable demand.
The projection therefore reflects a mixture of the workloads in the recorded period. Screen brightness, video calls, browser tabs, gaming, CPU and GPU activity, Wi-Fi, Bluetooth, background tasks, power mode, external devices and temperature can all change power demand. A report generated after light office work may estimate much longer runtime than one dominated by gaming or video rendering.
This is why the heading says estimates. The table is historical evidence translated into a projection, not a laboratory battery benchmark.
Where to find the Battery life estimates table
- Open Command Prompt or Windows Terminal as administrator.
- Run
powercfg /batteryreport /output "%USERPROFILE%\Desktop\battery-report.html". - Open battery-report.html from the desktop.
- Scroll near the bottom to Battery life estimates.
If the command fails, the file is missing or the report opens blank, follow our Windows battery report troubleshooting guide before interpreting the table.
How to read every column
The exact layout can vary by Windows version and supported sleep model, but a typical table groups runtime under At full charge and At design capacity, with separate Active and Connected Standby values.
| Column | What it represents | Best use |
|---|---|---|
| Period | The date or date range from which Windows summarized observed drains. | Compare similar weeks or periods, not isolated numbers. |
| At full charge — Active | Projected active-use runtime at the battery's currently reported full-charge capacity. | Closest table value for current active runtime under a comparable workload. |
| At full charge — Connected Standby | Projected Modern Standby duration at current full-charge capacity, when that data is supported. | Context for standby behavior, not normal screen-on runtime. |
| At design capacity — Active | Projected active runtime if the same type of demand were applied to the original design capacity. | Shows the runtime effect associated with lost reported capacity. |
| At design capacity — Connected Standby | Projected standby duration using design capacity. | A reference comparison; it is not a promise about the current battery. |
Active and Connected Standby are different power states, so do not compare their hour values as if they describe the same workload. If the labels Suspended or Connected Standby are confusing, see our dedicated battery-report power-state guide.
At full charge versus At design capacity
Design Capacity is the original reference capacity reported for the battery. Full Charge Capacity is the maximum energy the system currently estimates the battery can hold. Because batteries wear, full-charge capacity commonly becomes lower than design capacity.
Suppose a battery reports 50,000 mWh design capacity and 42,500 mWh full-charge capacity. Its reported capacity ratio is 85%. Under the same observed power demand, the design-capacity runtime projection would normally be higher because it assumes more stored energy.
Full Charge Capacity ÷ Design Capacity × 100. Our battery health percentage guide explains that calculation and its limits.If the full-charge and design-capacity estimates are almost identical, check whether the reported capacities are also close. Some battery controllers may report limited or unusual capacity data, so interpret the numbers together rather than treating one column as authoritative.
What “Current estimate … since OS install” means
The final line may read Current estimate of battery life based on all observed drains since OS install. It combines usable drain history collected during the current Windows installation into one long-term projection.
“Since OS install” does not necessarily mean since the laptop was manufactured or since the battery was installed. Reinstalling or resetting Windows can start a new history period, while a battery replacement may leave earlier operating-system history in the report. Check the Installed batteries and capacity-history sections before assuming the final line describes one unchanged battery.
The aggregate can smooth out one unusual day, but it can also blend very different workloads. A recent, controlled real-world test is more useful when you want to predict today's runtime for a specific task.
Why Battery life estimates are blank or show dashes
A dash usually means Windows did not have enough usable information to calculate that value for the period or power state. It does not automatically mean the battery is defective or the entire report failed.
- The laptop has spent little time running on battery.
- The recorded discharge sessions were too short or incomplete.
- The current Windows installation is new or was recently reset.
- The battery, firmware or controller did not expose all expected data.
- The computer does not use the Connected Standby state shown by that column.
- A battery replacement or reporting change interrupted comparable history.
Use the laptop normally on battery for several meaningful sessions, then generate a fresh report. Also confirm that Recent usage and Battery usage contain data. If several sections are empty, troubleshoot report generation and firmware reporting rather than trying to fill the estimate manually.
Why the estimate looks too high or too low
The recorded workload was unusual
A gaming session, update, video export or high-brightness workload can pull the estimate down. A long idle or very light reading session can push it up. Neither necessarily represents your everyday use.
The report mixed different workloads
A weekly period can contain light browsing, meetings and demanding applications. The resulting projection summarizes observed drains rather than predicting one named activity.
The battery capacity estimate changed
Full-charge capacity can move after additional charge cycles, firmware updates, calibration changes or a battery replacement. Review Battery capacity history for a trend instead of relying on one value.
Standby and active use were confused
Connected Standby duration is not screen-on runtime. For unexpected sleep drain on a Modern Standby PC, use a Windows SleepStudy report to inspect specific sessions, low-power residency and recurring active components.
How to compare the estimate with real battery life
- Charge to a known level and unplug the laptop.
- Choose one normal, repeatable workload such as web browsing and document work.
- Keep brightness, power mode, Wi-Fi and attached devices consistent.
- Record the start time, starting percentage, end time and ending percentage.
- Repeat on another day under similar conditions.
- Generate a fresh battery report and compare the Active estimate with the measured pattern.
Do not run a deep-discharge test simply to prove the report. A partial, repeatable test is safer and usually more useful. Microsoft recommends avoiding frequent deep discharges and excessive heat as part of normal lithium-ion battery care.
If actual runtime is consistently unacceptable, combine the result with capacity health, charging reliability, physical condition and the laptop battery replacement decision guide.
What this table can and cannot tell you
| It can help with | It cannot prove |
|---|---|
| Approximate runtime implied by past drains | Guaranteed runtime for the next charge |
| Comparing current-capacity and design-capacity projections | The exact chemical condition of battery cells |
| Spotting periods with very different observed demand | Which app or component caused every drain |
| Adding usage context to capacity data | That a battery is physically safe |
Frequently asked questions
What are Battery life estimates in a Windows battery report?
They are workload-based runtime projections derived from battery drains Windows has observed. They are not a guaranteed number of hours for the next charge.
What does based on observed drains mean?
Windows uses recorded discharge behavior from real system use. Workload, brightness, radios, background activity, power mode and capacity can all influence the projection.
What is the difference between At full charge and At design capacity?
At full charge uses the battery's currently reported full-charge capacity. At design capacity projects comparable demand using the original reference capacity. A worn battery will usually show a longer design-capacity estimate.
What does Since OS install mean in the battery report?
It is an aggregate based on relevant drains recorded during the current Windows installation. It does not necessarily cover the physical lifetime of the battery or laptop.
Why are Battery life estimates blank or shown as dashes?
Windows may not have enough usable history for that period or power state. Collect several normal battery sessions and confirm that the other battery-report sections contain data.
Why is the estimate higher or lower than my real runtime?
The estimate reflects past workloads. Actual runtime changes with screen brightness, apps, CPU and GPU load, connectivity, peripherals, temperature, power mode and background activity.
Can Battery life estimates diagnose battery health?
No. Use Design Capacity, Full Charge Capacity and capacity history for reported wear. Estimates add usage context but cannot inspect cells, certify safety or prove a hardware fault.
How we verified this guide
Battery Health Lab checked the report command, available options and the purpose of battery-life history against Microsoft's Powercfg batteryreport documentation. Microsoft's energy-efficiency guidance describes the report as including power states, battery drains, capacity history and a battery-life estimate based on the PC's actual history.
Capacity definitions and limitations were cross-checked with Microsoft's battery APIs and battery-care guidance. The example values on this page are illustrative and do not diagnose a specific laptop.
Bottom line
Use At full charge — Active as a workload-dependent projection for the battery's current reported capacity. Use At design capacity only as a reference showing what more original capacity could imply under comparable demand. Check several periods, separate Active from Connected Standby, and compare the report with repeatable real use before making a repair or replacement decision.
Next, return to the complete Windows battery report guide or use the Battery Health Lab checker to extract reported capacity values privately in your browser.