Windows 11 Battery Health Assessment Using PowerCFG
In this lab, I investigated the battery health and power usage of a Windows 11 laptop using the built-in Windows PowerCFG utility.
The purpose of the lab was not simply to generate a battery report, but to use the information contained within the report to perform a basic battery health assessment.
The investigation examined:
Battery design capacity
Current full-charge capacity
Battery chemistry
Battery usage
AC and battery usage history
Historical battery capacity
Estimated battery life
Inconsistencies within the reported battery data
No third-party diagnostic software was used.
Lab Scenario
A Windows 11 laptop has been experiencing battery-related concerns.
As part of an IT support investigation, I wanted to establish whether the Windows battery data showed evidence of battery degradation.
Rather than immediately recommending battery replacement, I used Windows' built-in diagnostic capabilities to collect evidence and analyse the battery's condition.
The system used for this lab was a:
PC Specialist UltraNote V15
Lab Objectives
The objectives of this lab were to:
Generate a Windows battery report.
Identify the installed battery.
Record the battery's design capacity.
Record the current full-charge capacity.
Compare the two capacity figures.
Examine recent battery usage.
Examine historical battery usage.
Analyse battery capacity history.
Review Windows' estimated battery life.
Determine whether the collected evidence indicates battery degradation.
Produce an IT support assessment based on the findings.
Lab Environment
Item | Details |
Operating System | Windows 11 |
Laptop | PC Specialist UltraNote V15 |
Battery Chemistry | Li-ion |
Diagnostic Tool | Windows PowerCFG |
Third-Party Software | None |
Report Format | HTML |
Before generating the report, I checked the laptop's current battery status.
The laptop was showing:
100% battery
This provided the starting state for the investigation.

I opened Windows PowerShell with administrative privileges and used the following command:
powercfg /batteryreportWindows successfully generated an HTML battery report.

Figure 2 – PowerShell used for the battery investigation.

Figure 3 – Windows successfully generating the battery report.
The generated HTML report was opened in a web browser for analysis.
The report identified the system as:
PC Specialist UltraNote V15
The report was generated on:
8 October 2026 at 16:51:19
Connected Standby was reported as:
Not supported

Figure 4 – Generated Windows battery report.
The Installed Batteries section was examined.
The following information was recorded:
Property | Result |
Battery | Battery 1 |
Name | BAT |
Manufacturer | Notebook |
Serial Number | 0001 |
Chemistry | Li-ion |
Design Capacity | 43,070 mWh |
Full Charge Capacity | 44,063 mWh |
Cycle Count | Not reported |
The two most important figures for this part of the investigation were:
Design Capacity: 43,070 mWh
Full Charge Capacity: 44,063 mWh
The current full-charge capacity was compared with the original design capacity.
The calculation was:
Full Charge Capacity ÷ Design Capacity × 100Therefore:
44,063 ÷ 43,070 × 100Result:
Approximately 102.3%
Based purely on the current figures reported by Windows, the battery is reporting slightly more capacity than its nominal design capacity.
This does not mean that the physical battery has somehow gained capacity.
Battery capacity figures are reported by the battery and its associated hardware/firmware, and the values should therefore be treated as diagnostic measurements rather than laboratory measurements.
Finding
Current reported capacity does not indicate obvious battery degradation.

The Recent Usage section was examined to determine how the battery had been behaving during recent periods of use.
The report showed the system operating on battery power at various points, including a period where the battery level changed from approximately:
100% → 74%
and subsequently:
74% → 73% → 38%
The report also recorded further battery activity on the following day.

Figure 6 – Recent battery and AC activity recorded by Windows.
The report demonstrates significant battery consumption during some usage periods.
However, the report does not provide enough information by itself to determine whether this consumption is abnormal.
Battery drain can vary significantly depending on:
CPU workload
Display brightness
Applications running
Network activity
Windows updates
Background processes
Virtual machines
Other connected hardware
Therefore, battery percentage reduction was recorded as evidence but was not treated as proof of battery failure.
The Usage History section was examined to establish how the laptop had been operating on battery and AC power.
One recent period showed approximately:
Battery active: 3 hours 35 minutes
and:
AC active: 5 hours 38 minutes

Figure 7 – Historical AC and battery usage.
The laptop has experienced both significant AC and battery usage.
This provides useful context when evaluating the battery report, as the machine has not been exclusively operating from battery power.
The Battery Capacity History section produced the most interesting results from the investigation.
The report showed a historical design capacity of approximately:
43,800 mWh
However, the recorded full-charge capacity varied considerably.
Examples included:
Period | Reported Full-Charge Capacity |
September–October 2024 | 32,173 mWh |
October 2024 | 29,225 mWh |
October–November 2024 | 30,353 mWh |
August 2026 | 12,472 mWh |
August 2026 | 11,461 mWh |
September 2026 | 11,867 mWh |
October 2026 | 11,373 mWh |
October 2026 | 25,304 mWh |

Figure 8 – Historical battery capacity reported by Windows.
The historical results are highly inconsistent with the current Installed Batteries reading of:
44,063 mWh
For example, Windows previously recorded values around:
11,000–12,000 mWh
but currently reports:
44,063 mWh
This represents a substantial difference.
Because of this inconsistency, the historical values cannot be treated as definitive proof that the battery physically degraded to approximately 11 Wh and subsequently recovered to 44 Wh.
The data should instead be treated as an indication that the battery capacity reporting has changed significantly over time.
The Battery Life Estimates section was then examined.
Windows recorded a range of estimated battery runtimes depending on the period and observed battery behaviour.
Some historical estimates were approximately:
45 minutes
to:
1 hour 47 minutes
while another recorded period produced an estimate of approximately:
4 hours 15 minutes

Figure 9 – Historical Windows battery-life estimates.
The wide variation demonstrates why battery-life estimates should not be treated as a fixed specification.
The estimated runtime is influenced by the workload being performed while Windows collects the data.
A laptop performing a heavy workload may have a dramatically shorter estimated runtime than the same laptop performing light desktop work.
The report's current overall estimate was also reviewed.
Windows currently estimates:
At Full Charge: 2 hours 44 minutes
At Design Capacity: 2 hours 40 minutes

Figure 10 – Current Windows battery-life estimate.
Windows currently estimates approximately:
2 hours 44 minutes
of active battery life at the reported full-charge capacity.
This is useful as a baseline, but it should not be considered a guaranteed runtime.
The results of the investigation can be summarised as follows:
Test | Result |
Operating System | Windows 11 |
Laptop | PC Specialist UltraNote V15 |
Battery Chemistry | Li-ion |
Design Capacity | 43,070 mWh |
Full Charge Capacity | 44,063 mWh |
Current Capacity vs Design | ~102.3% |
Cycle Count | Not reported |
Connected Standby | Not supported |
Current Estimated Runtime | ~2h 44m |
Historical Capacity | Highly variable |
Immediate Evidence of Current Capacity Degradation | No |
The current battery figures do not indicate obvious capacity degradation.
The battery is currently reporting a full-charge capacity of 44,063 mWh, compared with a design capacity of 43,070 mWh.
However, the historical data is considerably less consistent.
Windows previously recorded substantially lower capacities, including values around 11–12 Wh.
This creates an important diagnostic finding.
If this were a real IT support ticket, I would not recommend replacing the battery solely from this report.
Instead, I would perform additional testing.
The most useful next step would be a controlled real-world battery test.
The laptop could be charged to 100%, disconnected from AC power and then monitored while performing a consistent workload.
The time taken to reach:
100%
90%
80%
70%
60%
50%could then be recorded.
This would provide real-world evidence that could be compared with the PowerCFG results.
Overall Result
Further investigation recommended.
Reason
The current battery capacity reported by Windows appears healthy when compared with the design capacity.
However, the historical capacity data contains significant inconsistencies.
There is therefore insufficient evidence from the battery report alone to classify the physical battery as defective.
A controlled battery runtime test would provide additional evidence.
This lab demonstrates how a Windows 11 IT technician can use native operating-system tools to investigate a hardware-related support issue.
The important part of the exercise wasn't simply running:
powercfg /batteryreportThe useful part was analysing the information produced by the command.
The investigation showed that:
A battery report can contain contradictory or unusual historical information, and an IT technician needs to interpret that information rather than blindly accepting individual figures.
This is an important part of troubleshooting.
The goal isn't simply to find a number.
The goal is to collect evidence, identify patterns, recognise inconsistencies and then make an informed technical decision.
The Windows 11 battery investigation successfully generated and analysed a PowerCFG battery report.
The current battery reports:
43,070 mWh design capacity
and:
44,063 mWh full-charge capacity
giving an approximate current capacity of:
102.3% of the nominal design capacity.
On that basis alone, there is no obvious indication of current battery capacity degradation.
However, historical capacity measurements were significantly lower and varied considerably over time.
Because of this, the battery report does not provide enough evidence to justify immediate battery replacement.
The appropriate IT support action would be to perform additional controlled runtime testing and compare the real-world results against the Windows battery report.



Comments