BitLocker recovery Archives

Winsage

May 17, 2025

Why Windows 10 PCs are locking up and crashing after May update

Microsoft will end update support for Windows 10 in October 2025, but new patches are still being released. The latest cumulative update, KB5058379, has caused issues for users, especially those with devices from Dell, Lenovo, and HP. Microsoft is aware of the problems and has not yet deployed a fix as of May 16, but has provided a temporary workaround. For users affected by the BitLocker bug, Microsoft Support recommends the following steps to regain access: 1. Disable Secure Boot in BIOS/Firmware settings. 2. If issues persist, disable all virtualization technologies in BIOS/Firmware settings. 3. Check the Microsoft Defender System Guard Firmware Protection Status via Registry Editor or GUI method. 4. If firmware protection settings are restricted by Group Policy, disable them using Group Policy Editor or Registry Editor. A system restart is required for these changes to take effect, and these workarounds should only be temporary until a patched update is released. Disabling certain BIOS settings may compromise system security.

Winsage

May 16, 2025

Microsoft confirms May Windows 10 updates trigger BitLocker recovery

Microsoft has acknowledged an issue affecting some Windows 10 and Windows 10 Enterprise LTSC 2021 systems after the installation of the May 2025 security update (KB5058379), causing devices to boot into BitLocker recovery mode. This problem arises when the update leads to multiple startup failures, preventing the system from initiating Automatic Repair without the recovery key. Users experiencing this issue may see LSASS errors and the 0x800F0845 error code in the Windows Event Viewer. Reports indicate that various devices from manufacturers like Lenovo, Dell, and HP are affected. Microsoft suggests troubleshooting steps such as disabling Intel Trusted Execution Technology, Secure Boot, Virtualization Technologies, or Firmware Protection. This is not the first occurrence of such issues, as similar problems were reported after previous updates in August 2024 and August 2022.

Winsage

May 16, 2025

Windows 10 PCs are locking and crashing after May’s security update

Microsoft's KB5058379 update has caused issues for Windows 10 users, prompting unexpected requests for the BitLocker recovery key during startup. This problem is affecting users in Germany and the United States, impacting both corporate and personal devices. Users without the recovery key find their systems locked, leading some to perform system recoveries. Additionally, some users experience blue screen crashes after booting into Windows 10. A potential workaround is to disable the “Intel Trusted Execution Technology (Intel TXT)” option in the BIOS/UEFI. The issue primarily affects devices from Dell, HP, and Lenovo running Windows 10 versions 22H2 or 21H2 Enterprise. Microsoft has not yet acknowledged these issues related to the update.

Winsage

May 16, 2025

Microsoft released one of its final updates for Windows 10 — and it has broken things

Microsoft is winding down support for Windows 10 this October and has released update KB5058379, which has caused unexpected BitLocker recovery prompts for some users after a restart. This issue has been confirmed by Microsoft representatives on forums, although it is not mentioned in the update's release notes. The problem predominantly affects devices from manufacturers like Dell, HP, and Lenovo, and the specific cause is unclear. Microsoft has provided workarounds, including disabling Secure Boot and virtualization technologies, checking Microsoft Defender System Guard Firmware Protection status, and disabling firmware protection via Group Policy or Registry Editor.

Winsage

May 16, 2025

Microsoft Update Fails—New Download Breaks Windows

Users are experiencing BitLocker Recovery screens and Blue Screens of Death (BSOD) after installing the Windows 10 update KB5058379. This mandatory update addresses significant security vulnerabilities, but Microsoft claims to be unaware of any new issues. Some users have found that disabling Intel TXT can help complete the installation. Reports include a user experiencing consistent BSODs after the update and another who resolved boot issues by changing BIOS settings. The end of support for Windows 10 is approaching on October 14, but Microsoft 365 applications will still receive security updates afterward. Windows 11 users are not affected by these issues.

Winsage

May 16, 2025

Windows 10 KB5058379 update triggering BitLocker Recovery after install

The Windows 10 KB5058379 cumulative update, released on May 13, 2025, has caused unexpected BitLocker recovery prompts for some users after installation and reboot. Reports indicate that affected devices, including those from Lenovo, Dell, and HP, automatically boot into the Windows Recovery Environment and display the BitLocker recovery screen. Users have experienced various issues, such as needing BitLocker keys to start up or devices refusing to start. A workaround involves disabling Intel Trusted Execution Technology (TXT) in the BIOS. Microsoft has not publicly acknowledged the issue but support representatives are aware and working on a resolution. Microsoft has provided steps to resolve the issue, including disabling Secure Boot and virtualization technologies, checking Microsoft Defender System Guard Firmware Protection status, and disabling firmware protection via Group Policy or Registry Editor.

Winsage

May 15, 2025

The latest Windows 10 update is reportedly causing havoc on some people’s PCs

Users are experiencing challenges following the deployment of Windows 10 update KB5058379, including unexpected requests for a BitLocker recovery key and Blue Screen of Death (BSOD) errors. The BitLocker issue has a low occurrence rate of 2-5%, with reports indicating that only 15 out of 600 devices in some organizations were affected. Adjusting certain BIOS settings may help mitigate BSOD errors. Delaying or rolling back the update could expose systems to vulnerabilities, as it addresses critical zero-day exploits. Many issues arise from the update not completing its installation effectively, and users have reported resolutions once the update is fully realized. Users are advised to contact Microsoft for assistance and consider alternatives like Linux distributions as the October end-of-support date for Windows 10 approaches.

Winsage

May 6, 2025

BitLocker is Locking Out Windows 11 Users; Here’s How to Recover and Prevent It

Microsoft's Windows 11 24H2 update enables BitLocker (Device Encryption) by default, encrypting the entire drive to protect user data. BitLocker is automatically activated during a clean installation when users sign in with a Microsoft account, and manufacturers will have it enabled by default on new PCs with this version. Microsoft has relaxed certain hardware requirements to increase accessibility. Users have reported being locked out of their PCs due to a lack of communication about BitLocker's activation process. The BitLocker recovery key can be found by signing into the Microsoft account linked to the PC at account.microsoft.com/devices/recoverykey. To disable BitLocker, Windows 11 Home users can go to Settings > Privacy & Security > Device Encryption, while Pro users can search for Manage BitLocker in the Start menu. To prevent automatic BitLocker encryption during installation, users can modify settings in the Registry Editor.

Winsage

May 2, 2025

Windows 11 24H2: BitLocker Encryption Now Default

With the rollout of Windows 11 24H2, BitLocker and Device Encryption are now automatically activated by default for all editions, including Home. Microsoft enabled BitLocker without prior notification, raising concerns about drive performance and potential data loss if users lose access to their Microsoft accounts. Users can back up BitLocker recovery keys and disable encryption during installation using tools like Rufus. To turn off BitLocker in Windows 11, users can go to the Settings app, select Device encryption under Privacy & Security, and manage their encryption settings.

Winsage

March 30, 2025

Microsoft’s killing script used to avoid Microsoft Account in Windows 11

Microsoft has removed the 'BypassNRO.cmd' script from the Windows 11 Insider Dev preview build to enhance security and user experience, requiring users to log in with a Microsoft Account during installation. This change reflects Microsoft's ongoing emphasis on using a Microsoft Account since the launch of Windows 11, making it difficult to set up the operating system with a local account. Users previously used the script to bypass this requirement by creating a Registry value that allowed them to proceed without an internet connection. Although the script is no longer available, the BypassNRO Registry value remains intact, and users can still achieve the same outcome by manually modifying the Windows Registry. However, there is a possibility that Microsoft may disable this Registry value in the future.