PC's continually asking for Bitlocker password

[aydee]

Hi All,

We are having a spate of PC's all requesting bitlocker passwords. But when rebooting after puting it in, it asks again.

Its mentioning that the PC configuration has changed when it hasnt. BIOS picks up all the RAM, and the drive, and when your in Windows, it works fine.

To add to the confusion, its only in one particular room, and its occuring even after a reimage, which is leading my mind down the Windows updates path. But im not 100% sure, because then it would be school wide due to WSUS..

 

We only use Stone, and these PC's are all of the Asus  H110M-A-DP Motherboard. Possibly WinUpdate pushed a bios update?

Anyone else seeing this or have any ideas??
Thanks

Edited September 17, 2025 by aydee

[sigma]

Maybe this:

https://support.microsoft.com/en-gb/topic/may-13-2025-kb5058379-os-builds-19044-5854-and-19045-5854-0a30e9ee-5038-45dd-a5d7-70a8813a5e39

 

Symptoms

We are aware of a known issue on devices with Intel Trusted Execution Technology (TXT) enabled on 10th generation or later Intel vPro processors. On these systems, installing the May 13, 2025, Windows security update (KB5058379) might cause lsass.exe to terminate unexpectedly, triggering an Automatic Repair. On devices with BitLocker enabled, BitLocker requires the input of your BitLocker recovery key to initiate the Automatic Repair. 

Affected devices then enter one of two states:

1. Some devices might make several attempts to install update KB5058379 before Startup Repair successfully rolls back to the previously installed update.

2. Startup Repair might experience a failure that creates a reboot loop, which again initiates an Automatic Repair, returning the device to the BitLocker recovery screen.

Consumer devices typically do not use Intel vPro processors and are less likely to be impacted by this issue. 

Resolution

This issue was resolved by Windows updates released May 19, 2025 (KB5061768), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. 

 

I passed on May's Cumulative Update for Win 10 devices that reason.