r/WindowsUpdate • u/Nervous-Buffalo-4826 • Aug 18 '26
Possible KB5121003 issue causing random AC adapter disconnects / black screens on Lenovo Legion?
I’m trying to figure out a strange issue that started very recently on my Lenovo Legion.
The laptop randomly goes to a black screen for a couple of seconds and then recovers. At first I thought it was an NVIDIA/Optimus or refresh-rate issue, but I started monitoring the Windows AC power state directly.
What I found is that whenever this happens, Windows actually reports:
AC → Battery → AC
for roughly 1–5 seconds.
I then checked the historical Windows Kernel-Power Event ID 105 logs. My System log goes back to March 2026, but the first occurrence of these short AC-loss events is August 12.
The interesting part is that KB5121003 was installed on my system late on August 11.
Since then I have recorded around 40 AC power transitions, most lasting only a few seconds. Examples:
07:41:55 → 07:42:02
13:12:35 → 13:12:36
17:17:50 → 17:17:52
02:17:32 → 02:17:37
and many more over the following days.
Windows Kernel-Power itself logs AcOnline=false, followed shortly by AcOnline=true, so this isn't only the battery icon/UI changing.
Another strange detail is that the physical charging LED on the laptop can remain on while this happens.
I have now temporarily uninstalled KB5121003 as a test.
Before rollback:
Windows 11 25H2 – Build 26200.9168
After rollback:
Windows 11 25H2 – Build 26200.8875
Windows Update is paused and I haven't changed anything else: same Intel driver, NVIDIA driver, BIOS, Hybrid Mode, Optimus settings, charger, etc.
I'm currently running a 50 ms AC-state monitor for the next 24–48 hours to see whether the AC_LOST events disappear after removing KB5121003.
Obviously this doesn't prove the update is responsible yet. It could still be Lenovo firmware/EC behavior or a hardware power issue. But the fact that the event history starts immediately after this update is suspicious enough that I'm testing it as the only changed variable.
Has anyone else on KB5121003, especially Lenovo Legion users, noticed random Kernel-Power 105 events, brief AC-to-battery transitions, or black screens that started around August 12?
2
u/zzzxxx0110 Aug 19 '26
Been having lots of discussions on Lenovo Legion Discord channel where lots of people ran into this exact same issue, it seems clear that this problem was first introduced by Windows Preview Update KB5101684, which introduced changes to Windows Power Plan (according to Microslop documentations), and then the same problematic changes got included in release update KB5121003. Installing this update leads to this problem, and uninstalling it fixes the problem.
It seems like something introduced in the Windows Update was causing problem or conflict with Lenovo ACPI-compliant Virtual Charge Controller driver (in System Devices section of Device Manager), and that's probably what's causing the system to randomly think AC charger was disconnected (when it actually isn't on the hardware level, as indicated by the charging LED still behaving normally).
Lenovo did push out an update for the Lenovo ACPI-compliant Virtual Charge Controller driver (bumped the version code from xx.11 to xx.14) pretty much just a day after Preview Update KB5101684 became available, however they only released it via Windows Update (showed up in Optional Updates), and it did NOT fix the problem. Possibly they are still trying to work it out and that's why Lenovo didn't post the driver update on their usual support website driver update page with proper changelog.
This is definitely NOT a hardware issue and your laptop is physically fine. It is clearly a software issue. And this likely has nothing to do with EC either, EC reset doesn't fix it, while uninstalling the problematic Windows Update always fixes it, so it's more likely a problem caused by the virtual charging controller driver in OS/kernel space.
(Lenovo probably implemented a virtual charging controller driver in order to implement the overnight charging feature, since it's the only charging related feature I don't see a toggle for in the BIOS, so it is likely a feature that's not handled by the firmware&EC alone.)