FVE_E_WRONG_SYSTEM_FS (0x8031002B) fix – system partition must be NTFS

When you'll see this error

You're trying to turn on BitLocker on a Windows 10 or Windows 11 machine – maybe a Dell OptiPlex 7080, an HP EliteBook 840, or a Lenovo ThinkCentre. You open BitLocker Drive Encryption in Control Panel, click "Turn on BitLocker" on the C: drive, and after a few seconds you get a red error: "The system partition file system must be NTFS" with code 0x8031002B. The BitLocker wizard won't let you proceed until this is fixed.

This happens most often on PCs that originally shipped with Windows 7 or were upgraded from an older version, but I've also seen it on custom-built machines where the system partition was created as FAT32 during a clean install of Windows 10. Yes, Windows Setup can create a FAT32 system reserved partition on UEFI systems if the disk is larger than 2TB, but that's rare – more often it's because the machine came with a small FAT32 ESP (EFI System Partition) that's separate from the system reserved partition.

What's going on under the hood

BitLocker needs a small, unencrypted system partition (usually around 100 MB to 500 MB) to store the boot files – the Windows Boot Manager and the BitLocker boot code. This partition must be NTFS. If it's FAT32, BitLocker refuses to encrypt the OS drive because it can't write the boot files reliably on a FAT32 filesystem. The FAT32 file system has a 4 GB file size limit and lacks certain security features BitLocker depends on.

The system partition is typically the "System Reserved" partition (no drive letter, labeled as system in Disk Management) or the EFI System Partition on UEFI systems. Windows 11 and recent Windows 10 versions often have both – a small FAT32 ESP (100 MB) and a larger NTFS system partition. But some OEMs skip the NTFS one entirely, leaving only the FAT32 ESP. That's when this error pops up.

The fix – convert the system partition to NTFS

You have two options. The first is to use a built-in Windows tool to shrink the OS partition and create a new NTFS system partition. That's the cleanest approach, but it's also time-consuming and risky if you're not careful. The second – and the one I recommend for most people – is to convert the existing FAT32 partition to NTFS using the convert command. This works because the system partition is small and has no critical data that FAT32 needs (like UEFI boot files – those are stored elsewhere).

1. Open an elevated Command Prompt. Press the Windows key, type cmd, right-click "Command Prompt" and select "Run as administrator." Click Yes on the UAC prompt.
2. Identify the system partition. In the Command Prompt, type diskpart and press Enter. Then type list volume and press Enter. Look for the volume with "System" in the Info column – it will have a drive letter or none. Note its volume number.
3. Select the system volume. Type select volume X (replace X with the volume number from step 2) and press Enter. You'll see "Volume X is the selected volume."
4. Assign a temporary drive letter. Type assign letter=S (or any unused letter like T or Z) and press Enter. Now that partition is accessible as S:\.
5. Exit diskpart. Type exit and press Enter to return to the Command Prompt.
6. Convert the file system. Type convert S: /fs:ntfs and press Enter. The system will tell you it must dismount the volume first and ask for confirmation. Type Y and press Enter. Wait for the conversion to finish – it usually takes less than 10 seconds.
7. Remove the temporary drive letter. Open diskpart again (diskpart), select the same volume (select volume X), then type remove letter=S and press Enter. Type exit to leave diskpart.
8. Reboot your PC. Restart Windows to ensure the boot configuration picks up the new filesystem.
9. Try BitLocker again. Open BitLocker Drive Encryption in Control Panel and click "Turn on BitLocker" on C:. The error should be gone.

What if the error persists after conversion

Sometimes Windows still sees the old filesystem in its boot configuration. Run bcdedit from an elevated Command Prompt to check: type bcdedit /enum {bootmgr}. Look for the path entry – it should point to \bootmgr on the NTFS partition. If it's wrong, you can fix it with bcdedit /set {bootmgr} device partition=S: (replace S: with the correct letter temporarily). I've also seen cases where the system reserved partition is simply too small (under 100 MB) – you'll need to resize it using a third-party tool like EaseUS Partition Master or MiniTool Partition Wizard. That's rare, but it happens.

If none of that works, you might be dealing with a UEFI machine that requires the EFI System Partition to remain FAT32. In that case, you need a different approach: shrink the OS partition by 500 MB, create a new NTFS partition in that space, and manually assign it the system role. That's a longer fix – look up how to create a system partition with diskpart after shrinking the C: drive. It's tedious but doable.

One more thing: never convert the EFI System Partition (the FAT32 one with the EFI folder) to NTFS. That will brick your system. The partition I'm talking about is the one labeled "System Reserved" or just "System" – it's separate from the ESP on UEFI machines. If you're unsure, check the partition size: the ESP is always 100 MB for Windows, while the system reserved partition is 100-500 MB and may be empty or contain a Boot folder.

Try the conversion first – it's saved me dozens of times on Dell and HP machines. Good luck.