| Previous | Next |
| STATUS_FVE_FAILED_AUTHENTICATION | STATUS_FVE_KEYFILE_NOT_FOUND |
STATUS_FVE_NOT_OS_VOLUME
The operation has operating-system-volume semantics, such as boot-time protector or validation requirements, but the selected target is not the boot OS volume. This is a role mismatch, not proof that the target lacks BitLocker protection.
Identify the actual Windows boot volume in the current environment before proceeding. In recovery, setup, or attached-disk scenarios, drive letters can differ from the normal running system and are not a reliable proxy for the OS volume.
Use the workflow intended for the actual target role. For the opposite mismatch—using a data-volume operation against another role—BitLocker reports STATUS_FVE_NOT_DATA_VOLUME.
BitLocker overview | BitLocker operations guide | manage-bde reference
Looking for a different code? Search another status or error code.