2026-04 Security Update (KB5083769) (26200.8246) causing failing boot loop

Question

2026-04 Security Update (KB5083769) (26200.8246) causing failing boot loop

Vagabond Superstar 0

I just attempted to install the latest security update, and my PC went into a death loop where the screen just showed a mosaic of weird pixels followed by an intermediate blue screen saying that Windows needed to be recovered. It gave an option to retry, which I used, then it went into a boot loop where it kept giving the message that it was attempting to repair the issue, and then it would loop back thru the pixelated screens.

The PC:

HP Pavillion 590-p0044

AMD Ryzen 5 2600

32GB RAM

GTX 1080ti GPU

Windows 11 Home ED

Any ideas on what happened to my PC and what I can do to get it back up and running?

L M 5 Reputation points

2026-04-17T21:33:32.3033333+00:00

Having exact same issue on Dell Desktop. Pixelated screen, attempts to update, gets to 30%, fails, reboots and then repairs as it indicates the update didn't succeed. Reboots back to state prior to loading the update.

How do we update? I am not able to do any future windows updates as its hung on this update!
Vagabond Superstar 0 Reputation points

2026-04-21T01:09:27.1333333+00:00

Ok, so after some time, fully disassembling my PC, cleaning it, putting back together, I restarted it.

It gave me the HP "CMOS checksum is invalid" screen. I hit enter to restart and my PC fully restarted on its own. I'm including a pic of the popup:

I don't know exactly what happened, but my PC is back up and running.

Checking the windows update, it looks like with the CMOS error the PC ended up rolling back to the last stable point. I'm seeing that Windows is wanting me to reinstall the current update (the one that caused the problem to begin with).
Vagabond Superstar 0 Reputation points

2026-04-21T03:20:38.64+00:00

Okay, this is a bit weird. I thought it rolled back to the previous state before the update, but in the update history it's saying that it's already been installed:
Vagabond Superstar 0 Reputation points

2026-04-21T03:26:57.3233333+00:00

Reposting both pics. This was windows saying that the update needed to be installed:

And the update history saying that it was already installed today:
Ares 0 Reputation points

2026-04-21T03:34:34.17+00:00

Signed up just to be able to add some more anecdotes in an attempt to provide a bit more info so this can be fixed.

I don't have an AMD or pre-built system, but I do have one thing in common in regards to the NVIDIA GTX 1080ti and the exact same symptoms (endless recovery auto-repair boot loop, pixelated bluescreen type graphics). Uninstalling this update helps, but for the life of me I can't block it using dism in powershell or wushowhide.diagcab. Best thing I've tried to do is pause the updates, but I'm still not game enough to restart my PC to test it out (again - tried already).

Funnily (or depressing) enough, the update has somehow reinstalled itself according to windows update. That's after uninstalling the latest quality update (KB5083769) via the recovery tools and pausing the updates. To be clear, I paused the updates, then restarted and uninstalled again via recovery tools hoping to block it that way - low and behold it's still installed >.<

Really can't wait for game publishers to support linux completely so I can get away from this OS.

CPU: Intel i7 8700K

Mobo: Asus ROG STRIX Z370-E GAMING

GPU: NVIDIA GTX 1080Ti

RAM: 32GB
Brad 0 Reputation points

2026-05-04T00:38:18.46+00:00

I have an HP Envy Laptop that won’t boot. Windows Recovery doesn’t come up. The 3x hard restart advice doesn’t work. Using the esc key gets to a menu, but no options on the HP menu do anything useful for the boot issue. Boot from a USB doesn’t work to repair or do a fresh install. I can’t get ahold of anyone at Microsoft because it’s all chatbot AI generated garbage. The advice from ChatGPT doesn’t work. HP helpdesk and Geek Squad all agree that this was caused by Microsoft’s update and they are 100% responsible for all losses. They suggest buying a new computer. Being in school full-time, working full-time, and being a parent…this is devastating. Especially when my school projects were due and I have worked hard all semester. They also said the Intel chip with Optane prevents any data recovery. I eventually had to buy a new computer. I got it home and the screen was broken, so I drove back to get a replacement. I’ll add that to my list of losses.

5 answers

Your answer

L M 5 Reputation points

2026-04-17T21:33:32.3033333+00:00

Having exact same issue on Dell Desktop. Pixelated screen, attempts to update, gets to 30%, fails, reboots and then repairs as it indicates the update didn't succeed. Reboots back to state prior to loading the update.

How do we update? I am not able to do any future windows updates as its hung on this update!
Vagabond Superstar 0 Reputation points

2026-04-21T01:09:27.1333333+00:00

Ok, so after some time, fully disassembling my PC, cleaning it, putting back together, I restarted it.

It gave me the HP "CMOS checksum is invalid" screen. I hit enter to restart and my PC fully restarted on its own. I'm including a pic of the popup:

I don't know exactly what happened, but my PC is back up and running.

Checking the windows update, it looks like with the CMOS error the PC ended up rolling back to the last stable point. I'm seeing that Windows is wanting me to reinstall the current update (the one that caused the problem to begin with).
Vagabond Superstar 0 Reputation points

2026-04-21T03:20:38.64+00:00

Okay, this is a bit weird. I thought it rolled back to the previous state before the update, but in the update history it's saying that it's already been installed:
Vagabond Superstar 0 Reputation points

2026-04-21T03:26:57.3233333+00:00

Reposting both pics. This was windows saying that the update needed to be installed:

And the update history saying that it was already installed today:
Ares 0 Reputation points

2026-04-21T03:34:34.17+00:00

Signed up just to be able to add some more anecdotes in an attempt to provide a bit more info so this can be fixed.

I don't have an AMD or pre-built system, but I do have one thing in common in regards to the NVIDIA GTX 1080ti and the exact same symptoms (endless recovery auto-repair boot loop, pixelated bluescreen type graphics). Uninstalling this update helps, but for the life of me I can't block it using dism in powershell or wushowhide.diagcab. Best thing I've tried to do is pause the updates, but I'm still not game enough to restart my PC to test it out (again - tried already).

Funnily (or depressing) enough, the update has somehow reinstalled itself according to windows update. That's after uninstalling the latest quality update (KB5083769) via the recovery tools and pausing the updates. To be clear, I paused the updates, then restarted and uninstalled again via recovery tools hoping to block it that way - low and behold it's still installed >.<

Really can't wait for game publishers to support linux completely so I can get away from this OS.

CPU: Intel i7 8700K

Mobo: Asus ROG STRIX Z370-E GAMING

GPU: NVIDIA GTX 1080Ti

RAM: 32GB
Brad 0 Reputation points

2026-05-04T00:38:18.46+00:00

I have an HP Envy Laptop that won’t boot. Windows Recovery doesn’t come up. The 3x hard restart advice doesn’t work. Using the esc key gets to a menu, but no options on the HP menu do anything useful for the boot issue. Boot from a USB doesn’t work to repair or do a fresh install. I can’t get ahold of anyone at Microsoft because it’s all chatbot AI generated garbage. The advice from ChatGPT doesn’t work. HP helpdesk and Geek Squad all agree that this was caused by Microsoft’s update and they are 100% responsible for all losses. They suggest buying a new computer. Being in school full-time, working full-time, and being a parent…this is devastating. Especially when my school projects were due and I have worked hard all semester. They also said the Intel chip with Optane prevents any data recovery. I eventually had to buy a new computer. I got it home and the screen was broken, so I drove back to get a replacement. I’ll add that to my list of losses.

Answer 1

DaveM121 876.6K Independent Advisor

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Please try each option one at a time, then see if Windows will boot up correctly.

1

If there is an option to uninstall the update from there, that will be the best option.

2

Go to Troubleshoot - Advanced Option - System Restore

Check to see if you have a restore point you can go back to

Vagabond Superstar 0 Reputation points

2026-04-18T05:27:49.5766667+00:00

This is the same answer that the AI generator provided. Still working on seeing if that will work.
DaveM121 876.6K Reputation points Independent Advisor

2026-04-18T06:00:34.5966667+00:00

Just checking with you, how are you proceeding with this problem, are you now able to boot into Windows normally.
Vagabond Superstar 0 Reputation points

2026-04-18T12:02:59.9233333+00:00

Not yet. I'll report back tomorrow.
DaveM121 876.6K Reputation points Independent Advisor

2026-04-18T12:04:19.1066667+00:00

Okay, glad to help!
Vagabond Superstar 0 Reputation points

2026-04-21T00:15:01.13+00:00

Still not working. Any other suggestions?
Vagabond Superstar 0 Reputation points

2026-04-21T03:38:20.27+00:00

Update: The PC managed to restart on it's own, and now Windows is trying to push the same update thru again. I wish that there was a viable way to genuinely stop these updates and not just pause them, because having a PC bricked after a forced update isn't okay AT ALL.
DaveM121 876.6K Reputation points Independent Advisor

2026-04-21T05:04:28.61+00:00

For now, the best option is to pause your updates to stop that update installing.

In an upcoming update, Microsoft are adding a new feature that will basically allow people to pause updates indefinitely or for as long as is necessary on their devices.
JJ IT 5 Reputation points

2026-04-27T13:35:34.61+00:00

We’re seeing another failure mode on the same update/build: Windows 11 25H2 (26200.8246 / KB5083769) hard‑freezes during idle/unattended periods. Systems are not on a black screen — they’re stuck at the Windows lock screen with the clock frozen, no keyboard/mouse response, no crash dump, and only Event ID 41 after a forced power‑off. This looks like broader instability tied to KB5083769, not isolated hardware. We’re aggregating confirmations here (please add hardware + clean install vs upgrade if affected): https://learn.microsoft.com/en-us/answers/questions/5869124/

Answer 2

Thomas B 0

Having the same issue, 3 people in are company were no longer able to boot into Windows. I was able to uninstall the latest "Quality" update and get back in, but one of the users recovery environment is so messed up I can't get them into it.

0 comments

Answer 3

Had the same issue on a number of machines where we use SCCM to deploy updates. After alot of Googling & going through log files, found in the CBS.log (C:\Windows\Logs\CBS) that the system partition was full...
User's image

The WUAHandler.log (C:\Windows\CCM\Logs) was also showing this...

User's image

Ran through this process...

Open CMD prompt and "Run as Administrator"

At the command prompt, enter command "mountvol y:/s" then hit enter. (This will add the Y: drive letter to access the System Partition
Switch to the Y Drive by typing "Y:" then enter
navigate to the fonts folder by entering "CD EFI\Microsoft\Boot\Fonts"
in the fonts folder, enter command "del*.*" to delete font files.
If prompted, make sure to press Y and then enter if prompted to continue

Once completed kicked off the updates sync/install & the update completed successfully.

Answer 4

CrazyKats 15,580 Volunteer Moderator

Hi,

This build is now up to 26200.8313.

Vagabond Superstar 0 Reputation points

2026-04-18T05:26:05.0133333+00:00

Just released today for preview/gradual release (thanks for the heads up), but this doesn't help the issue that I'm dealing with from yesterday. Also, is there a mention of the newer build resolving the issue that I and others stated to be having?

Answer 5

The behavior matches a failed Windows update that leaves the system unable to boot and stuck in an automatic repair loop. Similar issues are documented when a cumulative/security update corrupts boot-critical components or drivers, especially on some AMD-based systems.

To get the PC back up and running, use the Windows Recovery Environment (WinRE) and, if needed, installation media to repair or roll back the update.

Force Windows into the Recovery Environment
1. Power on the PC.
2. As soon as the Windows or HP logo appears, press and hold the power button until the PC turns off.
3. Repeat this power-on/forced-shutdown cycle 2–3 times.
4. On the next start, Windows should display “Preparing Automatic Repair” and then show the WinRE screen.
Try System Restore first
1. In WinRE, select Advanced options.
2. Select Troubleshoot > Advanced options > System Restore.
3. Choose a restore point from before the KB5083769 installation and complete the wizard.
4. Let the system restart and check if it boots normally.
If System Restore is unavailable or fails
1. In WinRE, go to Troubleshoot > Advanced options.
2. Try Startup Repair and let it complete.
3. If Startup Repair does not resolve the loop, return to Troubleshoot.
Reset this PC (last resort if other options fail)
1. In WinRE, select Troubleshoot > Reset this PC.
2. Choose Keep my files to preserve personal data (installed apps and some settings will be removed), or Remove everything if a clean start is acceptable.
3. When prompted, choose Local reinstall.
4. Complete the reset and allow Windows to reinstall and reboot.
If WinRE does not appear automatically
1. On another working PC, create Windows installation media:
  - Go to the Microsoft software download website.
  - Download and run the media creation tool.
  - Select Create installation media for another PC and follow the steps to create a bootable USB.
2. Boot the HP from this USB (change boot order in firmware if needed).
3. On the setup screen, choose language and keyboard, select Next, then Repair your computer.
4. Use the same Troubleshoot options: System Restore, Startup Repair, or Reset this PC.

If none of these steps restore normal boot, a full reimage (clean installation of Windows using the installation media) may be required, similar to other cases where an update corrupts the system beyond repair.

References:

Share via

2026-04 Security Update (KB5083769) (26200.8246) causing failing boot loop

5 answers

Your answer