| 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.
If policy permits software fallback, verify the final method explicitly. A failed hardware dry run can otherwise leave an administrator assuming protection that never started. Hardware-encrypted drives add firmware, storage-driver and drive-security state below the normal BitLocker volume provider. 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.
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.
manage-bde -status
powershell -NoProfile -Command "Get-CimInstance -Namespace root/cimv2/security/MicrosoftVolumeEncryption -Class Win32_EncryptableVolume"State checks specific to FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call hardware-encrypted drive negotiation state. 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. |
Official documentation
Looking for a different code? Search another status or error code.