Earlier, we lined a brand new BitLocker-related hassle on Home windows PCs wherethe newest Might 2025 Patch Tuesday replace is main gadgets right into a BitLocker restoration and reboot frenzy. This follows an earlier report for Home windows 11 24H2, whereby unaware customers could also be shedding their information on account of the default encryption.

From its preliminary investigation, Microsoft realized {that a} battle with Intel TXT (Trusted Execution Know-how) is the foundation of the problem, although, at the moment, an in depth clarification was not offered. Nonetheless, it led to a easy workaround for the BitLocker restoration and reboot concern by going into the BIOS of affected Intel-based PCs and disabling the TXT function there.

For these not acquainted, Intel TXT is a safety function constructed into Intel processors and chipsets. It helps defend computer systems from software program assaults by making certain that purposes run in a protected, remoted area. TXT makes use of hardware-based safety to maintain information safe and incorporates options like Intel PTT (or generally referred to as TPM) and Safe Boot.

After additional investigation, as promised, Microsoft has printed a brand new entry on its Home windows Well being Dashboard web site. The corporate says {that a} battle between Intel’s TXT function and its newest KB5058379 Home windows 10 Patch is resulting in the lsass.exe course of termination and that’s basically what’s triggering the Computerized Restore of such affected techniques.

That is as a result of the Native Safety Authority Server Service (LSASS) course of helps validate and authenticate customers for native and distant sign-ins by implementing native safety insurance policies. This helps clarify why techniques are going right into a BitLocker restoration frenzy as Intel TXT and LSASS will not be taking part in nicely with each other.

When this occurs, Microsoft has defined that affected gadgets react in certainly one of two methods. On the brighter facet, the system may make a number of makes an attempt to put in replace KB5058379 earlier than Startup Restore manages to efficiently roll it again to the earlier (secure) replace; however on the flip facet when it fails, it creates a reboot loop.

Other than these, Microsoft has additionally listed a few different signs:

• Occasion ID 20 may seem within the Home windows Occasion Viewer within the System occasion log, with the next textual content: “Set up Failure: Home windows failed to put in the next replace with error 0x800F0845: 2025-05 Cumulative Replace for Home windows 10 22H2 for x64-based Programs (KB5058379).”
• Occasion ID 1074 may seem within the System occasion log, with the textual content: “The system course of ‘C:WINDOWSsystem32lsass.exe’ terminated unexpectedly with standing code -1073740791.”

The corporate says it’s engaged on a repair for this bug on an pressing foundation, and thus, an out-of-band replace, much like the one for Home windows 11 24H2, will likely be launched quickly. You will discover the problem entry right here on Microsoft’s official Home windows Well being Dashboard web site.