Technology

Windows 10 Patch Nightmare: Users Encounter Recovery Loops!

2025-05-19

Author: Wei Ling

As the Microsoft Build developer conference kicks off, a slew of Windows 10 users are dealing with a distressing déjà vu: their operating systems are once again malfunctioning.

Broken Updates: What's the Cause?

The latest trouble affects Windows 10 versions 22H2 and Enterprise LTSC 2021, leaving those hoping to sidestep looming support issues deeply frustrated.

If users with Intel’s Trusted Execution Technology enabled on newer processors installed the infamous KB5058379 patch released on May 13, they better keep their BitLocker recovery key handy.

The Fallout: What Happens Next?

According to Microsoft, the patch can cause the critical lsass.exe process to terminate unexpectedly, leading to automatic repairs and potentially an endless reboot loop. This results in users getting stuck on the BitLocker recovery screen.

The company noted, "Consumer devices typically do not use Intel vPro processors and are less likely to be impacted by this issue," providing little solace to system admins scrambling for recovery keys.

Microsoft's Double Whammy: Layoffs and Buggy Updates

On the same day as this disruptive update, Microsoft announced significant layoffs, further straining resources at the tech giant.

While the company claims they are working on a fix and intend to issue an emergency update shortly, the urgency is palpable.

Temporary Measures: Proceed with Caution!

In the meantime, various workarounds have surfaced on social media, including disabling Trusted Execution Technology. However, this could expose systems to serious security vulnerabilities, as Intel explains that this feature helps to create a safeguarded environment for applications.

The Dilemma: Update or Wait?

Administrators find themselves in a precarious situation. Delaying the update means missing out on crucial fixes, yet applying it risks rendering machines unusable due to this latest oversight.

As The Register awaits a timeline for resolution from Microsoft, one thing is clear: users are left grappling with yet another example of the tech giant's inadequate testing practices.