
Understanding BitLocker Recovery Issues Caused by Windows 10 KB5058379
Windows 10 users are facing a significant challenge with the recent security update known as KB5058379, which has left many systems booting into Windows Recovery, prompting for a BitLocker recovery key. After installation attempts, users frequently encounter the message “Enter the recovery key to get going again (Keyboard layout: US)” with a field awaiting the key, and in some scenarios, a Blue Screen of Death (BSOD) manifests.
Typically, such automatic triggers for BitLocker recovery occur due to hardware changes or adjustments in BIOS settings. Concerns arose when many users reported that merely installing KB5058379 led to this state, with no explicit changes to hardware reported. The update is being deployed universally through Windows Update, affecting both individual users and enterprises.
This mandatory security update, first discussed in a post dated May 13, has now been linked with numerous boot issues encountered by users, especially as the effects seem to transcend previous expectations of stability following updates.
Despite Microsoft’s support documentation claiming a lack of widespread issues, user experiences increasingly suggest otherwise.
“Hello, are you aware of a KB5058379 causing the devices to lock for a BitLocker recovery key?”
Many reports detail users arriving at work to find their computers stuck demanding a BitLocker recovery key. The installation failure is often noted without triggering a BSOD, and users reported that entering the recovery key only led back to the update process, followed by subsequent returns to the login screen.

Reports of systems requiring BitLocker recovery due to KB5058379 are widespread, with discussions on platforms like Reddit confirming the trend. An observed thread indicated that many users encountered complexities not just related to recovery prompts, but also succumbing to BSOD errors.
Considered a critical security feature, it’s not advisable to bypass the installation of KB5058379, even though the likelihood of triggering a BitLocker Recovery screen remains high. Specifically, Windows 10 versions and devices reported to be affected include:
- Windows 10 22H2
- Windows 10 21H2 LTSC / Enterprise
- Devices from Dell, HP, and Lenovo
Notably, reports have emerged predominantly from users utilizing SCCM or WSUS protocols, suggesting that standard consumer PCs might evade such issues.
Steps to Resolve BitLocker Recovery Triggered by Windows 10 KB5058379
If you find your system halted at the Windows Recovery or specifically at the BitLocker Recovery screen with a prompt for a recovery key after KB5058379 installation, follow the steps outlined below:
- Reboot into BIOS/UEFI: Immediately press the designated key for your manufacturer (e.g., F2 for Dell, F10/F12 for HP, or Esc for Lenovo) right after powering on your computer to access BIOS/UEFI settings.
- Locate the Security Settings: Within the BIOS interface, navigate to “Security, ” then open the respective sections labeled “Virtualization” or “Advanced CPU Settings.”
- Disable Intel TXT: Turn off the setting named “Intel TXT, ” which may also appear under “Trusted Execution” or “OS Kernel DMA Support.”
- Keep VT Configuration ON: You can retain “VT for Direct I/O” (or “VT-d”) in the enabled state.
- Save and Exit: Conclude your adjustments by saving the settings and exiting the BIOS setup.
The aim here is to disable the Intel TXT / Trusted Execution option, allowing for the seamless completion of KB5058379 installation. Following these guidelines should prevent the recurrence of BitLocker Recovery prompts or BSOD experiences. Do note that while this update may instigate recovery prompts during installation, completing the installation should alleviate the problem.
Lastly, it’s worth noting that Windows 11 is currently unaffected by this issue, giving users of that operating system an additional layer of reassurance.
Frequently Asked Questions
1. What triggers BitLocker Recovery after installing KB5058379?
The automatic prompt for BitLocker Recovery often results from the installation of KB5058379, requiring no prior hardware or BIOS changes, leading to confusion among users.
2. Are all Windows 10 users affected by this update?
Not all users are impacted by KB5058379. Reports have indicated that primarily users of specific Windows 10 versions (22H2 and 21H2 LTSC/Enterprise) and particular devices (Dell, HP, Lenovo) are seeing these issues.
3. Will disabling Intel TXT ensure a successful installation of KB5058379?
Yes, disabling Intel TXT or Trusted Execution in BIOS is key to preventing BitLocker recovery prompts during the installation of KB5058379 while still enabling the security update successfully.
Leave a Reply ▼