Windows 10 KB5058379 update triggers BitLocker recovery on some devices

Windows 10 KB5058379 Cumulative Update Triggers BitLocker Recovery Prompts

The recent Windows 10 cumulative update KB5058379 has caused unexpected BitLocker recovery prompts for certain users after installation. Released on May 13, as part of Microsoft’s Patch Tuesday, this update includes critical security fixes for five actively exploited zero-day vulnerabilities. As reports of booting into WinRE recovery screens emerge from various users, the focus shifts to troubleshooting these issues while maintaining robust cyber security measures. Read on to explore the potential causes and solutions linked to this cumulative update.

Understanding the Issue: BitLocker Recovery Screen

What is BitLocker and Why is it Important?

BitLocker is a full-disk encryption feature included in Windows, designed to protect data by preventing unauthorized access to the operating system and file storage. By automatically prompting for recovery keys after certain system updates, BitLocker adds an extra layer of security against threats, such as unauthorized data access and potential data breaches.

Reports of Issues Following Update

Since the deployment of update KB5058379, multiple users have reported their devices booting into the Windows Recovery Environment (WinRE) and being prompted for BitLocker recovery keys. Notably, reports came from various hardware manufacturers, including Lenovo, Dell, and HP, raising questions about compatibility issues. One concerned user shared on Reddit, “We have about a half dozen laptops that experienced various intermittent issues after receiving the same KB—some require BitLocker keys to start up, others refusing to start at all.”

Troubleshooting Solutions for BitLocker Recovery Prompts

Steps to Resolve the Issue

While Microsoft has not fully acknowledged the issue, there are several recommended troubleshooting steps that can help users regain access to their devices:

1. Disable Secure Boot:
   • Access the BIOS/Firmware settings.
   • Locate the ‘Secure Boot’ option and set it to ‘Disabled.’
   • Save changes and reboot the device.
2. Disable Virtualization Technologies:
   • Re-enter BIOS settings.
   • Disable all virtualization options (Intel VT-d, Intel VT-x).
   • Be prepared to enter the BitLocker recovery key.
3. Check Microsoft Defender System Guard Firmware Protection Status:
   • Registry Method: Open Registry Editor, navigate to:
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\SystemGuard and check the Enabled DWORD value.
   • GUI Method: Open Windows Security > Device Security, and check under Core Isolation.
4. Modify Group Policy to Disable Firmware Protection:
   • Open Group Policy Editor (gpedit.msc).
   • Navigate to: Computer Configuration > Administrative Templates > System > Device Guard.
   • Set ‘Turn On Virtualization Based Security’ to ‘Disabled.’

Important Considerations

Tread carefully while disabling features such as Trusted Execution Technology (TXT) and Secure Boot. These features significantly enhance device security, so assess the implications on security and performance before making any changes.

Conclusion

In summary, the KB5058379 cumulative update has raised concerns regarding BitLocker recovery prompts on some devices. By taking practical steps, users can potentially regain access to their systems while continuing to uphold essential cyber security principles. Stay informed about ongoing updates and patches from Microsoft, as they are likely to provide a permanent solution in the near future.

FAQ

Question 1: What should I do if I can’t find my BitLocker recovery key?

The BitLocker recovery key is usually saved in your Microsoft account, a printed document, or a USB drive. If all else fails, consult your organization’s IT department for additional help.

Question 2: How can I prevent similar issues with system updates in the future?

Regular backups and maintaining a system restore point before applying updates can mitigate risks. Also, read change logs from Microsoft to stay informed about known issues related to updates.

Question 3: Are there any ongoing fixes from Microsoft regarding this update?

As of now, Microsoft’s support team is aware of the issues and is working on a permanent resolution. Check their official channels for updates.

Read the original article