Windows 11, the April update is a disaster: PCs in 'death loop' and other problems
The release of the April 2026 Patch Tuesday (identified by code KB5083769) is generating a series of high-profile technical issues, putting some Windows 11 systems in a state of total instability. Just five days after the rollout, reports on Microsoft Learn Q&A support pages describe critical scenarios where the update process ends up in what users have dubbed a "death loop." This phenomenon does not seem limited to isolated cases, but is affecting various hardware configurations, preventing access to the operating system and, in some cases, rendering even the built-in diagnostic tools ineffective.
The reported symptoms follow a recurring and decidedly bizarre pattern: before the final lock-up, the screens display a mosaic of distorted pixels, a kind of graphical corruption that precedes the loading of the blue recovery screen. Once in this state, PCs automatically attempt a repair, systematically failing and rebooting in an infinite cycle. This sequence effectively prevents any standard interaction with the user interface, freezing the machines at a pre-boot stage that is difficult to escape from without advanced manual interventions.
KB5083769: The April update crises Windows 11
Although the exact extent of the bug's spread has not yet been quantified by Microsoft, technical reports highlight specific configurations affected by the problem. One detailed case involves an HP Pavilion 590-p0044, equipped with an AMD Ryzen 5 2600 processor, 32 GB of RAM, and an NVIDIA GTX 1080ti GPU. However, the issue does not appear to be limited to HP systems alone; configurations based on Dell Desktop hardware have manifested identical errors, suggesting a deeper criticality related to driver management or essential boot components.
Microsoft's AI-based assistant (Q&A Assist) has hypothesized that the cumulative security update may have corrupted critical boot components, particularly impacting AMD architecture-based systems. The corruption of the system files necessary for the boot phase would explain why the PC, while attempting to restore, fails to find a valid configuration to stabilize the kernel and load the video drivers, leading to the display of the artifacted pixels mentioned by users.
For users facing a blocked system, the situation appears complex but not always irreparable. Some witnesses, such as user Thomas B, have managed to restore functionality by accessing the recovery environment and proceeding with the manual uninstallation of the latest "Quality Update." This procedure physically removes the package KB5083769, allowing the system to revert to the previous build. However, not everyone has been so lucky: in some cases, the recovery environment (WinRE) is itself compromised and does not allow access to uninstallation options or the command prompt.
The official recommendations in these extreme cases involve a series of sequential steps: initially attempting a System Restore to a point before the installation of the patch, proceeding with Startup Repair, and, as a last resort, performing a local reinstallation of the operating system. There remains a tangible risk of immediate loss of access to work documents, as reported by several companies that have seen entire departments frozen due to the inability to surpass the login phase. An official communication or corrective fix that can contain the problem without forcing users to undertake formatting procedures is currently awaited.