BitLocker error 0x800700 usually appears when Windows can’t read or write the encryption key, often after a BIOS update, a failed Windows update, or a drive connection change. The fix depends on the full error message, so the first step is always to capture the complete code and text before touching anything. This guide walks you through identifying the full error, then applying the correct repair method for the most common causes.
What You’ll Need
- Administrator access to the affected Windows PC
- A recovery key for the encrypted drive (check your Microsoft account, a printed copy, or a USB key saved earlier)
- A second working computer with internet access (for downloading tools if needed)
- An external drive to back up important files if the drive is still accessible
Step-by-Step
- Write down the full error code and message. When the error appears, press Ctrl + C on the error dialog to copy the text, then paste it into Notepad. If the error appears during boot, take a photo with your phone. The code may be 0x80070057, 0x8007007B, or 0x80070002 — each points to a different cause.
- Check the Event Viewer for the exact source. Press Win + R, type
eventvwr.msc, and press Enter. Go to Windows Logs > System and look for red error entries with source “BitLocker-DriveEncryption” or “volmgr” around the time the error occurred. Double-click each one and note the event ID and the full text. - Verify the drive is recognized in Disk Management. Right-click the Start button and select Disk Management. Check that the encrypted drive shows as “Healthy” and has a drive letter. If it shows as “Offline” or “Unreadable”, right-click it and choose Online or Reactivate.
- Suspend BitLocker temporarily. If you can still boot into Windows, open an elevated Command Prompt (right-click Start, select Terminal (Admin)) and run:
manage-bde -protectors -disable C:
ReplaceC:with your drive letter. This pauses protection so you can investigate without the drive locking itself. - Run the BitLocker repair tool. In the same elevated Command Prompt, run:
repair-bde C: D: -RecoveryPassword <your-recovery-key>
ReplaceC:with the locked drive andD:with an empty external drive. This copies the decrypted data to the external drive — it does not fix the original drive, but it recovers your files. - Update the TPM driver and firmware. Open Device Manager (right-click Start), expand Security devices, right-click the Trusted Platform Module (TPM) device, and select Update driver > Search automatically. Also check your PC manufacturer’s website for a BIOS/TPM firmware update, as outdated firmware is a common trigger for 0x800700 errors.
- Clear the TPM and re-enable BitLocker. If the TPM is the culprit, restart the PC, enter BIOS/UEFI (usually by pressing Del or F2 during boot), find the TPM settings, and select Clear or Reset. Save and exit. After Windows loads, open BitLocker Drive Encryption in Control Panel and re-enable BitLocker on the drive. You will need your recovery key to do this.
- Use the Windows startup repair. If the error appears at boot and you cannot reach the desktop, boot from a Windows installation USB. Choose Repair your computer > Troubleshoot > Advanced options > Startup Repair. Let it run — it may fix boot configuration files that reference the encrypted drive.
- Check for pending Windows updates. If you can boot, go to Settings > Windows Update and install all pending updates. A partially installed update can corrupt BitLocker metadata. After updating, run
manage-bde -statusin an admin Command Prompt to see if the drive reports as “Fully Encrypted” again. - Decrypt and re-encrypt as a last resort. If nothing else works and you have a backup of the data, open an admin Command Prompt and run:
manage-bde -off C:
This decrypts the drive completely. Once done, runmanage-bde -on C:to start fresh encryption. This resolves any corrupted metadata but takes hours on large drives.
Common Mistakes
- Ignoring the sub-code. 0x80070057 means an invalid argument (often a wrong recovery key), while 0x8007007B means the path is incorrect (drive letter changed). Treating them the same wastes time.
- Typing the recovery key manually. The key is 48 digits — one typo fails the whole operation. Copy-paste it from your Microsoft account or a saved file instead.
- Clearing the TPM without the recovery key. If you clear the TPM and don’t have the key, the drive becomes permanently inaccessible. Always back up the key first.
- Running repair-bde on the wrong drive. The destination drive must be empty and larger than the source. Using the same drive as source and destination corrupts everything.
- Forgetting to suspend protection before hardware changes. If you recently swapped a drive or RAM, suspend BitLocker first, then change hardware, then resume.
Tips
- Always print your recovery key and store it in a safe place — not on the same drive that’s encrypted.
- Keep a Windows installation USB handy. It is the only way to access recovery tools when Windows won’t boot.
- Run
manage-bde -statusmonthly to confirm encryption is healthy and the drive is not in “Encryption Paused” state. - If you have a laptop, ensure the battery is charged before any BitLocker operation — an interruption mid-encryption can cause this error.
- Use
manage-bde -protectors -get C:to list all protectors on the drive; this shows whether the TPM or a password is the active protector.
Troubleshooting
If repair-bde fails with “Access denied”: Run the command prompt as Administrator, and ensure the destination drive is formatted NTFS. Also verify you are using the correct recovery key format — it must be 8 groups of 6 digits, separated by hyphens.
If the drive still shows as locked after re-enabling BitLocker: The TPM may have a stale endorsement key. In an admin PowerShell, run Get-Tpm to check status. If it shows “TpmPresent: False”, the TPM is disabled in BIOS — enable it there and reboot.
If the error appears only after a Windows feature update: Roll back the update via Settings > Windows Update > Update history > Uninstall updates. After rollback, re-run manage-bde -status to confirm the drive is readable.
If the drive is not visible in Disk Management at all: The drive may have a hardware failure. Connect it to another computer via a USB adapter. If it still doesn’t appear, the drive itself is dead — no software fix will recover it.
If you cannot find your recovery key: Sign into account.microsoft.com/devices/recoverykey with the Microsoft account that was linked to the device. If the key is not there, check any printouts or USB drives from when BitLocker was first enabled.
If the error persists after all steps: The BitLocker metadata on the drive is likely corrupted beyond repair. Back up any accessible files, then use format on the drive (this erases everything) and re-enable BitLocker fresh.
Frequently Asked Questions
Q: What does error 0x800700 actually mean?
A: It is a generic Windows error meaning “The operation failed because the requested resource is in use” or “The parameter is incorrect.” The full message after the code tells you which one applies — always read that part.
Q: Will I lose my data if BitLocker gives this error?
A: Not necessarily. In most cases the data is still intact, just temporarily locked. Using repair-bde or re-entering the recovery key typically recovers everything. Only a physical drive failure causes permanent data loss.
Q: Can I fix this without the recovery key?
A: No. The recovery key is the only way to unlock a drive when the TPM fails. If you never saved it, the data is unrecoverable. Always save the key immediately after enabling BitLocker.
Q: Is it safe to clear the TPM?
A: Clearing the TPM removes all keys it stores, including BitLocker protectors. It is safe only if you have the recovery key and have suspended BitLocker first. Otherwise, the drive becomes permanently locked.
Q: How long does repair-bde take?
A: It depends on drive size and speed. A 500GB drive typically takes 2-4 hours. The process copies the entire encrypted volume to the destination drive, so it is a full read-write operation.
Q: Does this error appear on Windows 10 or Windows 11?
A: Both. The error code is the same across versions. The steps above work on Windows 10 version 1809 and later, and on all Windows 11 releases. The main difference is where the recovery key is stored in your Microsoft account.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Spotify Jam Not Working on Mobile? Fixes That Work
- Windows 10 No Internet Secured WiFi Error Fix
- Multi-Cloud GPU Failover Design Guide
- Error Code Currant Destiny? Meaning & Fixes
- AirPlay with Roku Multi-Device Setup: A How-To
- How to Set a Timer on iPhone (iOS 18 & 17)