| Previous | Next |
| FVE_E_DE_VOLUME_NOT_SUPPORTED | FVE_E_ADBACKUP_NOT_ENABLED |
FVE_E_EOW_NOT_SUPPORTED_IN_VERSION
Why this is not a generic disk error
The practical meaning of FVE_E_EOW_NOT_SUPPORTED_IN_VERSION is that Encrypt-On-Write mode was requested on a Windows version that does not implement that BitLocker conversion mode. The HRESULT is 0x803100D4.
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.
Why a common workaround is wrong
This should not be diagnosed as ordinary Used Space Only encryption, which remains available without EOW semantics. That nearby condition needs a different corrective action and may produce a similar user-facing message.
Confirm the returning layer
- Record OS build, API flags, provisioning sequence, target volume and current conversion state.
manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"Encrypt-On-Write is a provisioning mode, not ordinary conversion
Encrypt-On-Write changes how newly written sectors are handled during early provisioning. It depends on an operating-system implementation and API flag that older Windows releases do not expose. The volume can still use conventional BitLocker encryption or Used Space Only conversion without this mode.
Remove the EOW request from the provisioning sequence or service the image to a supported release. Repartitioning the disk does not add the missing operating-system capability.
State checks specific to FVE_E_EOW_NOT_SUPPORTED_IN_VERSION
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call volume state and geometry state. Encrypt-On-Write mode was requested on a Windows version that does not implement that BitLocker conversion mode. |
| At failure | Preserve OS build, API flags, provisioning sequence, target volume and current conversion state. |
| After correction | Enable BitLocker without EOW or upgrade through a supported Windows servicing path if the mode is required. |
References
Looking for a different code? Search another status or error code.