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?: For this result, 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?: For this result, resolve effective policy, Windows edition, caller token and management source for the cluster or thin-storage coordination operation.
Is the result state stable?: For this result, record conversion, protection, lock and reboot status before modifying anything.

Note: Cluster Shared Volumes and thin-provisioned storage add ownership and allocation semantics that a standalone disk does not have. When diagnosing this result, remember: BitLocker operations must respect the CSV coordinator and must not force thin backing storage to allocate every virtual extent. Note: Thin provisioning reports virtual size separately from allocated backing space. When diagnosing it, remember: 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. 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.

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

Correct the configuration deliberately

move execution to the current coordinator or use cluster-aware tooling rather than addressing the CSV from an arbitrary node.
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 it 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 it 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 it

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call cluster or thin-storage coordination state. The decisive boundary is that 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. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Move execution to the current coordinator or use cluster-aware tooling rather than addressing the CSV from an arbitrary node. 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.