{"id":45422,"date":"2026-04-15T20:04:10","date_gmt":"2026-04-15T12:04:10","guid":{"rendered":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/15\/microsoft-april-updates-trigger-bitlocker-key-prompts-on-some-servers\/"},"modified":"2026-04-15T20:04:10","modified_gmt":"2026-04-15T12:04:10","slug":"microsoft-april-updates-trigger-bitlocker-key-prompts-on-some-servers","status":"publish","type":"post","link":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/15\/microsoft-april-updates-trigger-bitlocker-key-prompts-on-some-servers\/","title":{"rendered":"Microsoft: April updates trigger BitLocker key prompts on some servers"},"content":{"rendered":"\n

\"Microsoft:<\/p>\n

Microsoft confirmed on Tuesday that some Windows Server 2025 devices will boot into BitLocker recovery after installing the April 2026 KB5082063 Windows security update.<\/p>\n

BitLocker is a Windows security feature that encrypts storage drives to prevent data theft. Windows computers typically enter BitLocker recovery mode after hardware changes or events such as TPM (Trusted Platform Module) updates, to regain access to protected drives that have not been unlocked via the default unlock mechanism.<\/p>\n

“Some devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key on the first restart after installing this update,” Microsoft said<\/a>.<\/p>\n

\"Microsoft:<\/a> <\/div>\n

“In this scenario, the BitLocker recovery key only needs to be entered once — subsequent restarts will not trigger a BitLocker recovery screen, as long as the group policy configuration remains unchanged.”<\/p>\n

However, as the company explained, this only happens for very specific configurations, on systems where all the following conditions are met:<\/p>\n

    \n
  1. BitLocker is enabled on the OS drive.<\/li>\n
  2. The Group Policy “Configure TPM platform validation profile for native UEFI firmware configurations<\/strong>” is configured, and PCR7 is included in the validation profile (or the equivalent registry key is set manually).<\/li>\n
  3. System Information (msinfo32.exe<\/strong>) reports that the Secure Boot State PCR7 Binding is “Not Possible<\/strong>“.<\/li>\n
  4. The Windows UEFI CA 2023 certificate is present in the device’s Secure Boot Signature Database (DB), making the device eligible for the 2023‑signed Windows Boot Manager to be made the default.<\/li>\n
  5. The device is not already running the 2023-signed Windows Boot Manager.<\/li>\n<\/ol>\n

    Microsoft added that this known issue is unlikely to affect personal devices, as impacted configurations are typically found on systems managed by enterprise IT teams.<\/p>\n

    \n
    \"Microsoft:
    BitLocker recovery screen (Microsoft)<\/em><\/figcaption><\/figure>\n<\/div>\n

    ​The company is now working on a solution to this issue and has shared temporary workarounds that allow installation of this month’s security updates.<\/p>\n

    Admins are advised to remove the Group Policy configuration before deploying the KB5082063 update, and to ensure that BitLocker bindings use the PCR7 profile by following these steps<\/a>.<\/p>\n

    Those who can’t remove the PCR7 group policy before installing can apply a Known Issue Rollback (KIR) on affected devices to prevent the automatic switch to the 2023 Boot Manager and to avoid triggering BitLocker recovery.<\/p>\n

    In May 2025, Microsoft released emergency updates<\/a> to address a similar issue that was causing Windows 10 systems to boot into BitLocker recovery after installing the May 2025 security updates.<\/p>\n

    One year earlier, in August 2024, Microsoft fixed another known issue<\/a> triggering BitLocker recovery prompts across all supported Windows versions after installing the July 2024 Windows security updates<\/a>.<\/p>\n

    In August 2022, Windows devices also became stuck at a BitLocker recovery prompt<\/a> after installing the KB5012170 security update<\/a>.<\/p>\n