This error appears when you try to enable BitLocker or manage an existing encrypted drive on a Windows edition that does not include full BitLocker support, or when the drive’s encryption format is newer than your current Windows version supports. The fix depends on which Windows edition you have and whether the drive is already encrypted. Below are the exact steps to resolve it, ordered from the most common cause to the least.
What You’ll Need
- Administrator access to the Windows computer (a user account in the Administrators group).
- Your Windows product key or a Microsoft account linked to the device, in case you need to change editions.
- For already-encrypted drives: the BitLocker recovery key (48-digit number) or the password you set when encrypting.
- An external backup drive if you plan to decrypt and re-encrypt (recommended, not strictly required).
Step-by-Step
- Check your Windows edition. Press Win + R, type
winver, and press Enter. The window shows the edition and version. Full BitLocker (the Control Panel applet andmanage-bdecommand) is only included in Windows 10/11 Pro, Enterprise, and Education. Windows Home does not include it — it only has “Device Encryption” on supported hardware, which is a different feature. - If you are on Windows Home: You cannot install full BitLocker. Your options are:
- Use the built-in Device Encryption if your device supports it (Settings > Privacy & Security > Device encryption). It encrypts the system drive automatically and is managed through your Microsoft account.
- Upgrade to Windows Pro. Go to Settings > System > Activation > Upgrade your edition of Windows, then enter a Pro product key or buy one from the Microsoft Store. After the upgrade restarts, BitLocker will appear in Control Panel.
- Use a third-party encryption tool (VeraCrypt is a common free option) — but note that this guide covers the native Windows error only.
- If you are on Pro/Enterprise/Education but still see the error: Open an elevated Command Prompt (right-click Start > Terminal (Admin) or Command Prompt (Admin)) and run
manage-bde -status. This shows the encryption state of each drive. If the drive shows “Encrypted” but you cannot open BitLocker from Control Panel, the drive may have been encrypted with a newer format (XTS-AES 256) on a newer Windows version and you are now on an older one. - Update Windows fully. Go to Settings > Windows Update > Check for updates, install everything, and restart. Microsoft has shipped fixes for BitLocker compatibility across several feature updates. If your Windows build is older than the one that created the drive, updating often resolves the “not compatible” message.
- If the drive is external and encrypted on another PC: The external drive may use a newer encryption method than your current Windows supports. Connect it to the original computer, open BitLocker Drive Encryption in Control Panel, and click “Change password” or “Back up recovery key” — this does not change the encryption method. To make it compatible with your older Windows, decrypt the drive (click “Turn off BitLocker”), then re-encrypt it on the older machine using its default method (AES-CBC 128 on most older builds). This is a last resort because it takes time and requires the recovery key.
- Check Group Policy for encryption method. On Pro/Enterprise, press Win + R, type
gpedit.msc, and navigate to Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption. Look for “Choose drive encryption method and cipher strength.” If it is set to “XTS-AES 256” but your Windows build only supports “AES-CBC,” change it to “AES-CBC 128” or “Not configured,” then restart. This matters most when creating a new encrypted drive on an older Windows version. - Run the BitLocker repair tool. In the elevated Command Prompt, run
manage-bde -unlock C: -recoverypassword(replace C: and the key). If the drive unlocks, runmanage-bde -protectors -disable C:thenmanage-bde -protectors -enable C:to refresh the protector list. This often clears a corrupted state that triggers the compatibility error. - If none of the above works and the drive is your system drive: Back up your data, then decrypt the drive using the recovery key on a working Windows PC (connect the drive as an external if it is not the OS drive). After decryption, re-encrypt on your current Windows. This is the nuclear option but guarantees compatibility.
Common Mistakes
- Assuming Windows Home has BitLocker. It does not. The error is expected on Home unless your hardware supports Device Encryption, which is a separate setting and not the same as BitLocker.
- Mixing up Device Encryption and BitLocker. Device Encryption is automatic, uses your Microsoft account for recovery, and is available on Home. BitLocker is the full-featured tool. If you see the error in Control Panel’s BitLocker applet on Home, that is normal.
- Using an old Windows build to read a drive encrypted on a newer build. The encryption algorithm (XTS-AES) was introduced in Windows 10 version 1511. If your Windows is older than that, it cannot read the drive. Update Windows first.
- Skipping the recovery key backup. If you decrypt or change protectors and lose the key, you may permanently lose access to the data. Always have the key saved before making changes.
Tips
- Before upgrading from Home to Pro, check that your CPU and motherboard support the required virtualization features (TPM 2.0 is recommended but not mandatory for BitLocker — you can enable it without TPM via Group Policy, but that is more advanced).
- Keep your Windows fully updated. Most BitLocker compatibility issues are fixed in cumulative updates, not feature updates.
- If you regularly move external drives between computers with different Windows versions, stick to the older encryption method (AES-CBC 128) for maximum compatibility.
- Write down the exact error text. “Not compatible with this version of Windows” can also appear when the drive has a file system BitLocker does not support (e.g., exFAT on some older builds). Convert the drive to NTFS if that is the case.
Troubleshooting
- The error still appears after updating Windows. Check if the drive is using the XTS-AES 256 method by running
manage-bde -status. If it says “Encryption Method: XTS-AES 256,” and your Windows build is older than 1511, you must decrypt and re-encrypt with AES-CBC. On newer builds, XTS-AES 256 is fully supported — if the error persists, runsfc /scannowin an elevated Command Prompt to repair system files. - BitLocker is greyed out in Control Panel. This usually means the drive is not a fixed data drive or the system drive is not the C: drive. BitLocker only works on internal fixed drives and the OS drive. External USB drives need “BitLocker To Go” which is also only on Pro/Enterprise.
- You do not have a recovery key. If you never backed it up, check your Microsoft account (account.microsoft.com > Devices > BitLocker recovery keys) if you used Device Encryption. For full BitLocker, the key is sometimes saved to your Microsoft account if you chose that option. If not, and you cannot unlock the drive, the data may be unrecoverable.
- The drive is encrypted but Windows does not show the unlock prompt. Open File Explorer, right-click the drive, and select “Unlock drive.” If that option is missing, run
manage-bde -unlock X:in an elevated Command Prompt. - After upgrading from Home to Pro, BitLocker still does not appear. Restart the computer. If it still does not show, run
Enable-WindowsOptionalFeature -Online -FeatureName BitLocker -Allin an elevated PowerShell, then restart again.
Frequently Asked Questions
Can I use BitLocker on Windows 10 Home?
No. Full BitLocker is only in Pro, Enterprise, and Education. Home has Device Encryption instead, which is automatic on supported hardware.
What is the difference between Device Encryption and BitLocker?
Device Encryption is a simplified, automatic encryption feature for Home editions. BitLocker offers full control (password, recovery key, multiple protectors, encryption methods) and is available on Pro and above.
Why does my external drive say “not compatible” on my laptop but works on my desktop?
Most likely the drive was encrypted with a newer encryption algorithm (XTS-AES 256) on the desktop, and the laptop runs an older Windows build that only supports AES-CBC. Update the laptop or decrypt/re-encrypt the drive using the older method.
Will I lose data if I decrypt the drive?
No, decryption preserves all files. However, the process can take a long time (hours for large drives), and you need the recovery key or password to start it. Always back up important data first.
How do I check which encryption method my drive uses?
Open an elevated Command Prompt and run manage-bde -status. Look for the “Encryption Method” line for each drive. It will show something like “XTS-AES 256” or “AES-CBC 128.”
Is it safe to disable BitLocker temporarily to fix the error?
Yes, but only if you have the recovery key saved. Disabling BitLocker fully decrypts the drive, which removes the error but also removes protection. Re-enable it after fixing the compatibility issue.
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
- iOS 18 Safari Not Working? Fixes That Help
- How to Check Your Linux Kernel for Spectre
- iPhone Safe Mode: How to Enable or Disable It
- Fix Slow Internet Lag on Samsung Galaxy Note
- How to Get iOS 17 on iPhone X (Safe Methods)
- Fix Gmail IMAP Error in Outlook: Step-by-Step