What does HRESULT 0x80310056 (FVE_E_HIDDEN_VOLUME) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The hidden drive cannot be encrypted.

Previous	Next
FVE_E_MOR_FAILED	FVE_E_TRANSIENT_STATE

FVE_E_HIDDEN_VOLUME

Why this is not a generic disk error

The practical meaning of FVE_E_HIDDEN_VOLUME is that the target is a hidden volume that BitLocker intentionally excludes from ordinary encryption management. The HRESULT is 0x80310056.

Three decisions before remediation

Is the FVE_E_HIDDEN_VOLUME target correct?: For FVE_E_HIDDEN_VOLUME, use the volume or protector GUID and confirm its role; do not rely only on a drive letter or friendly name.
Is the FVE_E_HIDDEN_VOLUME request allowed?: For FVE_E_HIDDEN_VOLUME, resolve effective policy, Windows edition, caller token and management source for the volume state and geometry operation.
Is the FVE_E_HIDDEN_VOLUME state stable?: For FVE_E_HIDDEN_VOLUME, record conversion, protection, lock and reboot status before modifying anything.

For FVE_E_HIDDEN_VOLUME, note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing FVE_E_HIDDEN_VOLUME, remember: Two volumes can both appear “encrypted” in a UI while being in very different states for a management API. For FVE_E_HIDDEN_VOLUME, note: Conversion status and protection status answer different questions: sectors can be encrypted while protectors are suspended, and a fully decrypted volume can still contain stale management context in a caller.

Why a common workaround is wrong

This should not be diagnosed as a volume without a drive letter; mount-point visibility and the partition hidden attribute are different properties. For FVE_E_HIDDEN_VOLUME, that nearby condition needs a different corrective action and may produce a similar user-facing message.

Confirm the returning layer

For FVE_E_HIDDEN_VOLUME, record partition GPT attributes or MBR type, volume GUID, mount points, role in the boot/recovery layout and the caller-selected device path. For FVE_E_HIDDEN_VOLUME, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_HIDDEN_VOLUME, 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_HIDDEN_VOLUME failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"

Correct the configuration deliberately

For FVE_E_HIDDEN_VOLUME, identify the partition role before changing attributes; never expose or encrypt an OEM/recovery partition merely to bypass the error.
After correcting the FVE_E_HIDDEN_VOLUME prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_HIDDEN_VOLUME condition is still active.
Before a FVE_E_HIDDEN_VOLUME 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.

Treat FVE_E_HIDDEN_VOLUME as a state label rather than a complete recovery plan. Confirm a successful retry with an updated BitLocker state query and a verified recovery path.

State checks specific to FVE_E_HIDDEN_VOLUME

Checkpoint	How to interpret it for FVE_E_HIDDEN_VOLUME
Before the call	Record the target identity and the pre-call volume state and geometry state. For FVE_E_HIDDEN_VOLUME, the decisive boundary is that the target is a hidden volume that BitLocker intentionally excludes from ordinary encryption management.
At failure	Preserve partition GPT attributes or MBR type, volume GUID, mount points, role in the boot/recovery layout and the caller-selected device path. This proves whether FVE_E_HIDDEN_VOLUME came from BitLocker itself or from a wrapper translating another result.
After correction	Identify the partition role before changing attributes; never expose or encrypt an OEM/recovery partition merely to bypass the error. The FVE_E_HIDDEN_VOLUME request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_HIDDEN_VOLUME; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

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

References

Reference set for FVE_E_HIDDEN_VOLUME:

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