Hello Speedy Nelson,
Windows triggered a BitLocker recovery because the system detected a change after an update. The update changed a boot component, forcing BitLocker to ask for the key even though the device appears in your devices list.
Quick checks :
- Find the recovery key in your Microsoft account Sign in to account.microsoft.com/devices with the same account used on the PC and open the device entry
- If the PC is Azure AD joined or managed: Ask your IT/admin to check for the stored recovery key.
- Check locally (admin) for protectors
manage-bde -protectors -get C:
How to control it:
Windows Update can modify boot files, firmware, or trigger a TPM state change. BitLocker treats that as a potential attack and requires the recovery key.
- Suspend BitLocker:
Suspend-BitLocker -MountPoint "C:" -RebootCount 1
- Or disable temporarily:
manage-bde -protectors -disable C:
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message.
Have a nice day!