Windows 10 KB5058379 Update Triggers BitLocker Errors and BSODs

Once again, Microsoftโ€™s engineers have found themselves in hot water. A recent Windows 10 updateโ€”KB5058379โ€”is causing headaches for users worldwide, with many reporting unexpected BitLocker recovery screens and even the dreaded Blue Screen of Death (BSOD) after installation.

The latest Windows 10 update – KB5058379 – was released on May 13, as part of Microsoftโ€™s May 2025 Patch Tuesday updates.

However, it appears that this mandatory security update, meant to address serious security threats (some of which are under active attack), has created problems for those who have downloaded and installed it on their systems. Instead, it is causing a sudden demand for a BitLocker recovery key and, in some cases, even BSODs after updating.

BitLocker Blues

One of the most common issues being reported involves BitLocker, Microsoftโ€™s built-in disk encryption tool. After installing KB5058379, several users say their devices unexpectedly boot into Windows Recovery or require BitLocker recovery keys ubiquitously following the update installation, including Reddit, even if no changes were made to hardware or system settings that would normally trigger it.

“โ€œEnter the recovery key to get going again (Keyboard layout: US),โ€ effectively locking them out unless they can provide the BitLocker recovery key,” reads the screen after users complete the update installation.

โ€œThis update was supposed to be routine,โ€ said one frustrated user on Reddit. โ€œInstead, I came back from a coffee break to find my PC locked behind a BitLocker screen. I didnโ€™t even enable it!โ€

Blue Screen Of Death Woes

In addition to BitLocker blues, some users are also experiencing spontaneous BSOD crashes either during or immediately after the update process. Multiple hardware vendorsโ€”including Dell, HP, and Lenovoโ€”have confirmed that users are experiencing BSOD errors, often followed by unexpected BitLocker recovery prompts, says Windows Latest, based on reports seen by them.

Further, devices running Windows 10 22H2, 21H2 LTSC, and Enterprise editions are at higher risk, especially those managed via SCCM or WSUS.

โ€œWe had 1 BSOD on a Dell Precision 3660 right after applying the cumulative update to 24H2. Uninstalling didnโ€™t help. BSOD approximately 6 minutes after reboot, consistently. Event log had some issues with Dell Supportassist so I uninstalled the 4 programs, and fine after that,โ€ warned oneย Redditor.

โ€œSeeing an issue with Win10 22H2 19045.5854 – KB5058379. BSOD after updating. Disabling VT for Direct I/O in BIOS virtualization settings allows the computer to boot again, but not a real ‘fix’ for why this is happening. Opened a ticket with Microsoft and will update when I hear back,โ€ another user reported.

Microsoft’s Response

Microsoft is aware of the bug in KB5058379, and preliminary investigations indicate that it predominantly affects Intel-based devices with the TXT (Trusted Execution Technology) feature in BIOS enabled.

However, the company is conducting further investigations and is actively working on a permanent solution.

Meanwhile, one can temporarily mitigate the problem by disabling the TXT feature in the BIOS. Also, users can continue to keep affected devices with the update installation paused. Additionally, for affected devices requiring BitLocker recovery, the recommended interim solution is to enter the recovery key and roll back the update.

Kavita Iyer
Kavita Iyerhttps://www.techworm.net
An individual, optimist, homemaker, foodie, a die hard cricket fan and most importantly one who believes in Being Human!!!
spot_img

Read More

Suggested Post