| Previous | Next |
| STATUS_FVE_INVALID_DATUM_TYPE | STATUS_FVE_ENH_PIN_INVALID |
STATUS_FVE_VOLUME_TOO_SMALL
The limiting value is the usable volume layout, not just the amount of free space reported by Explorer. BitLocker is rejecting the request before it can establish a supported protected-volume configuration.
Confirm the actual target volume, its role, file system, partition layout, and the requested encryption method. Do not try to solve this by deleting recovery protectors or by repeatedly starting conversion; neither action creates the required volume geometry.
Where a deployment needs a smaller OS or data partition, redesign the storage layout before enabling protection and retain recovery planning. This differs from STATUS_FVE_TOO_SMALL, which may surface in other BitLocker checks; use the exact code and operation context in logs.
BitLocker planning | BitLocker operations | NTSTATUS reference
Looking for a different code? Search another status or error code.