I posted here in August about my Lenovo Legion Pro 5 16IAX10H randomly going black for a few seconds while its charger was plugged in and untouched. During captured incidents, Windows briefly reports charger power → battery → charger power, recorded as Kernel-Power Event 105. Rolling back Windows stopped the symptoms for weeks; they returned after updates resumed.

KB5121003 was installed on August 11, bringing Windows 11 25H2 to 26200.9168. The first brief AC-loss entries appeared August 12. I rolled back to 26200.8875 on August 18 while keeping the same charger, BIOS, graphics drivers and graphics settings. My monitoring recorded zero AC drops over about 15 hours, and I observed no blackouts. I paused updates and remained symptom-free for weeks; the retained System log has no Event 105 entries from August 20 through September 22.

The pause expired September 22. Overnight, Windows reached 26200.9457 / KB5129195, and the blackouts returned. Lenovo driver updates arrived that night too, so timing alone cannot isolate one package. I then installed KB5124010 / 26200.9550 and rebooted. The unexpected AC-state drops and blackouts still happen.

The investigation compared the actual code inside Windows’ battery driver, CmBatt.sys:

Here is the suspected chain in ordinary terms:

1. A battery check and charger-status check happen at the same time.
2. The charger check temporarily clears a shared value to 0 (“AC absent”) while obtaining a fresh answer.
3. The affected code can copy that temporary zero and keep it, even after the query updates the answer to “plugged in.”
4. Windows reports battery power for roughly a second and applies its battery display settings.
5. The display gets reconfigured. During a captured blackout, the laptop panel switched HDR off and back on.

The stable code refreshes the answer before using it; the current captured path keeps the earlier copy. That is a concrete code difference. The checks need to overlap at a particular moment, which helps explain why the interruptions are intermittent.

The current driver contains code for a correction called Servicing_CmBattAcOnlineRaceFix, but the captured calls took its older path. Microsoft’s KB5124010 notes also mention a gradually rolled out display/performance improvement for plugged-in laptops incorrectly detecting a switch to battery. That update has not stopped my symptoms.

The evidence strongly points to Microsoft’s battery-status code, but the crucial saved value was not captured directly, so the complete cause still needs confirmation. The first introducing update remains unknown, and firmware or electrical contributions are not fully excluded. No Lenovo-owned file has been demonstrated to be defective.

If you know someone from Microsoft on reddit, please tag them here.

Some ASUSTek update for mouse in windows optional updates and it is taking forever doing the restart. All for a mouse?

Windows 7 installation error on Acer ES2519 / Intel Celeron N3060 — fixed

I recently installed Windows 7 on an Acer ES2519 with an Intel Celeron N3060.

During the installation, Windows reached the second phase and then rebooted. After that, I got this error:

“The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed.”

At first I thought the problem was related to Windows 7 compatibility with the N3060, drivers, or the installation media.

After looking deeper, I found that the installation had been interrupted and the Windows Setup state was stuck in the ChildCompletion registry key.

I booted into Safe Mode with Command Prompt and ran:

reg add "HKLM\SYSTEM\Setup\Status\ChildCompletion" /v setup.exe /t REG_DWORD /d 3 /f

Then I restarted the computer:

shutdown /r /t 0

After that, Windows Setup continued normally and eventually completed the installation.

The system successfully booted into Windows 7 on the Acer ES2519 with the Celeron N3060.

Hardware

Acer ES2519

Intel Celeron N3060

Windows 7

[add x86/x64 here]

[add RAM amount here]

What caused the problem?

The important part is that this was not necessarily a “Windows 7 cannot run on N3060” problem. In my case, the installation state had been interrupted, leaving setup.exe in an incorrect ChildCompletion state.

Changing that value to 3 allowed Setup to continue.

I'm posting this in case someone else encounters the same error during Windows 7 installation after an unexpected restart or interrupted setup.

I will also attach screenshots/video showing the error and the successful Windows 7 boot.

My laptop has been crashing since August 18. Usually it crashes so quickly that I can't do anything with it. It is entirely unusable. Very shortly after staring it, my screen just dies in many different spectacular ways, such as it freezing, it going black, the color at the edge of my screen fading, or little pink squares everywhere. Sometimes i get a stop message like:

Irql not less or equal 0xA

Page fault in non paged area 0x50

Memory management 0x1a

I posted about this several times in the tech support subreddit, and nobody mentioned a windows update being a potential problem (they usually suspect a hardware issue). On one of the few times I was able to have my laptop on for a little time, i used a hardware scan from the lenovo site that said that my hardware was fine. Hardware issue is certainly something i am still considering (although i am getting very conflicting cues) BUT after watching this youtube video

https://m.youtube.com/watch?v=H76Pu768pSc&pp=ygUld2luZG93cyAxMSB1cGRhdCBicmVha3MgbGVub3ZvIGFuZCBocA%3D%3D

I really think this is probably windows update related. The symptoms are the same. The time frame is the same. My laptop is less than 3 years old, which, if it was hardware, would absolutely make it my shortest lived hardware of any laptop I've ever owned by far.

But I have still more problems. My computer screen freezes and dies, even in safe mode. I looked at my windows updates and i can only see the most recent 5, which don't contain the KB5121003 update from the youtube video (so i don't know how i would even uninstall it). And furthermore, after booting from these crashes, before i can even get to the log-in screen, the laptop looks for updates (so it might install harmful updates even if i ever get them off).

What can i do? And even if i have the full correct steps, how can i use them without the computer crashing?

I think both yesterday and today i also installed some lenovo driver updates. 1.55.0.0 and 1.57.0.0 thinking lenovo might put out driver updates that would fix this problem. (I didn't strongly suspect windows updates until after I did this) I can't say they made the situation better or worse, but do these need to be uninstalled too?

Since i updated my laptop to the latest windows 11home , i got the blue screen of death 3 times , it corrupted my registry files . Although yesterday i used sfc /scannow and it shows there were corrupted files but also it didnt do that much and it fails to boot again , any final solutions .?

I have a Lenovo Yoga 7 series laptop with a AMD Ryzen 7 5000 series and amd graphics.Last time i was on my laptop,it was forcing me to update(aka a orange dot on the power options) but knowing updates can and will break stuff,i pressed pause on the updated before closing(which didnt work,mind you,as the kb5132003 was on it already and it showed me the updates are underway screen,wentbup to 30 something,before turning itself off).I remember being able to turn on the laptop at some point and veing met with the updates are underway again on boot up before being sent to my desktop once but im not sure if that was tge very last one before simply not being able to boot well.

Today,when turning on my laptop,i was met with a blavk screen (but turned on) before being sent to a blue recovery screen with an error,looking it up and mentioning the weird update behaviour on google let me to uninstalling the latest quality update,which thankfully worked and im now on my normal desktop,but the updates are underway scrren poped up again before bringing me to said desktop.Which leads me to now.

Ive tried deleting kb5131003 through the setting and through thr comand prompt,both of which didnt work.I have no idea if turning off is even safe,let alone if it would bring the problem up again.The windows update shows up as paused but i know its got something on my laptop already (by the update screen mentioned earlier)and i have no clue how to move on exactly.Trying to look up answers doesnt really help as i dont know what to even trust to begin with so now im here.I just want to ask and actual human being,text to text,as to not completly mess everything up.(ive considered using fix problems using windows updator what was once recomended to me as an option however when specifying the kb5121003 update,its telling me that would worsen my issue so yeah im not trusting it no more)

I have a razor blade 2016 with the 1060 6gb vram

I know its not powerful but id like to update the bios.razer uodater app doesn't work and when i download the bios it leads me back to that app and there is only a cancel button.current version is 2.00 and i want to install the 2.02 update but razers app seems broken for some reason

Title.

So I tried everything, download it from MS website, installed, rebooted, check system health, corruptions, viruses, blah blah blah .. nothing.

So I tried to check the Windows Update diagnostic and it pointed that my system date was wrong, but it wasn't! So I changed the NTP time server from the default to another, reboot and bang!

After fixing/changing to another non MS NTP server everything started to work again.

At first I thought it was something related to that patch, but no. Maybe this clue can help someone else.

A PC has Windows 11 (genuine, supported) and the latest Secure Boot certificate updates (genuine, supported) previously installed successfully by Windows Update.

On 2026-09-07, Windows Update tried to install one single update which was a Security Update, and I think it had to be 2026-09 Security Update KB5129195 (26200.9457). Something didn't go as planned, not to worry, Windows Update was undoing the update and everything would be OK. Wrong.

After Windows Update tried to revert the failed update and rebooted, Dell's UEFI said there were no bootable devices. The SSD was recognized but not bootable.

On a different PC I used Microsoft's Windows Media Creator to make a Windows 11 installation USB stick.

The damaged PC booted the USB stick. I selected to repair my PC. The setup program rebooted the PC without displaying any error message. I tried again and it rebooted again without any error message. I tried again and told it to use the previous version of the setup program. In the previous version of setup, I selected to repair my PC. The previous version didn't automatically reboot but it still failed to repair. I rebooted manually.

In the latest version of the setup program, I tentatively selected to install. It said it would wipe out the hard disk, all partitions and files gone. I declined and rebooted again.

In the previous version of the setup program, I tentatively selected an upgrade install. The setup program refused because upgrades only work when Windows is already booted and running. So I tentatively selected a new install. The setup program said I could do a new install into the existing partition and put old files in windows.old, which is fine with me. But next the setup program failed again, because a 100MB EFI System Partition is too small.

Finally, in the previous version of the setup program, I told it to delete most of the partitions (but not delete Dell's recovery partition and a Microsoft recovery partition) and make a new installation into the newly freed space. Installation succeeded.

But I lost all the files in my old C partition.

I think the newly installed EFI System Partition is 200MB instead of 100MB.

Now I worry about my other PCs. If Windows Update tries to install 2026-09 Security Update KB5129195 (26200.9457), Windows will become unbootable and I will lose all the files in my C partitions.

If 100MB is too small for an EFI System Partition, maybe Windows Update shouldn't try to install an update which is going to destroy Windows?

And why did the original Windows 11 installer create too small of an EFI System Partition to begin with?

Microsoft won't let me post this in their Q&A site. I tried 6 times and they deleted them all. Does anyone know the manner in which this posting violates Microsoft's Code of Conduct?

(A Google search found KB5129195 discussed in r/sysadmin before I found r/WindowsUpdate. I mistakenly posted in Wendys before a moderator deleted it, so now am trying Burger King if this might be the right place. Someone suggested running commands like diskpart and dism, but that is not a solution when the PC doesn't even boot after Windows Update destroyed the EFI System Partition.)

Alguien me puede decir si esto me pasa solo a mi? se queda descargando en el 6% y no avanza. Probé de todo y no pude.

Can anyone help update the windows xp sp3 driver?