Microsoft has encountered another unusual issue, this time mostly affecting Intel-based PCs. Users of Windows 11 versions 25H2 and 24H2, as well as some Windows 10 users, may unexpectedly find themselves in BitLocker recovery mode. Typically, BitLocker should not request the recovery key unless there have been changes to the system configuration. However, due to a new bug, users are being prompted to enter their recovery keys without any such changes. BitLocker encrypts the entire drive volume using AES encryption by default, ensuring the drive's security even if it is stolen, lost, or improperly decommissioned. "After installing Windows Updates released on or after October 14, 2025 (the Originating KBs listed above), some devices might encounter issues during restart or startup," notes Microsoft document for Microsoft 365 Business and Windows 11 Enterprise licensees.

From a portal not accessible to us (thanks to Windows Latest for images), it seems that Windows 11 25H2 with KB5066835 and Windows 11 version 24H2 with the same KB number are affected. Windows 10 version 22H2 is also impacted, with the originating ID KB5066791. The interesting part is the source of this issue. Since the launch of Windows 8, the Windows OS has included a Connected Standby feature. This power-saving feature allows the PC to stay connected to the network, receiving notifications and streaming music even while in standby mode. It was originally designed to extend battery life on laptops by maintaining a low-power state instead of draining the battery.Microsoft claims that primarily Intel-based systems are affected. Although there is no detailed explanation yet, it might be related to how Intel CPUs handle power states and interact with Windows. Currently, Microsoft is rolling out the fix slowly, likely planning to release it as another enablement package update to address this issue. The October update has already introduced several problems, so the new package will have many issues to resolve. Furthermore, this update reportedly caused three Azure-hosted virtual desktops running build 24H2 to become stuck at the recovery prompt, making them inaccessible to remote users. It's recommended to back up your BitLocker key (if you use BitLocker), and to apply the latest Windows updates to ensure your system doesn't unexpectedly prompt you for the key.