What does HRESULT 0x803100C5 (FVE_E_DE_FIXED_DATA_NOT_SUPPORTED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This PC cannot support device encryption because unencrypted fixed data volumes are present.

Previous	Next
FVE_E_NOT_PROVISIONED_ON_ALL_VOLUMES	FVE_E_DE_HARDWARE_NOT_COMPLIANT

FVE_E_DE_FIXED_DATA_NOT_SUPPORTED

Read this as a state-machine result

FVE_E_DE_FIXED_DATA_NOT_SUPPORTED is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case automatic Device Encryption cannot establish its device-wide posture while an unsupported or unencrypted fixed data volume is present.

For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, note: Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. When diagnosing FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, remember: It evaluates platform eligibility, account-backed recovery escrow, all applicable fixed volumes and protection state; failure of Auto-DE does not automatically mean manual BitLocker is unavailable.

What the code does not prove

The closest misleading interpretation is a removable drive or an ordinary BitLocker manual configuration on one volume. For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, verify the returning method and state transition before assigning the incident to disk corruption, TPM failure or bad credentials.

Inspect the target, not just the message

For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, record all fixed-disk inventory, bus and media type, support status, encryption/protection state and policy scope. For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, capture manage-bde -status and the protector inventory for the exact volume GUID, not only the drive letter, because letters can change in WinRE, clusters and deployment environments.
Export BitLocker operational events for the FVE_E_DE_FIXED_DATA_NOT_SUPPORTED failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, note: Evaluate every fixed volume and the OS trust anchor together. When diagnosing FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, remember: Automatic unlock and device-wide compliance can fail because a secondary volume is outside policy.

A low-risk recovery path

For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, encrypt or remove the incompatible fixed-data configuration through a supported design before reevaluating automatic device encryption.
After correcting the FVE_E_DE_FIXED_DATA_NOT_SUPPORTED prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_DE_FIXED_DATA_NOT_SUPPORTED condition is still active.
Before a FVE_E_DE_FIXED_DATA_NOT_SUPPORTED remediation deletes protectors, changes firmware mode, resizes partitions or decrypts a production drive, verify that an independent recovery method is available and escrowed in the intended directory or account.

msinfo32.exe
powershell -NoProfile -Command "Get-BitLockerVolume | Format-Table MountPoint,VolumeType,VolumeStatus,ProtectionStatus"

Result interpretation for FVE_E_DE_FIXED_DATA_NOT_SUPPORTED

After correction, compare the new conversion, protection and lock state with the original snapshot. A different HRESULT after FVE_E_DE_FIXED_DATA_NOT_SUPPORTED is useful because it means the request crossed this boundary and reached the next prerequisite.

State checks specific to FVE_E_DE_FIXED_DATA_NOT_SUPPORTED

Checkpoint	How to interpret it for FVE_E_DE_FIXED_DATA_NOT_SUPPORTED
Before the call	Record the target identity and the pre-call automatic Device Encryption state. For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, the decisive boundary is that automatic Device Encryption cannot establish its device-wide posture while an unsupported or unencrypted fixed data volume is present.
At failure	Preserve all fixed-disk inventory, bus and media type, support status, encryption/protection state and policy scope. This proves whether FVE_E_DE_FIXED_DATA_NOT_SUPPORTED came from BitLocker itself or from a wrapper translating another result.
After correction	Encrypt or remove the incompatible fixed-data configuration through a supported design before reevaluating automatic device encryption. The FVE_E_DE_FIXED_DATA_NOT_SUPPORTED request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_DE_FIXED_DATA_NOT_SUPPORTED; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

For FVE_E_DE_FIXED_DATA_NOT_SUPPORTED, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_DE_FIXED_DATA_NOT_SUPPORTED now matches the intended design, that the protector inventory has not lost an independent recovery route, and that the next reboot or remount can unlock the volume. If the FVE_E_DE_FIXED_DATA_NOT_SUPPORTED request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

References

Reference set for FVE_E_DE_FIXED_DATA_NOT_SUPPORTED:

Looking for a different code? Search another status or error code.