| 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.
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 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
Firmware, storage drivers and security-band state can change independently. 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.
manage-bde -status
powershell -NoProfile -Command "Get-CimInstance -Namespace root/cimv2/security/MicrosoftVolumeEncryption -Class Win32_EncryptableVolume"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 FVE_E_EDRIVE_DISALLOWED_BY_GP
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call hardware-encrypted drive negotiation state. 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. |
References
Looking for a different code? Search another status or error code.