Windows BitLocker Drive D keeps asking for recovery key after UEM migrationSolved

Hi @yuudai ,

This behavior usually occurs when Auto-Unlock is not enabled, or when the Auto-Unlock binding for the secondary drive was lost during migration from another UEM.

For BitLocker-protected fixed data drives such as Drive D, Windows uses Auto-Unlock to unlock the drive automatically during startup. Auto-Unlock binds the secondary drive to the encrypted operating system drive, typically Drive C. If that binding is missing, Drive D can remain locked and may prompt for the recovery key.

To re-enable Auto-Unlock for Drive D, use either of the following methods while the drive is currently unlocked:

Method 1: Control Panel

1. Open the Start menu.
2. Search for Manage BitLocker.
3. Locate Drive D:.
4. Select Turn on auto-unlock.

Method 2: PowerShell

1. Open PowerShell or Windows Terminal as administrator.
2. Run: Enable-BitLockerAutoUnlock -MountPoint “D:”

Important prerequisite: the primary C: drive must also be encrypted with BitLocker. Auto-Unlock for a secondary fixed drive depends on the encrypted OS drive. After enabling Auto-Unlock, restart the device and confirm that Drive D opens in File Explorer without asking for the recovery key.

Regards,
Isabel Lora
Hexnode UEM

So we don’t need to decrypt and encrypt Drive D again? The drive is accessible right now after entering the recovery key, but it keeps coming back after restarts.

No, decrypting and re-encrypting the drive is not required in this case if the drive is already unlocked and healthy. The key step is to enable Auto-Unlock while Drive D is unlocked.

Once Auto-Unlock is enabled, Windows stores the unlock information for the data drive against the encrypted OS drive. That should prevent the recurring recovery key prompt during normal startup.

A quick check after applying the change:

1. Confirm Drive C is BitLocker-encrypted.
2. Confirm Drive D is unlocked.
3. Enable Auto-Unlock using Control Panel or PowerShell.
4. Restart the device.
5. Open File Explorer and verify that Drive D is accessible without entering the recovery key.

Regards,
Isabel Lora
Hexnode UEM