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 condition

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. The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. Two volumes can both appear “encrypted” in a UI while being in very different states for a management API.

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.

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

State checks specific to FVE_E_FS_NOT_EXTENDED

Stage	How to interpret it
Before the call	Record the target identity and the pre-call volume state and geometry state. 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.

References

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