| Previous | Next |
| STATUS_FVE_VIRTUALIZED_SPACE_TOO_BIG | STATUS_FVE_VOLUME_TOO_SMALL |
STATUS_FVE_INVALID_DATUM_TYPE
Meaning and context of STATUS_FVE_INVALID_DATUM_TYPE
A BitLocker management datum is structured metadata, not a user file. This status says the reader encountered a type it does not recognize, which makes version compatibility, malformed metadata, and unsupported management information more relevant than ordinary access permissions.
Record the Windows build, BitLocker version reported by the volume, management tool, and whether the volume was created or modified on another Windows release. Do not edit the volume at sector level or remove protectors simply because an older tool cannot interpret a datum.
Use a supported current management interface to inspect the volume, then preserve recovery material before attempting migration or recovery. The WMI provider and manage-bde -status reveal the high-level state without requiring raw metadata changes.
Win32_EncryptableVolume | BitLocker status | NTSTATUS reference
Native status interpretation
STATUS_FVE_INVALID_DATUM_TYPE is 0xC021002A, an NTSTATUS error value. AllStat describes it as “The management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version.”. 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 / datum / type, the object or handle type, process and thread identity, and the state transition immediately before the return.
- For kernel I/O, keep the device stack, IRP major/minor function, request parameters, completion routine, and the first component that completed the request with this result.
Recovery considerations
A retry is appropriate only after the owner of this result has changed the state described by “The management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version.”, 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.