Problemas con BitLocker en Windows 11: clave de recuperación, bloqueo y soluciones para el arranque

Choose the section that matches the problem displayed on your computer. Avoid trying every method in sequence because unnecessary TPM, BIOS, or boot changes can create additional recovery prompts.

Problem 1. Windows 11 Is Asking for a BitLocker Recovery Key

Start by recording the first eight digits of the ID de la clave de recuperación displayed on the recovery screen. This is not the recovery key itself. It identifies which Tecla de 48 dígitos belongs to the encrypted drive.

Check the following locations in order:

1. Cuenta de Microsoft: Sign in from another device and check the recovery keys associated with your account.
2. Work or school account: Check the organization’s device portal or contact its IT administrator.
3. Another person’s Microsoft account: This may apply if someone else originally configured the computer.
4. Printed copy: Check documents saved when BitLocker was enabled.
5. USB flash drive or text file: Look for a previously exported recovery key.
6. Existing Windows installations or accessible backups: Search locations where the key may previously have been saved.

Match the Key ID before entering a recovery key. A valid key belonging to a different drive will not unlock the current volume.

Importante: There is no legitimate command that bypasses BitLocker encryption without an available password, recovery key, startup key, or another configured protector. Resetting or reinstalling Windows may erase the files on the encrypted system drive.

Problem 2. The BitLocker Recovery Key Is Not Accepted

If Windows rejects the recovery key, check the following:

• Confirm that the key contains exactly 48 digits.
• Match the first eight digits of the Recovery Key ID.
• Check whether you are using a key associated with a different computer or drive.
• Verify the keyboard layout shown in the recovery environment.
• Do not enter the Key ID itself as the recovery key.
• Check all Microsoft, work, and school accounts that may have been used to configure the computer.

Advanced users can open Command Prompt from Windows Recovery Environment and check the drive status:

manage-bde -status

Drive letters may be different in the recovery environment. After identifying the encrypted Windows volume, try:

manage-bde -unlock C: -RecoveryPassword YOUR-48-DIGIT-RECOVERY-KEY

Sustituir C: with the correct drive letter and replace the example text with the complete recovery key.

Problem 3. BitLocker Keeps Asking for the Recovery Key at Every Startup

If the correct key unlocks Windows but the recovery screen returns after every restart, BitLocker may still be detecting a mismatch between the TPM, Secure Boot, firmware, or boot configuration.

After Windows starts:

1. Abra el símbolo del sistema como administrador.
2. Check the current status:

manage-bde -status C:

3. Back up the recovery key before changing TPM, BIOS, UEFI, or Secure Boot settings.
4. Install the latest Windows updates and the latest stable firmware supplied for the device.
5. Temporarily suspend BitLocker protection:

manage-bde -protectors -disable C:

6. Restart the computer and allow Windows to start normally.
7. Resume protection:

manage-bde -protectors -enable C:

Suspending protection keeps the drive encrypted but temporarily prevents the TPM-based protector from forcing recovery while approved system changes are completed.

Do not clear the TPM as an initial troubleshooting step. Clearing the TPM removes TPM-stored security information and may require the recovery key before the encrypted drive can be accessed again.

Problem 4. The Correct Recovery Key Works, but Windows Still Will Not Start

A successful BitLocker unlock only restores access to the encrypted volume. It does not automatically repair corrupted boot files, failed updates, damaged system files, or hardware problems.

From the BitLocker recovery screen:

1. Seleccione Skip this drive.
2. Abrir Troubleshoot > Advanced options > Command Prompt.
3. Identify the Windows drive because it may not use the letter C: in the recovery environment.
4. Unlock the drive:

manage-bde -unlock C: -rp YOUR-48-DIGIT-RECOVERY-KEY

5. Temporarily disable the protectors:

manage-bde -protectors -disable C:

6. Close Command Prompt and try Reparación de la puesta en marcha.

Only consider boot-repair commands after the encrypted volume has been successfully unlocked and the problem has been confirmed as a Windows boot failure.

Do not present these commands as a universal BitLocker fix:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

They repair specific Windows boot components and do not recover, recreate, or bypass a BitLocker key. In addition, most modern Windows 11 system drives use UEFI and GPT, so MBR-specific commands may not address the actual startup problem.

Problem 5. Device Encryption or BitLocker Is Missing

Si Cifrado de dispositivos does not appear in Windows Settings:

1. Buscar Información del sistema.
2. Haga clic con el botón derecho y seleccione Ejecutar como administrador.
3. Localice Automatic Device Encryption Support o Device Encryption Support.

Las posibles razones son:

• TPM is unavailable or disabled
• Windows Recovery Environment is not configured
• Secure Boot is disabled
• PCR7 binding is unavailable
• The computer does not meet Device Encryption requirements
• The current Windows account does not have administrator permissions

Windows 11 Pro, Enterprise, and Education users should also search for Gestionar BitLocker, because the full BitLocker control panel may still be available even when the Device Encryption settings page is not shown.

Problem 6. A Windows Update Triggered the Recovery Screen

Install the latest cumulative Windows update after regaining access.

In April 2026, Microsoft confirmed that Windows 11 update KB5083769 could trigger a BitLocker recovery prompt on some systems using a specific and unrecommended PCR7 Group Policy configuration. Microsoft addressed the problem in the May 2026 update KB5089549.

Do not assume that every Windows update requires BitLocker to be manually suspended. Microsoft updates normally handle suspension automatically. Manual suspension is more relevant before certain non-Microsoft BIOS, UEFI, TPM firmware, or Secure Boot changes.

Problem 7. A BitLocker-Encrypted Data Drive Is Damaged

If an external, secondary, or removable BitLocker drive cannot be unlocked normally even though you have the correct recovery information, Microsoft provides the reparación-bde tool for disaster-recovery situations.

The recovered data must be written to a different destination drive. Do not use the damaged encrypted drive as the recovery destination.

Porque reparación-bde can overwrite the destination volume and requires correct recovery material, it should be treated as an advanced recovery method rather than a normal unlock command.