HRESULT 0x80310047 (FVE_E_FS_NOT_EXTENDED): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again.

Previous	Next
FVE_E_FIPS_DISABLE_PROTECTION_NOT_ALLOWED	FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED

FVE_E_FS_NOT_EXTENDED

The exact BitLocker boundary

FVE_E_FS_NOT_EXTENDED (0x80310047) identifies the point where the filesystem does not occupy the expected usable extent of the partition, so BitLocker cannot lay out its metadata and conversion boundary safely. Note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing this result, remember: Two volumes can both appear “encrypted” in a UI while being in very different states for a management API.

Note: Conversion status and protection status answer different questions: sectors can be encrypted while protectors are suspended, and a fully decrypted volume can still contain stale management context in a caller.

Do not confuse it with a nearby failure

Keep this separate from a partition that is merely low on free space; the mismatch concerns filesystem geometry versus partition geometry. That distinction determines whether the next check belongs to policy, protector inventory, volume geometry, firmware, account escrow or the calling application's buffer contract.

Evidence that distinguishes the condition

record partition start and length, filesystem-reported size, GPT/MBR layout, recent resize history and chkdsk/read-only filesystem health results. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
capture manage-bde -status and the protector inventory for the exact volume GUID, not only the drive letter, because letters can change in WinRE, clusters and deployment environments.
Export BitLocker operational events for the result failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"

Safe corrective sequence

repair or extend the filesystem to match the partition using supported storage tools, then rerun a status query before enabling encryption.
After correcting the result prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the condition is still active.
Before a this result remediation deletes protectors, changes firmware mode, resizes partitions or decrypts a production drive, verify that an independent recovery method is available and escrowed in the intended directory or account.

The boundary above identifies which BitLocker state must change before a retry can be meaningful; repeating the call without changing that state only adds noise.

State checks specific to the result

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call volume state and geometry state. The decisive boundary is that the filesystem does not occupy the expected usable extent of the partition, so BitLocker cannot lay out its metadata and conversion boundary safely.
At failure	Preserve partition start and length, filesystem-reported size, GPT/MBR layout, recent resize history and chkdsk/read-only filesystem health results. This proves whether this result came from BitLocker itself or from a wrapper translating another result.
After correction	Repair or extend the filesystem to match the partition using supported storage tools, then rerun a status query before enabling encryption. The request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for it; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

Success means more than the absence of a dialog. Confirm that the condition represented by this result now matches the intended design, that the protector inventory has not lost an independent recovery route, and that the next reboot or remount can unlock the volume. If the request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

References

Reference set for it:

Looking for a different code? Search another status or error code.