
🎯Basically, some Windows Server 2025 computers may ask for a recovery key after an update.
What Happened
Microsoft has acknowledged an issue affecting some Windows Server 2025 devices following the installation of the April 2026 security update, KB5082063. After applying this update, certain configurations may lead the servers to boot into BitLocker recovery mode. BitLocker is a security feature designed to encrypt storage drives and protect data from unauthorized access.
Who's Affected
This problem is primarily seen in enterprise environments where specific Group Policy configurations are in place. Personal devices are unlikely to be impacted, as the affected setups are typically managed by IT teams in organizations.
What Data Was Exposed
While no data has been reported as exposed due to this issue, the situation can lead to disruptions in access to encrypted drives until the recovery key is provided. This could cause operational delays in affected organizations.
What You Should Do
Microsoft has provided temporary workarounds for system administrators: If the PCR7 group policy cannot be removed prior to the update, administrators can apply a Known Issue Rollback (KIR) on affected devices. This will prevent the automatic switch to the 2023 Boot Manager and avoid triggering the BitLocker recovery screen.
Containment
- 1.Remove the Group Policy configuration before deploying the April update.
Remediation
Background and Previous Issues
This isn't the first time Microsoft has faced issues related to BitLocker recovery prompts. In May 2025, emergency updates were released to address a similar problem affecting Windows 10 systems. Additionally, in August 2024 and August 2022, Microsoft had to resolve issues that caused BitLocker recovery prompts after security updates. These recurring issues highlight the complexities involved in managing BitLocker settings across various Windows versions.
🔒 Pro insight: This issue underscores the importance of validating Group Policy settings before deploying critical updates to avoid operational disruptions.




