Shulou(Shulou.com)11/24 Report--

CTOnews.com August 20 news, Microsoft confirmed last week that the KB5012170 update will cause some problems, mainly because the Secure Boot DBX security update cannot be installed. Later, more users reported that this is not the only problem, there are some other BitLocker-related Bug.

A large number of users launch to the BitLocker recovery interface after installing the update. According to user feedback from The Register and Microsoft Forum, Reddit and Twitter, Windows 11 prompts users to enter the recovery key on the BitLocker recovery interface. It is not known whether other versions of Windows are also affected.

According to preliminary findings, this issue will not affect the stored data, which means that users can regain control of PC by entering a key stored in a Microsoft account or active directory.

In addition, there are user feedback that after installing KB5012170, the system will change the hard drive configuration from RAID to AHCI. As with BitLocker issues, users can change their systems back to RAID without losing data. At present, however, the problem of secure startup DBX is still the only recognized problem.

Microsoft said KB5012170 updated its database DBX after a security vulnerability in the system that allowed attackers to bypass secure startup and load untrusted software. So Microsoft has to block certificates from third parties, so this update is important, at least Microsoft thinks users should not skip it, even though there are too many Bug.

The Windows team now offers a temporary solution to the BitLocker problem. CTOnews.com reminds you that if you don't want to suspend the BitLocker feature, you need to wait patiently for Microsoft to release a subsequent update to fix the Bug.

If BitLocker Group Policy enables the TPM platform Authentication profile for the native UEFI firmware configuration, and PCR7 is selected by policy, the update may not be installed.

To view the PCR7 binding status, run the Microsoft system Information (Msinfo32.exe) tool with administrative privileges.

To resolve this issue, do one of the following before deploying this update:

On devices that do not have Credential Gard enabled, run the following command from the administrator command prompt to pause BitLocker for a restart cycle: Manage-bde-Protectors-Disable C:-RebootCount 1 then deploy the update and restart the device to restore BitLocker protection.

On Credential Guard-enabled devices, run the following command from the administrator command prompt to pause the BitLocker 2 restart cycles: Manage-bde-Protectors-Disable C:-RebootCount 3 and then deploy the update and restart the device to restore BitLocker protection.

Note: this issue only affects the security update (KB5012170) for the secure launch DBX and does not affect the latest cumulative security update released on August 9, 2022.

Solution: if your device prompts you to enter your BitLocker password to start Windows.

If you have not installed KB5012170 and enabled BitLocker on your device, follow the instructions below to temporarily disable BitLocker before installation.

If you have installed KB5012170 and have not restarted your device, or have only restarted once, use the following instructions to temporarily override BitLocker.

Important: if you restart the device two or more times after installing KB5012170, your device will not be affected by this issue.

The solution to temporarily suspend BitLocker or avoid BitLocker recovery when deploying KB5012170, perform the following steps:

Run the following command from the administrator command prompt:

Manage-bde-protectors-disable%systemdrive%-rebootcount 2

If you have not already installed Update KB5012170, install it.

Restart the device.

Restart the device.

BitLocker should be enabled automatically after two starts.

If you want to restore BitLocker manually to verify that it is enabled, use the following command:

Manage bde-protectors-Enable%systemdrive%

Next step: we are working on the solution and will provide updates in the next release.

Affected platform: client: Windows 11, version 21H2

Servers: none

"Microsoft acknowledges that there are problems with KB5012170 system updates, including Win8.1, Win10, Win11, etc."

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.