April Tuesday Patch (KB5083769) causes death loops

Five days ago, Microsoft released the April Patch Tuesday (KB5083769) and already users are starting to report more and more issues on Microsoft’s Q&A Learn pages. One of the issues that stands out is that a “death loop” has been reported by several users. It’s not known how many are experiencing this issue, but in addition to the user who posted it, one commenter reported that he is experiencing the same issue, as are three other people at his company.windows update sux

The user who wrote it (Vagabond Superstar) reported that he tried to install the April Patch Tuesday update, but his computer got stuck in a “death loop” (reboots with blue screens) where the screen displayed a “mosaic of strange pixels” followed by a blue screen saying that Windows needs to be recovered. The user was then given the option to try again, but when they tried, the computer went into a loop that continued to display the message that it was trying to fix the problem while then showing the screens with the pixels mentioned above.

Discover more articles in search results.

Vagabond Superstar reports that his computer is an HP Pavillion 590-p0044. It has an AMD Ryzen 5 2600 processor, 32GB of RAM, a GTX 1080ti GPU, and runs Windows 11 Home. Another commenter, going by the name “LM,” reported experiencing the exact same issue on a Dell desktop, describing the pixelated screen and everything else the original user mentioned.

The latest commenter to report the same issue was Thomas B, who said they are experiencing the same thing, as are three other people at their company who are no longer able to boot into Windows, potentially preventing them from accessing important work documents. Thomas B noted that they were able to uninstall the latest “Quality” update and get back into their system, but one of the users had a recovery environment that was so corrupted that they couldn’t get back into their system.

Microsoft's AI-powered Q&A Help recommends going into the Windows Recovery Environment, attempting System Restore, then Startup Repair, and then Local Reinstallation if the first two recommendations fail.

You can find her detailed response from the company in the comments section of the post.

follow us

Google preferences

Leave a Comment

Your email address is not published. Required fields are mentioned with *

Your message will not be published if:
1. Contains insulting, defamatory, racist, offensive or inappropriate comments.
2. Causes harm to minors.
3. It interferes with the privacy and individual and social rights of other users.
4. Advertises products or services or websites.
5. Contains personal information (address, phone, etc.).