The April 2026 cumulative KB5083769 (builds 26200.8246 and 26100.8246) is throwing a subset of Windows 11 machines into a death loop: mosaic or pixelated artifacts on screen, a bugcheck, then automatic repair that fails and restarts the cycle. HP and Dell business fleets are taking the bulk of the hits. Microsoft has not pulled the update, so you fix it by ripping the patch out.

Boot into Safe Mode if the machine still gets to the login screen. If it does not, use WinRE (Windows Recovery Environment) to uninstall the update offline.

Get Into Safe Mode

If you can reach the sign-in screen, hold Shift while clicking Restart. Otherwise, power-cycle the PC three times at the Windows logo to force WinRE. Then:

Troubleshoot > Advanced options > Startup Settings > Restart > 4 (Safe Mode)

Log in, then remove the update:

wusa /uninstall /kb:5083769 /quiet /norestart
shutdown /r /t 0

Uninstall Offline From WinRE

If Safe Mode refuses to load, stay in WinRE and open a command prompt from Troubleshoot > Advanced options > Command Prompt. Find your Windows drive letter:

diskpart
list volume
exit

Then pull the package directly with DISM. Replace C: with your actual Windows drive if different:

dism /image:C:\ /get-packages /format:table | findstr 5083769

Copy the full Package_for_KB5083769~... identifier, then remove it:

dism /image:C:\ /remove-package /packagename:Package_for_KB5083769~31bf3856ad364e35~amd64~~26100.8246.1.10

Reboot. The machine should come up without the update.

Block the Update From Reinstalling

Until Microsoft ships a fix, pause updates so Windows Update does not redeploy KB5083769:

Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" `
    -Name "PauseUpdatesExpiryTime" -Value (Get-Date).AddDays(14).ToString("yyyy-MM-ddTHH:mm:ssZ")

If you manage the fleet, push a WUfB deferral or use wushowhide.diagcab to hide the KB on individual machines.

Verify

Confirm KB5083769 is gone:

Get-HotFix -Id KB5083769

Expected output: Get-HotFix : Cannot find the requested hotfix.

Check your current build is back below the broken build:

[System.Environment]::OSVersion.Version

Anything below 26100.8246 means the rollback worked.

Need help staging Patch Tuesday updates across a multi-site fleet before they nuke half your desktops? Contact Rain City Techworks.