[German]With the Windows 10 22H2 update of May 13, 2025, there was the problem that numerous systems got stuck in WinRE with a request for the Bitlocker recovery key. When the key was entered, some systems entered a boot loop. Microsoft has released an out-of-band update on May 19, 2025, which should fix the problems.
The Bitlocker problem from May 2025
Update KB5058379 for Windows 10 22H2 from May 13, 2025 has caused quite a few problems for some users and administrators. On some machines, Windows 10 was locked after installing the update because the system requested the Bitlocker recovery key on boot and got stuck. Some affected users reported that Windows entered a boot loop after entering this key.
I reported in the blog post Windows 10/11: May 2025 updates triggers Bitlocker Recovery and BSODs. In the meantime, I have also received reports from blog readers that Windows 11 is also affected. Microsoft subsequently confirmed this problem (see my blog post Microsoft confirms Bitlocker boot problems after Windows 10/11 May 2025 update) and booting is not possible without this BitLocker recovery key. This key should be stored in the Microsoft account used to activate Bitlocker. Microsoft has no way of restoring or determining the key in Windows.
As of May 16, 2025, Microsoft confirmed in the Windows Release Health dashboard of Windows Server 10 22H2 via support article Windows 10 might repeatedly display the BitLocker recovery screen at startup that after installing the May 2025 update (KB5058379), Windows 10 22H2 may display the BitLocker recovery screen and may enter a boot loop. Microsoft blames the problem on devices with Intel Trusted Execution Technology (TXT) enabled when using 10th generation Intel vPro processors.
Out-of-Band Update KB5061768
As of May 19, 2025, Microsoft has updated the support article Windows 10 might repeatedly display the BitLocker recovery screen at startup and writes that the problem is solved by the special update (out-of-band update) KB5061768. This out-of-band update (OOB) KB5061768 is only available via the Microsoft Update Catalog.
The further procedure then depends on the circumstances. If you are affected by the Bitlocker problem on systems with the above-mentioned Intel vPro processors of the 10th generation under Windows 10 22H2 or Windows 10 Enterprise LTSC 2021, the update must be downloaded from the Microsoft Update Catalog and installed manually.
If the Windows security update from May 13, 2025 has not yet been installed, or if the installation of KB5058379 has failed, Microsoft recommends installing the OOB update KB5061768 directly.
If the system can no longer boot due to the installed KB5058379 update, Microsoft recommends temporarily disabling Intel VT for Direct I/O (also known as VTD or VTX) and Intel Trusted Execution Technology (TXT) in the BIOS/UEFI settings. Windows 10 should then boot again and, after entering the Bitlocker Recovery Key, also boot successfully to the desktop.
Then download the update KB5061768 from the Microsoft Update Catalog and install it manually. After restarting Windows 10, Intel VT for Direct I/O (also known as VTD or VTX) and TXT must be reactivated in the BIOS / UEFI settings. This step requires the BitLocker recovery key to be entered.
Booting is not possible without this BitLocker recovery key. This key should be stored in the Microsoft account with which Bitlocker was activated. Microsoft has no way of restoring or determining the key in Windows.
I have received reports from Windows 11 users that they are also affected. There is neither a confirmation from Microsoft nor a special update. And German blog reader Fritz asks in this comment whether anyone has already successfully tested the special update and the bug has been fixed?
Similar articles:
Microsoft Security Update Summary (May 13, 2025)
Patchday: Windows 10/11 Updates (May 13, 2025)
Patchday: Windows Server-Updates (May 13, 2025)
Patchday: Microsoft Office Updates (May 13, 2025)
Windows 10/11: May 2025 updates triggers Bitlocker Recovery and BSODs
Microsoft confirms Bitlocker boot problems after Windows 10/11 May 2025 update
