HRESULT 0x80310071 (FVE_E_DV_NOT_ALLOWED_BY

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go.

Previous	Next
FVE_E_DV_NOT_SUPPORTED_ON_FS	FVE_E_POLICY_USER_CERTIFICATE_NOT_ALLOWED

FVE_E_DV_NOT_ALLOWED_BY_GP

The failed prerequisite

FVE_E_DV_NOT_ALLOWED_BY_GP / 0x80310071 marks a rejected BitLocker transition: Group Policy forbids creating the BitLocker To Go discovery volume requested by the caller.

For FVE_E_DV_NOT_ALLOWED_BY_GP, note: When policy is the boundary, retrying under SYSTEM does not necessarily help: policy can forbid the operation for every caller. When diagnosing FVE_E_DV_NOT_ALLOWED_BY_GP, remember: Separate authorization from allow/require/disallow settings before changing identities.

Diagnostic map

Layer	policy and authorization
Proof to collect	effective removable-drive policy, management source, target media type and the exact creation command
Different condition	FVE_E_DV_NOT_SUPPORTED_ON_FS, where the policy allows the operation but the filesystem cannot support it
First safe change	change policy centrally if legacy reader deployment is still required; do not work around managed restrictions on individual machines

For FVE_E_DV_NOT_ALLOWED_BY_GP, note: BitLocker evaluates the target volume together with effective Group Policy or MDM policy, Windows edition, caller authorization and the requested protector or management method. When diagnosing FVE_E_DV_NOT_ALLOWED_BY_GP, remember: A policy HRESULT therefore describes a rejected configuration decision, not evidence that encrypted sectors are damaged.

A focused verification sequence

For FVE_E_DV_NOT_ALLOWED_BY_GP, record effective removable-drive policy, management source, target media type and the exact creation command. For FVE_E_DV_NOT_ALLOWED_BY_GP, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_DV_NOT_ALLOWED_BY_GP, 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 FVE_E_DV_NOT_ALLOWED_BY_GP 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

For FVE_E_DV_NOT_ALLOWED_BY_GP, change policy centrally if legacy reader deployment is still required; do not work around managed restrictions on individual machines.
After correcting the FVE_E_DV_NOT_ALLOWED_BY_GP prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_DV_NOT_ALLOWED_BY_GP condition is still active.
Before a FVE_E_DV_NOT_ALLOWED_BY_GP 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
gpresult /h bitlocker-policy.html

Interpretation checkpoint

FVE_E_DV_NOT_ALLOWED_BY_GP 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 FVE_E_DV_NOT_ALLOWED_BY_GP

Checkpoint	How to interpret it for FVE_E_DV_NOT_ALLOWED_BY_GP
Before the call	Record the target identity and the pre-call policy and authorization state. For FVE_E_DV_NOT_ALLOWED_BY_GP, the decisive boundary is that Group Policy forbids creating the BitLocker To Go discovery volume requested by the caller.
At failure	Preserve effective removable-drive policy, management source, target media type and the exact creation command. This proves whether FVE_E_DV_NOT_ALLOWED_BY_GP came from BitLocker itself or from a wrapper translating another result.
After correction	Change policy centrally if legacy reader deployment is still required; do not work around managed restrictions on individual machines. The FVE_E_DV_NOT_ALLOWED_BY_GP request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_DV_NOT_ALLOWED_BY_GP; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

For FVE_E_DV_NOT_ALLOWED_BY_GP, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_DV_NOT_ALLOWED_BY_GP 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_DV_NOT_ALLOWED_BY_GP request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

Official references

Reference set for FVE_E_DV_NOT_ALLOWED_BY_GP:

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