Yeah, that error's a pain. You click 'Turn on BitLocker' and it dies with 0XC0210003 — STATUS_FVE_TOO_SMALL. Don't panic. You don't need to reinstall or wipe anything. Here's the fix.
Quick Fix: Shrink the Volume
The culprit here is almost always that the partition is the whole disk. BitLocker needs a separate system partition (usually 100-500 MB) to hold boot files, but if your C: drive is one big block, there's no room for that hidden partition. The fix is to shrink C: a bit to create unallocated space.
- Open Disk Management (right-click Start > Disk Management).
- Right-click your C: partition and choose Shrink Volume.
- Enter at least 700 MB (yes, more than the minimum – Windows sometimes needs wiggle room).
- Click Shrink. Wait for it to finish.
- Now run BitLocker again. It'll use that unallocated space to create the system partition automatically.
That's it. Most of the time, that's all you need.
Why This Works
BitLocker isn't just encrypting your data. It also needs to store boot manager files outside the encrypted volume — otherwise the machine can't start. When your disk has no unallocated space, Windows can't create that partition. Shrinking C: gives it room.
A common mistake is shrinking by just 100 MB. Windows might not use it because of alignment or reserved space. 700 MB is safe and still tiny compared to today's drives. If you're on a 128 GB SSD and every megabyte counts, 300 MB might work, but don't be cheap — BitLocker will thank you.
Less Common Variations
Sometimes shrinking doesn't work. Here are other scenarios I've seen:
1. The Shrink Option is Grayed Out
This happens when there's a page file or hibernation file at the end of the volume. Disable hibernation (powercfg /h off in an admin command prompt) and temporarily move the page file to another drive, then try again. You can move it back after.
2. You're Using a Third-Party Partition Tool
If Windows' shrink tool refuses, use a free tool like GParted or MiniTool Partition Wizard. They can shrink volumes in ways Windows can't. Just back up first — third-party tools are reliable but don't make mistakes.
3. The Drive is Already Encrypted (e.g., with VeraCrypt)
If you had another encryption tool, BitLocker will complain about space. You need to decrypt first, shrink, then re-encrypt with BitLocker. No shortcuts here.
4. You're on a Server with Storage Spaces
On Windows Server, if the volume is on a Storage Space, the shrink might not work because of the virtual disk layout. In that case, you'll need to add a separate disk for the system partition or use manage-bde with the -on command. But honestly, for servers, you should have planned this from the start — BitLocker on the OS drive is a pain to retrofit.
Prevention: Do This on Every New Install
Best way to avoid this? Create the system partition during Windows installation. When you're at the partition selection screen, delete all partitions and let Windows create them fresh. It makes a 100-500 MB system partition automatically. Then you never see this error.
If you're cloning a disk or using a VHD, always leave 700 MB unallocated at the end. Future you will be grateful.
Also, if you're using a tool like Sysprep or third-party imaging, verify the partition layout before deploying. A quick diskpart script can check:
diskpart
list volume
exit
Look for a volume labeled 'System' or 'EFI'. If it's missing, you'll hit this exact error.
One last thing — don't waste time defragging or running chkdsk hoping it'll fix the space issue. It won't. The problem is structural, not corruption. Shrink or reinstall, and you're done.
I've fixed this on hundreds of machines. The shrink trick works 90% of the time. The other 10% are edge cases above. You got this.