Impossible d'activer BitLocker ? Comment résoudre ce problème sous Windows 10/11

Choose the section that matches your symptoms. After each relevant change, retry once and check the new status or event message.

1. Check the TPM When the Message Mentions Encryption Keys

Presse Windows + R, tapez tpm.msc, and check the status. For more detail, open Windows PowerShell en tant qu'administrateur et exécutez :

1. Get-Tpm

Check whether Windows detects the TPM and reports it as ready. If Windows cannot find it:

1. Check your PC manufacturer’s firmware instructions.
2. Confirm that the firmware enables the TPM feature.
3. Look for names such as Intel PTT, AMD fTPM, ou Soutien aux dispositifs de sécurité.
4. Restart and check the status again.

Use the manufacturer’s guidance for your exact model. Firmware menus differ.

If Windows reports TPM lockout or preparation errors, follow the matching Microsoft troubleshooting procedure. Do not clear the TPM as a routine first step: Microsoft warns that clearing it can cause data loss. Preserve recovery access before any reset.

For an already encrypted system, follow the device maker’s instructions for suspending and resuming protection around firmware maintenance. Do not switch between Legacy and UEFI boot modes simply to test whether the error disappears.

2. Check the USB Startup Key After a Failed Restart Test

Si “ Impossible d'activer BitLocker ” appears after the hardware test and your configuration uses a USB startup key, check that USB device first.

1. Leave the startup-key USB drive connected during restart.
2. Connect it directly to the PC.
3. Try another built-in USB port.
4. Check the manufacturer’s instructions for USB support during startup.
5. If necessary, create the startup key on a different compatible USB drive through the appropriate BitLocker setup process.

Microsoft identifies unreadable USB ports, incompatible USB devices, and firmware behavior as possible causes in this scenario.

A USB startup key and a printed 48-digit recovery password serve different roles. A flash drive containing only a text copy of the recovery password does not automatically act as a startup-key device.

3. Investigate 0x80070057 BitLocker Errors in Context

A code 0x80070057 BitLocker message indicates an invalid parameter, but that description alone does not tell you which setting failed.

Start with the action that produced it:

• A command failed: confirm its syntax and target drive letter.
• The setup wizard failed: record whether it stopped during drive preparation, protector setup, or recovery-key backup.
• A deployment task failed: ask IT to inspect the task’s logs and applied policy.

Microsoft documents a specific enablement failure involving an operating-system disk without a separate active system partition. That article describes older Windows layouts. Its partition preparation command is not a universal Windows 10/11 fix.

To inspect your current layout:

1. Ouvrir msinfo32 and note Mode BIOS.
2. Ouvrir diskmgmt.msc.
3. Identify the disk containing Windows.
4. Inspect its existing system partitions without modifying them.

Modern UEFI installations normally use a FAT32 EFI System Partition; legacy systems use a different arrangement. A recovery partition has a separate purpose.

Do not format, delete, or mark partitions active based only on 0x80070057 BitLocker search results. If the evidence points to a layout problem, back up the disk and arrange a repair that matches its firmware and partition style.

4. Trace the Missing File Behind 0x80070002 BitLocker

Pour un 0x80070002 BitLocker failure, identify what Windows tried to open.

For example, a command might reference a startup-key file on a USB drive whose letter changed. A recovery-environment operation may instead point to an unavailable Windows RE image.

Use this sequence:

1. Check any file path in the command or event.
2. Confirm that the referenced device is connected.
3. Verify its current drive letter.
4. If the failure concerns recovery setup, check Windows RE:
5. reagentc /info

If Windows RE is disabled on the running Windows installation, try:

1. reagentc /enable

Then run reagentc /info again. If enabling fails, record the message and repair the identified image or configuration problem. Do not delete the recovery partition to make the error disappear. Microsoft’s REAgentC documentation explains these commands and their scope.

For evidence of missing or damaged Windows system files, use Microsoft’s repair sequence:

1. DISM.exe /Online /Cleanup-Image /RestoreHealth
2. sfc /scannow

Run SFC after DISM finishes successfully. These tools repair Windows components; they cannot recreate a lost personal recovery-key file.

5. Check Device Availability for 0x80070015 BitLocker

A 0x80070015 BitLocker error points to a device that is not ready. First determine which device the failing operation needs: the encrypted volume, a startup-key USB, or the recovery-key backup destination.

For an external drive:

1. Check that File Explorer and Disk Management detect the expected device.
2. Confirm the drive letter and capacity.
3. Check its power supply and cable.
4. Try a direct USB connection if a hub causes intermittent detection.

Do not disconnect a drive during active encryption. If it repeatedly disappears or reports read errors, stop repeated enablement attempts and protect accessible files first.

Cancel any unexpected initialization or formatting prompt for a drive containing needed data. Formatting does not resolve the underlying access problem while preserving those files.

6. Separate 8007139f BitLocker Setup Errors From Recovery Loops

The underlying invalid-state code does not prove that the TPM, bootloader, or disk has failed.

Pour un 8007139f BitLocker error inside Windows, inspect volume status and the event recorded at the same time. Determine whether another encryption operation or an incomplete configuration explains the state.

If the code appears before Windows starts:

• Record the screen and any recovery-key ID.
• Retrieve the matching 48-digit recovery password.
• Use the available Windows recovery options if normal startup still fails.
• Give IT or support the recent firmware, hardware, or boot changes.

Do not apply desktop repair commands blindly from recovery mode. Drive letters can differ there.

If the screen requests a key, follow our 48-digit BitLocker recovery key guide. A valid key restores an unlock method; it does not necessarily repair the startup fault.

7. Review Event Logs and Organizational Policy

Quand BitLocker could not be enabled still appears, use evidence from the failure time.

Ouvrir Event Viewer > Applications and Services Logs > Microsoft > Windows. Review the available BitLocker-API logs. Check Windows Logs > System for TPM and TPM-WMI events as well.

Save the event ID, full message, affected volume, and timestamp.

For managed computers, ask IT to check effective policy and recovery-key backup requirements. BitLocker may need to store recovery information in the organization’s directory before activation can continue. Troubleshoot that requirement with the administrator rather than disabling it locally.