You did the responsible thing: set a charge limit at 80 percent to baby your battery. Then you glanced at the taskbar and saw 100 percent staring back at you. The limiter is on, the battery ignored it, and now you are wondering whether the feature is decorative.
It is not — but charge limiters are a handshake between software, firmware, and the embedded controller, and any one of those layers can break the deal. This guide finds the broken layer, starting with the settings you can see and working down to the firmware you cannot. If your specific limiter is Lenovo’s, the Conservation Mode stuck-on guide covers its quirks in detail.
Why this happens
- The app toggle does not reach the firmware. The UI says on, but the embedded controller never got the message.
- A BIOS setting conflicts. Firmware-level battery care can override or fight the Windows app.
- The app or BIOS is outdated. Limiter bugs are routinely fixed in updates.
- The limiter only applies on AC power. Some implementations ignore the cap when charging from certain states.
- A recent update reset the feature. Windows or firmware updates can silently disable limiters.
- Competing battery tools. Two apps managing the same limit step on each other.
- The battery needs a full cycle to engage. Some limiters only take effect after one complete charge cycle.
- Power plan resets wiped the configuration. Switching power plans or running a “reset to defaults” can clear limiter hooks that the app does not automatically reapply.
How to fix it
Work through these in order — start with Fix 1 and only move on if the battery still sails past the limit.
Fix 1: Verify the setting actually saved
Open your manufacturer’s app — Lenovo Vantage > Device > Power, MyASUS > Battery Health Charging, Dell Power Manager > Battery Settings, or MSI Center — and confirm the limiter shows as enabled. Then close the app entirely, reopen it, and check again. Toggles that revert on reopen were never applied, and this reopen test catches the problem in seconds. Try the off-on-off dance: disable, wait 30 seconds, re-enable, and keep the adapter plugged in — several implementations only commit the change on AC power. Drain the battery below the limit first (to 70 percent for an 80 percent cap), then charge and watch whether it stops.
Fix 2: Check the BIOS for a conflicting setting
Restart into the BIOS/UEFI (F2, Del, F1, or F10 by brand) and look under Configuration, Power, or Advanced for battery conservation, charge threshold, or battery health options. If the BIOS has its own limiter, align it with the app: either configure the limit in the BIOS and leave the app alone, or disable the BIOS option and manage it from the app — but not both fighting each other. Save and exit, then test a full charge cycle. Firmware-level settings win every argument with Windows apps.
Fix 3: Update everything in the chain
Update the manufacturer’s app from the Microsoft Store, install all pending System Update driver packages (especially power management and BIOS), and flash the latest BIOS for your exact model from the maker’s support site with the adapter connected. Limiter failures are a classic “fixed in the latest firmware” bug — Lenovo, ASUS, and Dell have all shipped exactly such fixes. After updating, re-enable the limiter and test from below the cap. Check Lenovo’s official support site or your brand’s equivalent for the newest releases.
Fix 4: Reset the embedded controller
The EC enforces the limit at the hardware level and can get wedged. Shut down, unplug the adapter, remove the battery if removable, and hold the power button for 30 seconds. Reconnect AC only, boot, shut down, reinstall the battery, and boot normally. Re-enable the limiter in the app. This clears EC states where the limit was “on” in software but never engaged in hardware — a surprisingly common root cause.
Fix 5: Remove competing battery software
Open Settings > Apps > Installed apps and inventory everything battery-related: old manufacturer power tools, third-party limiters, “battery saver” utilities. Keep exactly one: the current manufacturer app. Uninstall the rest — two tools writing charge limits to the same controller produce exactly this “setting does nothing” symptom. Restart after uninstalling and test the limiter alone.
Fix 6: Give it one full cycle to engage
Some limiter implementations only activate after the battery completes a full charge cycle under the new setting. Disable the limiter, charge to 100 percent, then re-enable the limiter and discharge to around 50 percent in normal use. Now charge again and watch: many users report the cap engages properly on this second cycle. It is an odd quirk, but it costs nothing to try before deeper troubleshooting.
Fix 7: Confirm with a battery report
To verify the limiter is truly working — not just displaying a capped number — run in an elevated Command Prompt:
powercfg /batteryreport
Charge with the limiter on, then check the report’s recent usage history: the charge level should plateau at your cap and hold there. If the report shows charging continuing past the cap, the limiter is definitively broken at the firmware level — report it to the manufacturer’s support with your exact model and BIOS version, since that is a bug they need to fix. Our battery report guide explains every section if you want to dig deeper.
Closing
A limiter that does not limit is a communication breakdown between app, BIOS, and embedded controller — and one of those three is always the culprit. Align the settings, update the firmware, reset the controller, and test carefully after each step, and the cap will hold. Once it does, leave it on: that quiet 80 percent ceiling is adding years to your battery’s life without you ever thinking about it again, which is exactly what a good background setting should do.
