HRESULT 0x80310070 (FVE_E_DV_NOT_SUPPORTED_ON

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The selected discovery drive type is incompatible with the file system on the drive. BitLocker To Go discovery drives must be created on FAT formatted drives.

Previous	Next
FVE_E_VOLUME_TOO_SMALL	FVE_E_DV_NOT_ALLOWED_BY_GP

FVE_E_DV_NOT_SUPPORTED_ON_FS

Why this is not a generic disk error

The practical meaning of FVE_E_DV_NOT_SUPPORTED_ON_FS is that a BitLocker To Go discovery volume was requested on a filesystem that cannot host the discovery-reader layout. The HRESULT is 0x80310070.

Three decisions before remediation

Is the result target correct?: For this result, use the volume or protector GUID and confirm its role; do not rely only on a drive letter or friendly name.
Is the result request allowed?: For this result, resolve effective policy, Windows edition, caller token and management source for the volume state and geometry operation.
Is the result state stable?: For this result, record conversion, protection, lock and reboot status before modifying anything.

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.

Why a common workaround is wrong

This should not be diagnosed as ordinary BitLocker encryption support for the data volume; discovery-volume compatibility is a separate legacy interoperability feature. That nearby condition needs a different corrective action and may produce a similar user-facing message.

Confirm the returning layer

record filesystem type, removable-media geometry, requested discovery-volume operation and whether the target already contains user data. 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 *"

Correct the configuration deliberately

reformat only an appropriate removable target with the supported filesystem after backing up data, or omit the discovery volume if it is not required.
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 it 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.

Treat it as a state label rather than a complete recovery plan. Confirm a successful retry with an updated BitLocker state query and a verified recovery path.

A discovery volume is not the encrypted payload volume

The legacy BitLocker To Go discovery feature places a reader application on a small compatible filesystem so older Windows systems can access protected removable media. Its filesystem requirement belongs to that reader area, not to the main encrypted data area. Record exactly which partition the API selected before formatting anything.

If compatibility with legacy readers is unnecessary, omit the discovery volume. If it is required, create it only on suitable removable media after backing up user data and confirming policy permits the feature.

State checks specific to it

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 a BitLocker To Go discovery volume was requested on a filesystem that cannot host the discovery-reader layout.
At failure	Preserve filesystem type, removable-media geometry, requested discovery-volume operation and whether the target already contains user data. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Reformat only an appropriate removable target with the supported filesystem after backing up data, or omit the discovery volume if it is not required. 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 it 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.