FVE_E_TOO_SMALL (0X80310011) – Not Enough Space for BitLocker Encryption

When This Error Hits

You're trying to turn on BitLocker for your system drive (C:) or a data drive. You've got BitLocker enabled in Group Policy, your TPM is working, and everything looks fine. Then—bam—the error pops up: "FVE_E_TOO_SMALL (0X80310011)" with a message about not enough free space remaining on the volume to allow encryption. I've seen this most often after a Windows feature update (like going from 22H2 to 23H2) or after someone fills a drive with large files—think game installs, video projects, or backups. The exact trigger: BitLocker needs room to store encryption metadata and temporary files during the encryption process. If your free space drops below a certain threshold (typically around 1 GB for system drives, more for larger volumes), it kills the operation.

Root Cause in Plain English

BitLocker doesn't encrypt your data immediately—it encrypts on the fly as you write new data. But it needs a scratchpad area to store encryption state, recovery keys, and metadata. That scratchpad is roughly 250 MB to 1 GB, depending on the drive size and encryption algorithm (XTS-AES 128 vs 256). If your drive is too full—say 99% used—BitLocker can't reserve that space, so it throws 0X80310011. This isn't a failure of BitLocker itself; it's a disk space problem. The fix is either freeing up enough space or shrinking the partition to give BitLocker breathing room.

Step-by-Step Fix

Step 1: Check Free Space

Open File Explorer, right-click your drive, and select Properties. Look at "Free space." For a system drive (C:), you need at least 1 GB free. For larger data drives (say 2 TB+), at least 2 GB is safer. If you're below that, proceed to Step 2.

Step 2: Free Up Space (Quickest Win)

1. Run Disk Cleanup: Type "Disk Cleanup" in Start, select the drive, hit OK. Click Clean up system files to clear Windows Update leftovers and temp files.
2. Empty the Recycle Bin (obvious, but I've missed it).
3. Delete large files you don't need—old downloads, temporary project files, or move them to external storage.
4. Run cleanmgr /sageset:1 in an admin command prompt to access advanced cleanup options.

After cleaning, recheck free space. If you're above 1 GB (system) or 2 GB (data), try BitLocker again—it should work.

Step 3: Shrink the Partition (If Freeing Space Isn't Enough)

Sometimes you need more free space than you can reasonably free up. Shrinking the partition makes the existing free space appear larger relative to the volume size. Here's how:

1. Open Disk Management: right-click Start > Disk Management.
2. Right-click the volume you want to encrypt (e.g., C:) and select Shrink Volume.
3. Enter a shrink amount in MB. For a 256 GB drive, shrink by 2048 MB (2 GB). For larger drives, go for 4096 MB (4 GB). Don't go crazy—shrink too much and you risk data issues.
4. Click Shrink. This creates unallocated space next to your volume. That unallocated space counts as free space for BitLocker.

Now the drive should have enough room. Try enabling BitLocker again.

Step 4: Use PowerShell to Force BitLocker (If Steps 2-3 Fail)

If you still get the error, something else might be blocking it. Run PowerShell as Administrator and type:

manage-bde -on C: -used

The -used flag tells BitLocker to only encrypt used space, not the free space. This reduces the temporary space needed. If your drive is mostly empty, this can bypass the error. But be careful: with -used, data that was deleted but not overwritten remains unencrypted (though it's still secure from most threats).

What to Check If It Still Fails

If you've freed space, shrunk the partition, and tried PowerShell, but the error persists, check these:

• Third-party encryption software: VeraCrypt, TrueCrypt, or Symantec Drive Encryption can conflict with BitLocker. Uninstall them first.
• Volume Bitmap corruption: Run chkdsk C: /f from an admin command prompt to fix file system errors. This clears NTFS metadata that might confuse BitLocker.
• TPM issues: If BitLocker fails silently after this error, check TPM status with tpm.msc. If the TPM is disabled or not ready, it can cause cascading failures.
• Windows version quirk: On Windows 10 20H2 through 22H2, there's a known bug where BitLocker incorrectly calculates free space on drives with compression enabled (like compact os). Disable compression with compact /u in an admin command prompt, then retry.

I've seen this error stump folks for days. But 90% of the time, it's just a space issue. Clear temp files, shrink the partition, and you're good. If you're still stuck, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > BitLocker-API for more detail. Good luck.