| 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. For FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, it belongs to the hardware-encrypted drive negotiation part of BitLocker rather than to generic file I/O.
For FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, note: If policy permits software fallback, verify the final method explicitly. When diagnosing FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, remember: A failed hardware dry run can otherwise leave an administrator assuming protection that never started. For FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, note: Hardware-encrypted drives add firmware, storage-driver and drive-security state below the normal BitLocker volume provider. When diagnosing FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, 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? | For FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, 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
- For
FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, record UEFI versus legacy BIOS boot mode, disk partition style, firmware version, measured-boot capability and requested OS-volume protector. ForFVE_E_FIRMWARE_TYPE_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_FIRMWARE_TYPE_NOT_SUPPORTED, capturemanage-bde -statusand 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_FIRMWARE_TYPE_NOT_SUPPORTEDfailure 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. For FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, 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 FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED; those actions affect different trust layers and can destroy the easiest recovery route.
State checks specific to FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED
| Checkpoint | How to interpret it for FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED |
|---|---|
| Before the call | Record the target identity and the pre-call hardware-encrypted drive negotiation state. For FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, 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 FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED 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 FVE_E_FIRMWARE_TYPE_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_FIRMWARE_TYPE_NOT_SUPPORTED; a successful management call is incomplete if the next boot cannot unlock the volume. |
Verification after the change
For FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_FIRMWARE_TYPE_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_FIRMWARE_TYPE_NOT_SUPPORTED request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.
Official documentation
Reference set for FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED:
- Microsoft: Configure BitLocker policy
- Microsoft: Encrypted hard drives
- Microsoft: GetHardwareEncryptionStatus method
- Microsoft: BitLocker operations guide
Looking for a different code? Search another status or error code.