What does HRESULT 0x803100B4 (FVE_E_EDRIVE_DV_NOT_SUPPORTED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Discovery Volumes are not supported for volumes using hardware encryption.

Previous	Next
FVE_E_NOT_ALLOWED_TO_UPGRADE_WHILE_CONVERTING	FVE_E_NO_PREBOOT_KEYBOARD_DETECTED

FVE_E_EDRIVE_DV_NOT_SUPPORTED

The failed prerequisite

FVE_E_EDRIVE_DV_NOT_SUPPORTED / 0x803100B4 marks a rejected BitLocker transition: BitLocker To Go discovery volumes are not supported when the target uses hardware encryption.

Note: Hardware encryption is not inferred from the SSD marketing name. When diagnosing this result, remember: Verify the encryption method reported by BitLocker and the drive capability returned through the storage and volume-encryption providers.

Diagnostic map

Layer	hardware-encrypted drive negotiation
Proof to collect	hardware-encryption state, removable-media role, discovery-volume request and compatibility requirement for older readers
Different condition	a discovery volume rejected because of filesystem type or Group Policy
First safe change	choose software encryption if a discovery volume is genuinely required, or omit the legacy discovery feature

Note: Hardware-encrypted drives add firmware, storage-driver and drive-security state below the normal BitLocker volume provider. When diagnosing this result, remember: BitLocker can reject the hardware path before conversion starts, and policy may or may not permit a fallback to software encryption.

A focused verification sequence

record hardware-encryption state, removable-media role, discovery-volume request and compatibility requirement for older readers. 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.

Recommended operational response

choose software encryption if a discovery volume is genuinely required, or omit the legacy discovery feature.
After correcting the result prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the condition is still active.
Before a this result 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.

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

Interpretation checkpoint

This result identifies a condition but not every owner of the surrounding state. Preserve the original caller, volume GUID and event sequence so the correction is applied at the right layer.

State checks specific to it

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 BitLocker To Go discovery volumes are not supported when the target uses hardware encryption.
At failure	Preserve hardware-encryption state, removable-media role, discovery-volume request and compatibility requirement for older readers. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Choose software encryption if a discovery volume is genuinely required, or omit the legacy discovery feature. 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 it 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 references

Reference set for it:

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