| Previous | Next |
| STATUS_FVE_BAD_DATA | STATUS_FVE_NOT_DATA_VOLUME |
STATUS_FVE_VOLUME_NOT_BOUND
Meaning and context of STATUS_FVE_VOLUME_NOT_BOUND
This status concerns a required binding relationship between the volume and the system context expected by the operation. It is not a statement that the volume is unencrypted, and it is not the same as a recovery authentication failure.
Verify the intended role of the target and the management workflow that created or expects the binding. A data-volume task, an operating-system-volume task, and a startup-protector task do not have interchangeable prerequisites.
Inspect the actual BitLocker volume type and protector configuration before changing firmware or TPM settings. If the operation is being applied to a detached or migrated disk, establish whether the task is supported in that context instead of trying to bind it by changing recovery credentials.
Microsoft NTSTATUS reference | BitLocker planning guide | BitLocker operations guide
Native status interpretation
STATUS_FVE_VOLUME_NOT_BOUND is 0xC021000B, an NTSTATUS error value. AllStat describes it as “The volume is not bound to the system.”
Looking for a different code? Search another status or error code.