MAI update ensures BSOD risk and Bitlocker chaos
The MAI update KB5058379 for Windows 10 causes significant problems with some users. Affected systems suddenly request Bitlocker keys or show BSODs. However, a temporary solution via the BIOS settings can help.
May update for Windows 10 blocks systems
This week Microsoft took care of his Windows 10 users. In addition to the announcement that the support for office apps will be extended by 2028, the company also published an optional update for Windows 10, which, among other things, fixes an error in account synchronization. There was also a new version of the operating system for the Patch Day on May 13th.
However, the available cumulative update KB5058379 for Windows 10 version 22H2 causes serious problems for Windows 10 version 22H2. The update should actually offer important security improvements. But in addition, many users experience a nasty surprise after installing KB5058379. Because their systems sometimes no longer boot normally and suddenly request Bitlocker recovery keys or show BSODs.
The problem is particularly noticeable in corporate environments. Users report on Born’s IT and Windows blog that the update installation for Windows 10 clients fails, a rollback takes place and the system then requires a recovery key to start. In some cases, affected computers end up in an endless Windows Recovery Environment (WinRe) boot loop from which only a system recovery helps to a time before update installation.
Cause of the problems
The current problem with the May Update may be related to the interaction between Bitlocker and the virtualization functions in BIOS, especially with Intel TXT. This technology is designed for the safe execution of code, but seems to be in a conflict in connection with the update KB5058379 that triggers the symptoms described.
There were some weak points in the Microsoft Defender, Windows driver, in the Universal Print Management Service, at Bitlocker and in the disclosure. The update KB5058379 should actually close these security gaps, but now leads to the difficulties described by incompatibility with the BIOS settings.
Transitional solution via BIOS settings
How Windows Latest reported, the problem of Dell, HP and Lenovo with Windows 10 22H2 and Windows 10 21h2 Enterprise/LTSC are affected. The difficulties probably occur mainly in systems that are managed via SCCM or WSUs, which indicates that private users could be rarely confronted with the error.
As a temporary solution, some users recommend deactivating the “Intel Trusted Execution Technology (Intel TXT)” option in BIOS/UEFI. Depending on the manufacturer, this can also be called “Trusted Execution” or “OS Kernel DMA Support”. After this change, the update can usually be successfully installed without Bitlocker recovery inquiries or BSODs.
What can affected users do?
If users are confronted with a Bitlocker recovery request after installing the update, you need your Bitlocker recovery key. In corporate environments, this is usually managed by the IT department. Private users often find their key in their Microsoft account if they have activated the backup there. After entering the recovery key, it is advisable to also change the BIOS change described above in order to avoid further problems.
Since the update contains important security improvements, a complete waiver of installation is not advisable.
Digital marketing enthusiast and industry professional in Digital technologies, Technology News, Mobile phones, software, gadgets with vast experience in the tech industry, I have a keen interest in technology, News breaking.
1 thought on “MAI update ensures BSOD risk and Bitlocker chaos”
Comments are closed.