What does HRESULT 0x803100AD (FVE_E_NOT_ALLOWED_ON_CSV_STACK) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This command can only be performed from the coordinator node for the specified CSV volume.

Previous	Next
FVE_E_NO_TPM_WITH_PASSPHRASE	FVE_E_NOT_ALLOWED_ON_CLUSTER

FVE_E_NOT_ALLOWED_ON_CSV_STACK

Why this is not a generic disk error

The practical meaning of FVE_E_NOT_ALLOWED_ON_CSV_STACK is that the operation was issued from a non-coordinator node for a Cluster Shared Volume. The HRESULT is 0x803100AD.

Three decisions before remediation

Is the result target correct?: Use the volume or protector GUID and confirm its role; do not rely only on a drive letter or friendly name.
Is the result request allowed?: Resolve effective policy, Windows edition, caller token and management source for the cluster or thin-storage coordination operation.
Is the result state stable?: Record conversion, protection, lock and reboot status before modifying anything.

Cluster Shared Volumes and thin-provisioned storage add ownership and allocation semantics that a standalone disk does not have. BitLocker operations must respect the CSV coordinator and must not force thin backing storage to allocate every virtual extent. Thin provisioning reports virtual size separately from allocated backing space. Operations that write every free extent can consume the entire pool without adding user data.

Why a common workaround is wrong

This should not be diagnosed as a command disallowed on all clustered volumes; this operation is valid only at the CSV coordinator. That nearby condition needs a different corrective action and may produce a similar user-facing message.

Confirm the returning layer

Record CSV owner/coordinator node, volume path, cluster resource state, caller node and the exact BitLocker operation.

Get-ClusterSharedVolume | Format-List *
manage-bde -status

State checks specific to FVE_E_NOT_ALLOWED_ON_CSV_STACK

Stage	How to interpret it
Before the call	Record the target identity and the pre-call cluster or thin-storage coordination state. The operation was issued from a non-coordinator node for a Cluster Shared Volume.
At failure	Preserve CSV owner/coordinator node, volume path, cluster resource state, caller node and the exact BitLocker operation.
After correction	Move execution to the current coordinator or use cluster-aware tooling rather than addressing the CSV from an arbitrary node.

References

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