Fix BitLocker To Go Refusing to Unlock a Drive Formatted on macOS

Quick fix: BitLocker To Go on Windows 11 reads FAT32 and exFAT volumes encrypted with the password protector, but if macOS formatted the drive with a partition layout Windows can’t parse (Apple Partition Map, or a HFS+ wrapper), Windows sees only the wrapper and fails to find the BitLocker container. Reformat the drive on Windows first, then re-encrypt with BitLocker To Go.

You used a macOS-formatted USB drive on a Windows 11 machine. The drive contained BitLocker To Go data from a previous session. Now Windows can’t unlock the drive — it doesn’t even prompt for the password. The drive shows as raw or with no detected file system. macOS may have written its own partition signature on top of the BitLocker partition.

Why this happens

BitLocker To Go stores its container in a special partition layout. The drive shows two partitions: a small unencrypted “discovery” partition that holds the BitLocker reader (for legacy Windows compatibility), and a large encrypted partition. When you connect the drive to macOS, macOS treats the encrypted partition as raw and may write a HFS+ header or APM signature when prompted “Do you want to initialize this disk?” If the user clicked Yes, macOS wrote over the BitLocker partition header.

Without the BitLocker header, Windows can’t find the password protector, the volume metadata, or the recovery key slots. The drive looks RAW. Data inside the encrypted region is still there but unreachable without forensic-level tools.

Method 1: Verify whether macOS overwrote the BitLocker container

1. Connect the drive on Windows.
2. Open Disk Management (diskmgmt.msc). Find the drive.
3. If the drive shows as RAW with no partitions visible: macOS overwrote the partition table. Data recovery may be needed (Method 3).
4. If the drive shows partitions but they’re not recognized: the BitLocker container may still be intact but the discovery partition was overwritten.
5. Open elevated Command Prompt and run:
   
   manage-bde -status X: (replace X: with your drive letter; assign one in Disk Management first)
6. If manage-bde reports “No valid BitLocker partitions found,” the container itself is corrupted; recovery requires the next steps.
7. If manage-bde reports a BitLocker volume but locked, run manage-bde -unlock X: -password and enter your password.

If unlock works, you’re fine. If not, continue to Method 2 or 3.

Method 2: Reformat the drive and start fresh (data lost)

If the data on the drive isn’t critical:

1. In Disk Management, right-click the drive and choose Delete Volume for any visible partitions. Confirm.
2. Right-click the resulting unallocated space and choose New Simple Volume.
3. Format as exFAT or NTFS. exFAT is best for cross-platform compatibility; NTFS for Windows-only.
4. Right-click the drive in File Explorer and choose Turn on BitLocker.
5. Choose Use a password to unlock the drive. Set a strong password.
6. Save the recovery key (Microsoft account, file, or print).
7. Choose Encrypt used disk space only for speed.
8. Click Start encrypting. Wait for completion.
9. Test by ejecting and reconnecting — Windows should prompt for the password.
10. Connect on macOS — the system can’t read the BitLocker container, which is expected.

To use the drive again on macOS without breaking BitLocker: do not click “Initialize” when macOS prompts. Just dismiss the dialog — the drive remains intact even though macOS can’t use it.

Method 3: Attempt data recovery on the corrupted drive

If the drive contained important data:

1. Stop using the drive immediately. Don’t write anything.
2. Download a forensic-grade tool like EaseUS Data Recovery (free trial), R-Studio, or DiskGenius.
3. For BitLocker-encrypted partitions, you need the original recovery key. Run the tool, scan the drive, and if it identifies a BitLocker container, supply the recovery key when prompted.
4. Recovery is not guaranteed — if macOS wrote a HFS+ header over the BitLocker header bytes, those exact bytes are gone and can’t be reconstructed.
5. For drives where the BitLocker container is intact but the partition table is gone, TestDisk (free, open-source) can rebuild the partition table without writing to the drive.

Data recovery is best-effort. The right time to recover is before doing anything else with the drive.

How to verify the fix worked

• After Method 2: the drive prompts for BitLocker password when connected to any Windows PC.
• You can mount, read, and write to the drive normally after unlocking.
• Disconnect cleanly via Safely Remove Hardware — reconnect and confirm the prompt appears again.
• The drive shows as BitLocker-encrypted in Disk Management (volume name has a padlock icon).

If none of these work

If you need to use the same drive on both macOS and Windows long-term, BitLocker To Go isn’t the right tool — macOS doesn’t read it natively, and any “Initialize” click on macOS corrupts it. Consider VeraCrypt instead, which has clients for both macOS and Windows and uses a container file format that both OSes preserve. For drives that must use BitLocker To Go due to corporate policy, label the drive clearly so users don’t accidentally initialize it on a non-Windows machine. As a last resort, replace the USB drive — physical drives are cheaper than the data recovery effort.

Bottom line: BitLocker To Go and macOS don’t coexist well. Reformat on Windows and re-encrypt fresh, or switch to a cross-platform tool like VeraCrypt. Once macOS “initializes” a BitLocker drive, the data is mostly lost — recovery is possible but not reliable.