| Previous | Next |
| STATUS_FVE_BAD_INFORMATION | STATUS_FVE_FAILED_WRONG_FS |
STATUS_FVE_TOO_SMALL
Meaning and context of STATUS_FVE_TOO_SMALL
This code is about usable free space during the requested operation. It should not be confused with STATUS_FVE_VOLUME_TOO_SMALL, which describes a drive whose overall capacity is too small for BitLocker protection.
Measure available space on the actual target volume and check whether another conversion, resize, backup, or maintenance task is consuming space or holding the volume state. The relevant remedy is to meet the operation’s free-space requirement or select an appropriate supported encryption workflow—not to remove recovery protectors.
After capacity is corrected, re-check the conversion and protection state before retrying. A later read or write failure during conversion is a different class of problem and is reported by the conversion I/O statuses.
BitLocker overview | BitLocker operations guide | manage-bde reference
Native status interpretation
STATUS_FVE_TOO_SMALL is 0xC0210003, an NTSTATUS error value. AllStat describes it as “The volume cannot be encrypted because it does not have enough free space.”. 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.
- Correlate this result with ETW, Event Viewer, protocol traces, or a dump from the component that owns fve / too / small; do not diagnose from translated text alone.
- 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 volume cannot be encrypted because it does not have enough free space.”, 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.