| Previous | Next |
| STATUS_FVE_NOT_ALLOWED_ON_CSV_STACK | STATUS_FVE_NOT_ALLOWED_TO_UPGRADE_WHILE_CONVERTING |
STATUS_FVE_NOT_ALLOWED_ON_CLUSTER
Meaning and context of STATUS_FVE_NOT_ALLOWED_ON_CLUSTER
The volume is part of a cluster, so a normally valid single-machine BitLocker operation has been rejected. This is not an access-control failure and it does not establish that encryption data is corrupt.
Determine whether the target is a physical disk resource, a CSV, or another clustered storage role, and use the supported cluster procedure rather than the generic local-disk path. Note the current owner node and application impact before any change.
Do not force a local operation by removing the volume from the cluster or disabling protection without a recovery and failover plan. Clustered BitLocker management relies on the cluster’s view of the storage and its ownership model.
Protect CSV and SAN storage | Use BitLocker with CSV | BitLocker status
Native status interpretation
STATUS_FVE_NOT_ALLOWED_ON_CLUSTER is 0xC0210035, an NTSTATUS error value. AllStat describes it as “This command cannot be performed on a volume when it is part of a cluster.”. The first useful question is which native API, IRP, protocol operation, or subsystem in the kernel, native API, or subsystem that returned the status produced that status.
Debugging sequence
- Preserve this result before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Log the operation associated with fve / allowed / on / cluster, the object or handle type, process and thread identity, and the state transition immediately before the return.
- When user mode receives this result, capture both the native status and the final Win32/COM error so the translation boundary remains visible.
Recovery considerations
A retry is appropriate only after the owner of this result has changed the state described by “This command cannot be performed on a volume when it is part of a cluster.”, or when its contract explicitly marks the status as transient. If the value reports corruption, invalid format, access policy, or a lifecycle mismatch, preserve evidence and correct that cause before repeating the request.
Looking for a different code? Search another status or error code.