Some battery tools want an installer, a service, and a permanent tray icon before they will tell you a single number. BatteryInfoView wants none of that. It is a genuinely portable utility: extract three files, run the executable, read your battery, and delete the files when you are done. This guide explains exactly what ‘portable’ means here, how to run it from a USB stick, what stays behind (essentially nothing), and — briefly and honestly — what the freeware licence says about passing the program on to others.
Download the official packages from the download page or via /go/batteryinfoview (the official NirSoft file). More guides are in the Tutorials hub.
No installation, no additional DLLs
NirSoft’s own wording sets the terms: BatteryInfoView does not require any installation process or additional DLL files — you simply run BatteryInfoView.exe. There is also no documented .NET or other runtime requirement, so do not let any guide tell you a framework must be installed first; none is documented anywhere in the official documentation. Each official ZIP contains exactly three files:
BatteryInfoView.exe— the program itself (80,384 bytes in the 32-bit build; 115,200 bytes in the 64-bit build, v1.27).BatteryInfoView.chm— the help file.readme.txt— the documentation, identical in substance to the official product page.
The ZIPs themselves are small: 118,909 bytes (32-bit) and 132,819 bytes (64-bit). Extract them anywhere — a folder on the desktop, a tools folder, a USB stick — and the extracted folder is the installation. Because nothing is registered or installed, running the program does not modify your system in the way an installer does, and the official documentation describes no registry or system modification function.
Running from USB
- Download the ZIP for the architecture you need — the 64-bit build (added in v1.26) for modern 64-bit Windows, the 32-bit build for older or 32-bit machines — from the download page.
- Extract all three files to a folder on the USB stick, keeping them together.
- On the target laptop, open the folder and run
BatteryInfoView.exe. Press F7 for the health check (walkthrough) or F8 for the Battery Log. - Export any report you need with Ctrl+S (export guide) — save it to the stick so the record travels with you.
- Close the program and remove the stick. Nothing was installed on the laptop.
This is the practical way to check a used laptop before buying, to help a friend or family member, or to survey several machines in an office — one stick, no installs, no leftovers on machines that are not yours. The command-line save options pair naturally with this workflow for fast, identical captures per machine; see Command-Line Options.
Uninstalling means deleting the files
Following the standard NirSoft pattern, uninstalling is simply deleting the files. There is no uninstaller to run because there was no installer: delete the extracted folder (or the three files) and the program is gone. If you placed a language file (batteryinfoview_lng.ini) next to the executable for a translation — see Language Packs — delete that too, along with any reports you exported and no longer need. Settings the program remembers, such as window position, are part of normal program behaviour; the honest portability claim, and the one the documentation supports, is: no installation process, no extra DLLs, removal by deletion.
The licence: what redistribution actually allows
BatteryInfoView is freeware by Nir Sofer (NirSoft) — it is not open source, and no source-code licence is published. The official licence allows you to freely distribute the utility — via disk, CD-ROM, the Internet, or in any other way — subject to clear conditions. In plain terms:
- You must not charge anything for it.
- You must not sell it or distribute it as part of a commercial product.
- If you distribute it, you must include all files in the distribution package, without any modification.
The software is provided ‘AS IS’ without warranty, with the author not liable for damages, per the official disclaimer. Safe summary wording — the one this site uses — is: freeware; free to use and to redistribute unmodified, provided you don’t charge for it or bundle it into a commercial product. That is why this site’s main download channel links to the official NirSoft file rather than repackaging it: the licence’s unmodified-package condition makes the official file the cleanest thing to share, and our Terabox links are labelled honestly as mirrors rather than dressed up as anything else. Running the program on as many laptops as you like, including from USB at work or at home, sits comfortably within free use; selling it, charging for the download, or bundling a modified copy into a commercial product does not.
Portable does not mean limited
Portability costs you nothing in features here, because the portable executable is the product: both views (F7 Battery Information, F8 Battery Log), all 19 documented fields, Ctrl+S export to text/CSV/HTML/XML, the full command-line save options, Advanced Options (F9), and the language-pack system all work from the extracted folder exactly as documented. There is no separate ‘installed edition’ with more capability. What the program does not do at all — calibration, repair, charge limiting, temperature monitoring — it does not do in any edition, because those functions do not exist in BatteryInfoView; see the honest rundown starting from the health check and the FAQ page.
Frequently asked questions
Can I keep BatteryInfoView on my laptop permanently without installing it?
Yes. Many people simply keep the extracted folder in a utilities folder and run it when needed. ‘Portable’ describes how it runs, not a time limit — there is no licence clock or feature expiry on the freeware program.
Do I need administrator rights to run it?
The official documentation does not state an admin requirement either way, so this site does not present one as a spec. In normal experience it is run as a standard user; if your organisation’s policies restrict running downloaded executables generally, that policy — not BatteryInfoView — is what applies.
Which build should go on the USB stick?
Carry both if space allows — together they are under 260 KB as ZIPs. Use the 64-bit build on 64-bit Windows and the 32-bit build on 32-bit Windows or very old machines; official support runs from Windows 2000 up to Windows 11. The choice is explained further in 32-bit vs 64-bit: Which Download Do You Need?
Next: run the health check, try the tool on Windows 11, or browse the Tutorials hub.
One more portability habit: keep the three files together
The single habit that keeps portable use trouble-free is keeping the distribution together. The executable, the help file, and readme.txt belong in one folder, and the optional language file — if you use one — belongs in that same folder, as Language Packs explains. Copying only the .exe to a desktop while leaving the rest behind still runs the program, but it scatters the package the licence asks distributors to keep whole and makes later checks — version, help, documentation — harder than they need to be. Treat the folder as the unit: copy the folder, run from the folder, delete the folder. That discipline is also what makes the USB workflow in this guide reliable across many machines, because every laptop sees exactly the same complete, unmodified set of files.