Is the May 2025 Windows 10 Update Causing BitLocker Lockouts and BSODs? Here’s How to Fix It Fast

Troubled by the Latest Windows 10 Update? Solve BitLocker and BSOD Headaches with These Proven Steps

The Windows 10 update KB5058379, released on May 13, 2025, is a mandatory security patch addressing several critical vulnerabilities. However, after installation, many users and IT administrators have reported two major problems:

• Unexpected BitLocker Recovery Prompts: Devices request the BitLocker recovery key at boot, even if no hardware changes have occurred.
• Blue Screens of Death (BSODs): Some systems crash with a BSOD after the update, sometimes repeatedly, making normal use impossible.

These issues have been reported across multiple hardware brands, including Dell, HP, and Lenovo, and are not limited to a single manufacturer or device model.

Why Is This Happening?

The update appears to alter certain system parameters or BIOS/UEFI flags, which BitLocker interprets as a potential security risk, triggering the recovery prompt. Minor changes to boot configuration or virtualization settings may also contribute to the issue. The BSODs are often linked to virtualization and security settings in the BIOS, such as Intel Trusted Execution Technology (TXT) and VT for Direct I/O.

Who Is Affected?

Primarily Windows 10 22H2 users; some reports mention Windows 11, but the majority of cases involve Windows 10. Both enterprise and individual users have experienced these problems, with incident rates ranging from 2% to 5% of devices in some organizations.

Practical Solutions and Workarounds

Disable Intel Trusted Execution Technology (TXT) in BIOS/UEFI

This is the most widely reported workaround. Disabling TXT allows the update to install and the system to boot normally.

Disable Secure Boot or Virtualization Technologies

If disabling TXT does not resolve the issue, try turning off Secure Boot or virtualization features such as VT for Direct I/O.

Obtain and Use Your BitLocker Recovery Key

If prompted, enter your BitLocker recovery key to regain access. For enterprise users, IT can usually provide this. Home users should check their Microsoft account, printouts, or USB backups.

Suspend or Delay the Update

If possible, temporarily pause the deployment of KB5058379 in enterprise environments using WSUS, SCCM, or Intune until Microsoft provides a permanent fix.

Re-enable Security Features After Update

After successful installation and reboot, you can try re-enabling the BIOS security features to restore your system’s original security posture.

Monitor for Official Fixes

Microsoft is aware of the problem and is reportedly working on a resolution, but as of now, no official patch has been released.

Additional Notes

• Some users reported persistent errors, such as “Unknown NTSTATUS Error code: 0xc0290122,” during failed boot attempts.
• In rare cases, uninstalling conflicting software (e.g., Dell SupportAssist) resolved BSODs.
• The update is critical for security, so skipping it is not recommended without a mitigation plan.