Fix FVE_E_RELATIVE_PATH (0X80310032) BitLocker Error

What Triggers FVE_E_RELATIVE_PATH (0X80310032)

You're trying to save your BitLocker recovery key, and Windows throws back the error: "The file cannot be saved to a relative path" with code 0X80310032. It usually happens when you're using the Manage BitLocker wizard or a PowerShell command and you type something like ."key.txt" or Backup\key.txt—paths that don't start with a drive letter. BitLocker needs an absolute path. I've seen this on Windows 10 version 2004 and Windows 11 after a TPM firmware update. The fix is straightforward.

Fix 1: The 30-Second Quick Fix — Full Path in the Wizard

If you're using the BitLocker Drive Encryption control panel, here's the simplest way to bypass the error.

1. Open the Start menu and type "BitLocker." Click Manage BitLocker.
2. Under your system drive (usually C:), click Back up your recovery key.
3. The wizard asks where to save. Choose Save to a file.
4. In the Save As window, DON'T just type a filename. Instead, navigate to a folder like C:\Backup or use the address bar to type C:\Backup\MyKey.txt. The key is the path starts with a drive letter.
5. Click Save. If you still get the error, make sure the folder exists—create it first if needed.

What you should see: After clicking Save, the window closes and you get a green checkmark saying "Recovery key backed up." That's it. 90% of users are done here.

Fix 2: The 5-Minute Moderate Fix — PowerShell with Absolute Path

The wizard is finicky. If it still complains, use PowerShell. This works on Windows 10/11 Pro and Enterprise.

1. Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin).
2. Type this command to see your BitLocker volumes: manage-bde -status
3. Note the drive letter. Usually it's C:.
4. Now run:

   manage-bde -protectors -get C:

   This shows your recovery key ID. You'll need it.
5. Back up the key using an absolute path:

   manage-bde -protectors -adbackup C: -id {your-recovery-key-ID}

6. Or save to a file with:

   manage-bde -protectors -save C: -path C:\Backup\RecoveryKey.txt

Important: The path C:\Backup\RecoveryKey.txt must exist. If the folder doesn't exist, create it first: mkdir C:\Backup

What you'll see: The command runs silently. No error message means it worked. To verify, check that the file exists. If you get "ERROR: Relative path specified," then you forgot the drive letter—go back and fix it.

Fix 3: The 15+ Minute Advanced Fix — Registry and Group Policy Check

If neither fix works, something deeper is blocking absolute paths. This is rare—I've only seen it on domain-joined machines with strict group policies or corrupted registry entries.

Step 1: Check Group Policy

1. Press Win + R, type gpedit.msc, and hit Enter. (Skip this on Windows 10/11 Home—you won't have it.)
2. Go to Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drives.
3. Find Choose how BitLocker-protected operating system drives can be recovered. Double-click it.
4. If it's set to Enabled, check under "Configure recovery folder"—make sure it's a full path like C:\BitLockerKeys. If it says %USERPROFILE% or anything relative, change it to an absolute path.
5. Click OK, then run gpupdate /force in Command Prompt.

Step 2: Check Registry for Stuck Relative Path

1. Open Registry Editor: press Win + R, type regedit, hit Enter.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\FVE

3. Look for a value named RecoveryKeyFilePath. If it exists and contains a relative path like .\, double-click it and change it to an absolute path, e.g., C:\BitLockerKeys.
4. Close Registry Editor and restart your computer.

Step 3: Alternative — Save to Azure AD or Microsoft Account

If your machine is Azure AD joined or uses a Microsoft account, skip the file path entirely. In the BitLocker wizard, choose Save to your Microsoft account or Save to Azure AD. That stores the key online and avoids the path problem completely. It's not a real fix, but it works.

Why Relative Paths Break BitLocker

BitLocker is paranoid by design. It's built to protect your data even if the OS is compromised. Relative paths like .\ or ..\ depend on the current directory, which can change depending on how the wizard runs. An absolute path locks in the exact location. Microsoft made this a hard error because they're not taking chances. Frustrating? Sure. But it's a deliberate safety measure.

When to Give Up and Call Support

If you've tried all three fixes and still get the error, your TPM might be failing or your BitLocker metadata is corrupt. In that case, back up your data, decrypt the drive (if possible), and re-enable BitLocker fresh. Use manage-bde -off C: to decrypt—it takes hours. Then turn it back on with manage-bde -on C:. That usually nukes whatever gremlin is causing the path issue.

You've got this. Start with Fix 1. Nine out of ten users never need Fix 2.