| Previous | Next |
| STATUS_FVE_ENH_PIN_INVALID | STATUS_FVE_WIPE_NOT_ALLOWED_ON_TP_STORAGE |
STATUS_FVE_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE
Meaning and context of STATUS_FVE_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE
Thin-provisioned storage is allocated on demand, so BitLocker restricts this scenario to Used Space Only encryption. The status is a storage-semantics and policy mismatch, not a damaged encryption key or a failed TPM protector.
Confirm whether the target is a thin-provisioned virtual disk, Storage Spaces volume, or other layered storage before changing BitLocker policy. Compare the required encryption method with what the backing store supports, and record the conversion status before any retry.
Do not force a full-volume policy onto a volume that reports this status. Choose a supported Used Space Only deployment or redesign the storage layer. Wiping free space is a separate operation with its own restrictions and status codes.
BitLocker thin-provisioned storage note | BitLocker status | BitLocker operations
Native status interpretation
STATUS_FVE_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE is 0xC0210032, an NTSTATUS error value. AllStat describes it as “BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage.”. 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 / full / encryption / allowed / on, 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 “BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage.”, 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.