Microsoft has issued an urgent warning for Windows users, highlighting a potential bug that could cause some devices to enter the BitLocker recovery screen after installing security updates released on or after October 14, 2025.
See also: BitLocker: Automatic encryption can lock your data
The company is actively investigating the issue, which affects select Windows client versions and primarily affects Intel-based systems that support Connected Standby. This power-saving feature keeps devices connected to the network during low-power states. While the issue does not compromise security , it could disrupt user workflow by requiring a one-time entry of the BitLocker recovery key upon restart.
According to Microsoft's Windows release documentation, affected users may encounter the recovery prompt during startup or reboots after updates.
Once the key is provided, the device should return to normal operation without further interruption. This return to recovery mode stems from interactions between the updates and BitLocker encryption mechanisms, although Microsoft has not yet analyzed the exact cause. The warning emphasizes that no server versions are affected, limiting the scope to consumer and enterprise customer environments.
The issue targets three key customer platforms: Windows 11 version 25H2 and 24H2, linked to in the original knowledge base article KB5066835, and Windows 10 version 22H2 under KB5066791.
See also: Bitpixie vulnerability allows bypass of BitLocker encryption
Users can refer to Microsoft issue trackers such as WI1183025 for Windows 11 25H2, WI1183026 for 24H2 , and WI1183027 for Windows 10 22H2 via the Windows Release Health portal for the latest status.
These updates, released to fix critical vulnerabilities and improve system stability, unintentionally caused BitLocker to behave erratically on compatible hardware. Intel processors with Connected Standby appear to be most vulnerable, as the network persistence feature may conflict with boot processes after the update.
Microsoft recommends that affected organizations implement a Known Issue Rollback (KIR) to work around the issue. This mitigation tool, described on the company's IT Pro blog, requires contacting Microsoft Business Support for organization-wide deployment.
Individual users should ensure they have their BitLocker recovery keys available, typically stored in Microsoft accounts or printed during setup, to avoid extended downtime. In the meantime, Microsoft is urging caution before applying the October updates to affected devices, suggesting a pause for non-emergency systems.
See also: BitlockMove tool allows lateral movement & COM Hijacking
The company promises updates as the investigation progresses, with a focus on a permanent solution in future updates. Cybersecurity experts advise proactively backing up recovery keys, especially for enterprise fleets that rely on BitLocker for compliance.
