The useful first step is to separate battery wear from higher power consumption after the update. They produce the same symptom but need different fixes.
- Run
winverand note the exact Windows build. - Generate a fresh report from an elevated Command Prompt:
powercfg /batteryreport /output "%USERPROFILE%\Desktop\battery-report.html"
In Installed batteries, compare Full Charge Capacity with Design Capacity. Then check Battery capacity history. If capacity was already falling before the update, the battery itself is worn. If capacity is stable but runtime suddenly dropped, focus on software, drivers and background activity.
- In Settings > System > Power & battery > Battery usage, compare the last 24 hours by app. Also test for 30–60 minutes with the same brightness, Balanced mode and the same light workload. Note percentage lost and whether the laptop remains warm at idle.
- Install the BIOS, chipset, graphics and power-management drivers from the exact HP model's support page. OEM graphics/hybrid-GPU drivers matter on a Victus because the discrete GPU staying awake can cause a large drain during light use.
- Run the HP UEFI battery test. If the laptop loses power mainly while the lid is closed, also run
powercfg /sleepstudyand inspect the affected standby session.
This Windows battery-report guide explains the capacity-history, recent-usage and runtime-estimate sections and what each can actually prove.
If Full Charge Capacity is still close to its pre-update value but active drain is much higher, do not replace the battery yet. Record the Windows build, HP BIOS/driver versions and the controlled test result; that evidence is much more useful for identifying an update or driver regression.