May 13 -KB5058379 Windows 10 leads to corruption and endpoints asking for bitlocker key,.- Any known issues?

Microsoft has added it to the Windows 10 22H2 known issues

https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2#3555msgdesc

@MersonZZ

I'm a normal user too.
Unfortunately I have not seen any official MS communication yet.........

We have about 1800 Devices registered to Intune. We've had at least 70 with the bitlocker key issue. It asks every time the user reboots. Every device is running Windows 10.0.19045.5737.

Some devices update fine with no issues.

Windows 11 doesn't seem to be an issue at this point.

I cannot recreate this issue in a test environment.

We have paused all of our Update Rings in Intune.

I have opened a ticket with Microsoft and they have not responded.

This is what I've got by raising a support call via our corporate support partner:

**Issue Summary:**  
After installing update KB5058379 on certain Precision 5570 and 5680 models, users are being prompted for BitLocker recovery keys and encountering restart loops. This issue does not affect Latitude 3540 and 3520 devices. Attempts to uninstall the update or pause updates have not resolved the problem.

**Current Status:**  

• The issue has been identified as a known problem with the May Patch (KB5058379) on certain Windows 10 devices, specifically where the update appears to corrupt a recently serviced boot binary and triggers BitLocker recovery.
• Some users enter restart loops, fail to apply the update, and subsequently roll back, while being repeatedly prompted for BitLocker recovery.
• The problem is currently under investigation by the Product Group team, with active engagement from customers to provide crash dumps and logs for deeper analysis.
• Disabling the TXT (Trusted Execution Technology) feature in BIOS has been reported as a potential workaround by some, although it may require additional user intervention and is not a permanent solution.
• Initial investigations suggest the issue predominantly affects Intel-based devices with the TXT feature enabled.

**Next Steps & Recommendations:**  

• Continue to keep affected devices with update installation paused.
• For devices already affected and requiring BitLocker recovery, applying the recovery key and rolling back the update as you described is the advised interim measure.
• Disabling TXT in BIOS is another possible workaround, but as you noted, it may require remote staff to come in and is not ideal for large deployments.
• Microsoft is working to document the issue on the Windows Release Health and Microsoft 365 Admin Center portals; updates will be provided as new information becomes available.

@Ṣmeed - Should we expect a out of the band patch? Is there any official communication from Microsoft?