| 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?
- 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?
- Resolve effective policy, Windows edition, caller token and management source for the volume state and geometry operation.
- Is the result state stable?
- Record conversion, protection, lock and reboot status before modifying anything.
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.
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.
manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"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 FVE_E_DV_NOT_SUPPORTED_ON_FS
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call volume state and geometry state. 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. |
| 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. |
References
Looking for a different code? Search another status or error code.