If your laptop runs Windows 10, BatteryInfoView works on it — fully and officially. The tool, by Nir Sofer (NirSoft) and currently at version 1.27, officially supports “any version of Windows, starting from Windows 2000 and up to Windows 11”, which puts Windows 10 squarely in the middle of its range. This guide covers the practical points for Windows 10 users: which build to download, what to expect from the two views, and how BatteryInfoView fits alongside two things Windows 10 users ask about most — the history tool BatteryHistoryView and the battery page in Settings.
Compatibility: nothing special to arrange
There is no Windows 10 edition, compatibility mode or installer for BatteryInfoView. The program is portable: download the ZIP from the download page, extract it, and run BatteryInfoView.exe. No installation process and no additional DLL files are required, and no .NET or runtime prerequisite is documented. Deleting the extracted files removes the tool. Most Windows 10 laptops are 64-bit, so the 64-bit build (/go/batteryinfoview, ZIP 132,819 bytes) is normally the right download; the 32-bit build (/go/batteryinfoview-32bit, 118,909 bytes) serves 32-bit installations and works as a fallback. 32-bit vs 64-bit explains how to check your system type in Settings > System > About.
What you see on Windows 10 is the complete feature set. Battery Information view (F7) shows the 19 official fields — from Battery Name and Power State through Designed Capacity, Full Charged Capacity, Battery Health (Full Charged Capacity divided by Designed Capacity), Voltage and Charge/Discharge Rate — refreshing every 10 seconds by default. Fields such as Serial Number, Manufacture Date and cycle count appear only if your battery provides them; that rule is set by the battery, not by Windows 10. Battery Log view (F8) adds a line every 30 seconds by default and also logs on suspend and resume. Export either view with Ctrl+S to CSV, tab-delimited, HTML or XML files.
Tips for getting the most from it on Windows 10
- Pin down a baseline early: record Designed Capacity, Full Charged Capacity and Battery Health at full charge, so later readings have something to be compared against.
- Use the log across a real workday rather than judging from a single glance. The F8 log shows drain through work, idle and standby periods in one table.
- Turn on automatic saving of each new log line (Advanced Options, F9, a comma- or tab-delimited file) if you want a record without remembering to export it.
- Remember the four time fields are estimates calculated from the change in capacity over the last 30 seconds. Expect them to move when your workload changes; that is their design, not a Windows 10 quirk.
- Keep a verified copy: the SHA-256 values for both version 1.27 ZIPs are listed on the download page, and
certutil -hashfilewill confirm any copy in seconds.
If the program will not open or shows nothing on a Windows 10 machine, the version of Windows is unlikely to be the cause. Work through BatteryInfoView Won’t Open (extract the ZIP, verify the hash, try the other build) and BatteryInfoView Shows No Data (run it on the laptop itself, confirm Windows can see the battery) before suspecting compatibility.
The Windows 10 bonus: BatteryHistoryView and SRUDB
Windows 10 gives you something older Windows versions do not: a battery history that Windows itself records. NirSoft’s sister tool BatteryHistoryView reads that history from the SRUDB.dat database on Windows 10 and Windows 11, and presents Timestamp, Cycle Count, Designed Capacity, Full Charged Capacity, Charge Level/Percent and active and connected-standby times for recorded points in the past. BatteryInfoView answers “what is my battery doing right now, and what does its log show while I watch?” while BatteryHistoryView answers “what has Windows already recorded about this battery over time?” Used together on Windows 10, they cover live monitoring and recorded history from the same author, both freeware and portable in spirit.
The pairing is especially helpful when a live field is blank. If cycle count does not appear in BatteryInfoView because the battery does not report it live, the recorded history BatteryHistoryView extracts may still contain cycle-count values at past timestamps — where Windows recorded them. The full walkthrough is at BatteryHistoryView guide, and the live-versus-history distinction is also covered in Cycle Count Is Blank. Neither tool can manufacture history that was never recorded, so a fresh Windows 10 installation will show a short history at first.
BatteryInfoView vs the Windows 10 Settings battery page
Windows 10 has its own battery pages in Settings, centred on the charge percentage, estimated remaining time, battery saver settings and which apps have used battery recently. That page and BatteryInfoView overlap only at the headline percentage — officially, BatteryInfoView’s Current Capacity percentage is the same value Windows displays — and then diverge. Settings is about managing the system; BatteryInfoView is about the battery hardware itself: capacities in mWh, health from Designed versus Full Charged Capacity, voltage, charge/discharge rate in milliwatts, chemistry, and exportable logs. Settings cannot show you Full Charged Capacity against Designed Capacity, and BatteryInfoView cannot change a single power setting — it is read-only.
For the structured side-by-side, see BatteryInfoView vs the Windows Settings Battery Page. In daily practice most users keep both: Settings for battery saver and per-app usage, BatteryInfoView when the question is “how worn is this battery, in numbers?” The built-in powercfg /batteryreport sits between them as a periodic formal report — compared in detail in BatteryInfoView vs powercfg /batteryreport.
What stays the same, and what the tool still cannot do
Windows 10 does not unlock extra BatteryInfoView features, and the program’s limits are identical on every Windows version. It has no temperature or per-cell voltage field, no calibration or repair function, and no charge limiting or power-plan control. It displays, logs and exports information — nothing more, on Windows 10 as on Windows 11. Readers weighing an upgrade may also read the companion notes on the Troubleshooting hub, where the Windows 11 guide sits alongside this one.
Frequently asked questions
Do I need a special version of BatteryInfoView for Windows 10?
No. Version 1.27 supports Windows 2000 through Windows 11 with the same two downloads. Pick the 64-bit ZIP for 64-bit Windows 10 (the usual case) or the 32-bit ZIP for 32-bit Windows 10.
Why does BatteryHistoryView need Windows 10 or 11?
Because it reads the battery history stored in Windows’ SRUDB.dat database, which is a Windows 10/11 data source. BatteryInfoView itself has no such requirement — it reads the live battery and works on far older Windows versions.
BatteryInfoView and Settings show the same percentage but different times. Which is right?
Both are estimates built differently. BatteryInfoView’s time fields are explicitly calculated from the change in capacity over the last 30 seconds, so they react fast to workload changes. Compare capacities, not time estimates, when you want a stable judgement.