What does HRESULT 0x80310016 (FVE_E_BAD_DATA) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The data is not valid.

Previous	Next
FVE_E_NOT_SUPPORTED	FVE_E_VOLUME_NOT_BOUND

FVE_E_BAD_DATA

The exact BitLocker boundary

FVE_E_BAD_DATA (0x80310016) identifies the point where BitLocker metadata or a management input was parsed but failed structural validation. For FVE_E_BAD_DATA, note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing FVE_E_BAD_DATA, remember: Two volumes can both appear “encrypted” in a UI while being in very different states for a management API.

For FVE_E_BAD_DATA, 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 locked volume or an incorrect recovery secret, which fail at access or authentication rather than data validation. For FVE_E_BAD_DATA, 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

For FVE_E_BAD_DATA, record the exact API method, input buffer length, volume metadata version, first failing offset and whether another BitLocker tool can read the same volume. For FVE_E_BAD_DATA, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_BAD_DATA, 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 FVE_E_BAD_DATA 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

For FVE_E_BAD_DATA, stop writes to the affected volume, preserve recovery material, and reproduce the failure with a read-only status query before attempting repair.
After correcting the FVE_E_BAD_DATA prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_BAD_DATA condition is still active.
Before a FVE_E_BAD_DATA 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.

For FVE_E_BAD_DATA, 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.

Validate structure before attempting recovery

This result is deliberately broader than an authentication failure: BitLocker received bytes or metadata but could not accept their internal structure. The first question is which object was being parsed—volume metadata, a key package, a protector blob or caller-supplied management data. Record that object and the exact read-only method that first rejected it.

A successful filesystem mount does not validate BitLocker metadata, and a failed recovery password does not prove structural corruption. Preserve the disk image or metadata evidence before any operation that rewrites headers.

State checks specific to FVE_E_BAD_DATA

Checkpoint	How to interpret it for FVE_E_BAD_DATA
Before the call	Record the target identity and the pre-call volume state and geometry state. For FVE_E_BAD_DATA, the decisive boundary is that BitLocker metadata or a management input was parsed but failed structural validation.
At failure	Preserve the exact API method, input buffer length, volume metadata version, first failing offset and whether another BitLocker tool can read the same volume. This proves whether FVE_E_BAD_DATA came from BitLocker itself or from a wrapper translating another result.
After correction	Stop writes to the affected volume, preserve recovery material, and reproduce the failure with a read-only status query before attempting repair. The FVE_E_BAD_DATA request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_BAD_DATA; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

For FVE_E_BAD_DATA, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_BAD_DATA 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 FVE_E_BAD_DATA request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

References

Reference set for FVE_E_BAD_DATA:

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