What does HRESULT 0x80310048 (FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions.

Previous	Next
FVE_E_FS_NOT_EXTENDED	FVE_E_NO_LICENSE

FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED

Where the operation stops

The value 0x80310048, named FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, is returned when the operating-system volume is booting through firmware that does not meet the BitLocker startup path required by the requested configuration. It belongs to the hardware-encrypted drive negotiation part of BitLocker rather than to generic file I/O.

Note: If policy permits software fallback, verify the final method explicitly. When diagnosing this result, remember: A failed hardware dry run can otherwise leave an administrator assuming protection that never started. Note: Hardware-encrypted drives add firmware, storage-driver and drive-security state below the normal BitLocker volume provider. When diagnosing it, remember: BitLocker can reject the hardware path before conversion starts, and policy may or may not permit a fallback to software encryption.

Question	What to verify
Which object failed?	The exact volume GUID, protector GUID, certificate or API target supplied by the caller.
Which state matters?	UEFI versus legacy BIOS boot mode, disk partition style, firmware version, measured-boot capability and requested OS-volume protector.
What is the nearest false lead?	a disabled TPM or invalid Secure Boot setting; firmware type is evaluated before those protector details.

Build a minimal diagnostic record

record UEFI versus legacy BIOS boot mode, disk partition style, firmware version, measured-boot capability and requested OS-volume protector. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
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 result failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

Change only the failed prerequisite

align firmware and disk layout with a supported boot mode, update firmware if appropriate, and retest the BitLocker hardware check. Collect a fresh state snapshot and issue a single retry from the same management layer.

manage-bde -status
powershell -NoProfile -Command "Get-CimInstance -Namespace root/cimv2/security/MicrosoftVolumeEncryption -Class Win32_EncryptableVolume"

Do not delete all key protectors, clear a TPM, reformat a partition or decrypt the volume as a generic response to this result; those actions affect different trust layers and can destroy the easiest recovery route.

State checks specific to the result

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call hardware-encrypted drive negotiation state. The decisive boundary is that the operating-system volume is booting through firmware that does not meet the BitLocker startup path required by the requested configuration.
At failure	Preserve UEFI versus legacy BIOS boot mode, disk partition style, firmware version, measured-boot capability and requested OS-volume protector. This proves whether this result came from BitLocker itself or from a wrapper translating another result.
After correction	Align firmware and disk layout with a supported boot mode, update firmware if appropriate, and retest the BitLocker hardware check. The request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for it; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

Success means more than the absence of a dialog. Confirm that the condition represented by this result 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 request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

Official documentation

Reference set for it:

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