| Previous | Next |
| STATUS_FVE_BAD_PARTITION_SIZE | STATUS_FVE_FS_MOUNTED |
STATUS_FVE_FS_NOT_EXTENDED
Meaning and context of STATUS_FVE_FS_NOT_EXTENDED
Here the file system ends before the end of the volume. This is the inverse kind of layout inconsistency from STATUS_FVE_BAD_PARTITION_SIZE, where the file system appears to exceed the partition recorded in the partition table.
Confirm whether the volume was recently extended or whether the target selection accidentally points to a larger block volume than the intended file system. Check the partition and file-system boundaries before making a storage change; the status is not caused by an incorrect recovery key or a TPM problem.
When a supported resize is actually intended, complete and validate that storage operation first, then retry BitLocker from a stable layout. Mixing encryption conversion with an unresolved resize state makes later diagnostics much harder.
Microsoft NTSTATUS reference | BitLocker overview | BitLocker operations guide
Native status interpretation
STATUS_FVE_FS_NOT_EXTENDED is 0xC0210006, an NTSTATUS error value. AllStat describes it as “The file system does not extend to the end of the volume.”. 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 / fs / extended; 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 file system does not extend to the end of the volume.”, 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.