Ddos 
BitLocker recovery screen
Yesterday, we reported that Microsoft’s May routine updates caused some Windows 10/11 devices to reboot into the Microsoft BitLocker recovery interface. Upon investigation, Microsoft identified the root cause as a compatibility issue with Intel’s Trusted Execution Technology (Intel TXT), a security feature that interfered with the proper installation of the update.
Specifically, this issue affects systems equipped with Intel’s 10th-generation and later vPro processors that have Intel TXT enabled—typically found in security-conscious commercial devices. To address the problem, Microsoft has released an emergency out-of-band update, KB5061768, targeting Windows 10 versions 21H2 and 22H2. After installation, system builds will be updated to Windows 10 Build 19044.5853 and Build 19045.5853 respectively.
According to Microsoft’s release notes: “A known issue on devices with Intel Trusted Execution Technology (TXT) enabled on 10th generation or later Intel vPro processors. On these systems, installing the May 13, 2025, Windows security update (KB5058379) might cause the Local Security Authority Subsystem Service (LSASS) process to terminate unexpectedly, triggering an Automatic Repair prompting for the BitLocker recovery key to continue.”
For systems already caught in the BitLocker recovery loop, the following workaround is advised:
Access the BIOS/UEFI settings and temporarily disable Intel I/O virtualization technologies (including Intel VTD and Intel VTX), as well as Intel TXT. Note: Disabling these settings may also require entering the BitLocker recovery key to proceed.
Once these technologies are disabled, reboot into Windows 10 and install the out-of-band update KB5061768. After the update installation and system reboot are complete, you may re-enter BIOS/UEFI and re-enable Intel VTD, VTX, and TXT.
This update has a known issue:
There is a display rendering problem involving the fallback font “Noto” in Windows 10. When the display scaling is set to 100% (96 DPI), text in CJK (Chinese, Japanese, Korean) characters may appear blurry in Chrome, Microsoft Edge, and other Chromium-based browsers. As a temporary workaround, users can set the scaling to 125%.
Donate