Security hardening changes needed on domain controllers in IT environments to address CVE-2022-37967 will enter the Third deployment phase, as outlined in KB5020805: How to manage Kerberos protocol changes related to CVE-2022-37967 on June 13, 2023. Previous announcements had listed this change as taking place in April, however, that date has changed.
BitLocker not Resuming After Reboot Count Reached
Microsoft recently released a security update that causes BitLocker to not resume after the reboot count has been reached. This issue affects Windows 10 and Windows Server 2016 and 2019.
What is BitLocker?
BitLocker is a feature of Windows that provides encryption for data stored on a computer’s hard drive. It helps protect data from unauthorized access by requiring a user to enter a password or PIN before the computer can be used.
What is the Problem?
When the reboot count is reached, BitLocker is supposed to resume automatically. However, this is not happening due to a bug in the security update. As a result, users are unable to access their data until they manually enter the password or PIN.
How to Fix the Problem
Microsoft has released a patch to fix the issue. Users should install the patch as soon as possible to ensure that BitLocker resumes properly after the reboot count is reached.
“We recommend that customers install this update as soon as possible to ensure that BitLocker resumes properly after the reboot count is reached.” – Microsoft
Key points from the article:
From the Core Infrastructure and Security Blog
