What does HRESULT 0x803100B1 (FVE_E_EDRIVE_DISALLOWED_BY_GP) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Group Policy settings do not allow the use of hardware-based encryption.

Previous	Next
FVE_E_EDRIVE_BAND_IN_USE	FVE_E_EDRIVE_INCOMPATIBLE_VOLUME

FVE_E_EDRIVE_DISALLOWED_BY_GP

Read this as a state-machine result

FVE_E_EDRIVE_DISALLOWED_BY_GP is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case effective policy explicitly disallows hardware-based BitLocker encryption on this drive type.

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.

What the code does not prove

The closest misleading interpretation is an incompatible drive or failed hardware-encryption dry run; policy blocks selection before capability is used. 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 effective OS/fixed/removable hardware-encryption policy, device type, management source and requested encryption method. 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.

Note: Firmware, storage drivers and security-band state can change independently. When diagnosing this result, remember: A successful filesystem check does not validate the eDrive management channel.

A low-risk recovery path

use software encryption or change the managed policy after security review; do not alter drive firmware to bypass policy.
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"

Result Interpretation

After correction, compare the new conversion, protection and lock state with the original snapshot. A different HRESULT after this result is useful because it means the request crossed this boundary and reached the next prerequisite.

Capability and policy answer different questions

An SSD can advertise encrypted-drive capability and still be intentionally excluded by enterprise policy. The correct evidence is the effective hardware-encryption setting for the target drive class, together with the final encryption method reported by BitLocker. Vendor utilities cannot override a Windows policy decision safely.

When software encryption is permitted, select it explicitly and verify conversion starts. When hardware encryption is mandatory, remediate policy deployment or device selection rather than silently accepting an unprotected volume.

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 effective policy explicitly disallows hardware-based BitLocker encryption on this drive type.
At failure	Preserve effective OS/fixed/removable hardware-encryption policy, device type, management source and requested encryption method. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Use software encryption or change the managed policy after security review; do not alter drive firmware to bypass policy. 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.

References

Reference set for it:

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