| Previous | Next |
| FVE_E_POLICY_PASSPHRASE_REQUIRES_ASCII | FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE |
FVE_E_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE
Read this as a state-machine result
FVE_E_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case full-volume encryption was requested on thin-provisioned storage, where BitLocker permits only Used Space Only conversion.
Cluster Shared Volumes and thin-provisioned storage add ownership and allocation semantics that a standalone disk does not have. BitLocker operations must respect the CSV coordinator and must not force thin backing storage to allocate every virtual extent.
What the code does not prove
The closest misleading interpretation is a small or nearly full volume; the restriction prevents allocation expansion of thin backing storage. Verify the returning method and state transition before assigning the incident to disk corruption, TPM failure or bad credentials.
Inspect the target, not just the message
Cluster maintenance should preserve resource ownership, quorum assumptions and application shutdown ordering. BitLocker is only one participant in that workflow.
A low-risk recovery path
- Use Used Space Only encryption and monitor backing allocation; do not force a full sweep that defeats thin provisioning.
Get-ClusterSharedVolume | Format-List *
manage-bde -status
State checks specific to FVE_E_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call cluster or thin-storage coordination state. Full-volume encryption was requested on thin-provisioned storage, where BitLocker permits only Used Space Only conversion. |
| At failure | Preserve provisioning type, virtual disk/VHD mode, conversion method, allocated versus virtual size and storage-pool capacity. |
References
Looking for a different code? Search another status or error code.