| Previous | Next |
| FVE_E_INVALID_DATUM_TYPE | FVE_E_MULTIPLE_NKP_CERTS |
FVE_E_EFI_ONLY
Read this as a state-machine result
FVE_E_EFI_ONLY is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case the requested BitLocker feature depends on UEFI services and cannot run on a legacy BIOS boot path.
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.
What the code does not prove
The closest misleading interpretation is FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED, which can cover a broader unsupported firmware configuration for OS-volume enablement. 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
- Record firmware mode, disk partition style, active boot loader, Secure Boot state and the feature being invoked.
Firmware, storage drivers and security-band state can change independently. A successful filesystem check does not validate the eDrive management channel.
manage-bde -status
powershell -NoProfile -Command "Get-CimInstance -Namespace root/cimv2/security/MicrosoftVolumeEncryption -Class Win32_EncryptableVolume"State checks specific to FVE_E_EFI_ONLY
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call hardware-encrypted drive negotiation state. The requested BitLocker feature depends on UEFI services and cannot run on a legacy BIOS boot path. |
| At failure | Preserve firmware mode, disk partition style, active boot loader, Secure Boot state and the feature being invoked. |
| After correction | Migrate to a supported UEFI/GPT boot configuration through documented deployment procedures before retrying the feature. |
References
Looking for a different code? Search another status or error code.