This is the diagnostic companion to our step-by-step fix guide for the same symptom. Where that guide gives you fixes in order, this one teaches you to diagnose: how to prove the BIOS update is actually the cause, isolate firmware from drivers from hardware, and decide whether rollback is warranted. The timing makes this case tempting to rush — “it broke right after the update, just undo the update” — but a rushed rollback on the wrong diagnosis wastes an hour and teaches you nothing. Work the isolations; each test rules out one suspect.

Why this happens

  • Charge settings wiped: Updates reset BIOS customizations, including charge thresholds and battery-health modes — a reset limit looks exactly like “not charging.”
  • EC firmware bug: The embedded controller code in the new BIOS mishandles the charging handshake with the battery.
  • Half-flashed controller state: A glitchy or interrupted flash leaves the charge controller in a confused in-between state that a normal reboot doesn’t clear.
  • Driver/firmware mismatch: The new BIOS speaks a slightly different firmware interface, and Windows is still using the old battery and chipset drivers.
  • Battery re-authentication: Some updates re-run battery authentication and temporarily fail to recognize even a genuine battery.
  • Genuine coincidence: Rarely, the battery actually dies at the same time — assume firmware first, but verify rather than assume.

How to fix it

Work through these in order — each test isolates one variable and rules out one suspect before you move on.

Fix 1: Isolate the timing

  1. Open Settings > Windows Update > Update history and find the BIOS/firmware update entry with its date.
  2. Run powercfg /batteryreport and check the usage history for the last successful charge before that date.
  3. If charging worked the day before and failed the day after, you have a firmware case — proceed with confidence.
  4. If charging was already intermittent before the update, treat this as hardware the update merely exposed, and check wear in the report first.

Fix 2: Isolate the EC with a hard reset

  1. Shut down completely and unplug the charger.
  2. Hold the power button for 30 to 40 seconds — this resets the embedded controller, which manages charging at the hardware level.
  3. Plug in, boot, and watch the battery icon for 5 minutes.
  4. If charging resumes, the update left the controller in a bad state and the reset cleared it — the most common outcome of this whole guide.

Fix 3: Isolate the settings variable

  1. Enter BIOS Setup (F2, Del, or F10 depending on brand).
  2. Choose Load Optimized Defaults (often F9), save, and exit — this clears corrupted power settings the update may have left behind.
  3. Re-enter Setup and check battery-specific options: charge thresholds, Battery Health Manager (HP), Battery Health Charging (ASUS), conservation modes.
  4. Reapply your preferred settings, save, boot into Windows, and retest. A limit silently re-enabled by the reset explains “not charging” with a perfectly healthy battery.

Fix 4: Isolate the Windows driver variable

  1. Test charging from the BIOS setup screen first: if it charges there but not in Windows, the firmware is fine and Windows is the suspect.
  2. In Device Manager > Batteries, uninstall the ACPI battery driver; in System devices, check the chipset/ACPI entries too.
  3. Full shutdown, unplug 60 seconds, boot on AC — Windows rebuilds the driver stack against the new firmware.
  4. If charging returns in Windows, it was a driver/firmware mismatch. For the ordered fix sequence, see how to fix a battery not charging after a BIOS update .

Fix 5: Isolate the firmware version

  1. Note your current BIOS version from msinfo32 and compare it with the latest on the manufacturer’s support site.
  2. If a newer BIOS exists, install it on AC power — charging bugs are frequently fixed in the very next release.
  3. If yours is already the latest, re-flash the same version: a second clean flash repairs incomplete flashes.
  4. After any flash, redo the EC reset from Fix 2 — the controller needs a clean initialization against the new firmware.

Fix 6: Isolate hardware coincidence

  1. In the battery report, check wear: (Design − Full Charge) ÷ Design. A heavily worn battery can genuinely die around an update.
  2. Check the report’s capacity history for a sudden cliff versus a gradual decline — cliffs mean failing cells, not firmware.
  3. If the battery is removable, test with it out (AC only) to confirm the adapter and board are healthy.
  4. A healthy battery (low wear, no cliff) that won’t charge after the update is firmware, full stop — don’t buy a battery for this.

Fix 7: Confirm with a rollback test

  1. Only now, with everything else ruled out, roll back: download the previous BIOS from the manufacturer and follow their rollback procedure exactly.
  2. If charging returns on the old BIOS, you’ve proven a firmware regression — document both version numbers.
  3. Report it through the manufacturer’s support portal with your model, both BIOS versions, and the symptom timeline.
  4. Stay on the old BIOS until a fixed release appears, then update — and check the changelog for battery or power mentions first. Lenovo-specific rollback steps are in our Lenovo BIOS-update charging guide .

Fix 8: Make the call

  1. EC reset or settings fix worked → done; note what you changed in case a future update reverts it.
  2. Rollback restored charging → confirmed regression; stay put, report it, watch for the fixed BIOS.
  3. Nothing worked and wear is high → the battery genuinely failed; replace it.
  4. Nothing worked and wear is low → contact manufacturer support with your timeline and test log — that’s a warranty-grade firmware case.

Closing

When a battery stops charging the day a BIOS updates, the update is guilty until proven innocent — but “guilty” still has five different meanings, from a wiped charge limit to a genuine firmware regression. The isolations above tell you which one in about an hour, and they keep you from the two classic mistakes: rolling back a BIOS for what was actually a reset charge limit, or buying a battery for what was actually firmware. Write down the BIOS versions and what each test showed; if you end up reporting the regression, that log is what gets it fixed.

Dell’s BIOS downloads and battery diagnostics are at Dell Support . Microsoft’s power troubleshooting docs are at the Windows support hub .

Frequently asked questions

How do I know the BIOS update caused my charging problem?
Check the dates: find the BIOS update in Settings > Windows Update > Update history or your manufacturer’s update log, then check powercfg /batteryreport for the last successful charge. If charging worked the day before the update and failed the day after, that’s a firmware problem until proven otherwise. Coincidental hardware failure at the exact same moment is rare.
Can I test whether it's firmware or a dead battery?
Yes. First, check the battery report for wear — a healthy battery that suddenly won’t charge points at firmware. Second, test charging from the BIOS setup screen, outside Windows: if it won’t charge there either and it did before the update, the firmware is the cause, not Windows and not the battery.
Should I roll back the BIOS immediately?
Not as the first step. Rollback is the confirmation test, not the opening move — try loading BIOS defaults, an EC reset, and driver reinstallation first, because those fix most cases without a downgrade. Roll back when you need to prove a firmware regression or when nothing else worked.
What if the battery charges in BIOS but not in Windows?
Then the firmware is fine and Windows is the problem — usually the battery driver stack talking to the new firmware the old way. Reinstall the ACPI battery drivers in Device Manager and update the chipset drivers from the manufacturer’s support site. That combination resolves most Windows-side cases.