HRESULT 0x803100A6 (FVE_E_WIPE_NOT_ALLOWED_ON_TP

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

BitLocker Drive Encryption does not support wiping free space on thin provisioned storage.

Previous	Next
FVE_E_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE	FVE_E_KEY_LENGTH_NOT_SUPPORTED_BY_EDRIVE

FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE

What BitLocker has already established

At HRESULT 0x803100A6, BitLocker has determined that wiping free space is blocked on thin-provisioned storage because it would allocate otherwise unallocated extents. The FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE code does not by itself say that the volume master key is lost or that user data is corrupt.

Operational boundary: cluster or thin-storage coordination.

For FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, note: Cluster Shared Volumes and thin-provisioned storage add ownership and allocation semantics that a standalone disk does not have. When diagnosing FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, remember: BitLocker operations must respect the CSV coordinator and must not force thin backing storage to allocate every virtual extent. For FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, note: Thin provisioning reports virtual size separately from allocated backing space. When diagnosing FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, remember: Operations that write every free extent can consume the entire pool without adding user data.

Data to preserve before changing state

For FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, record thin-provisioning status, storage pool free capacity, volume allocation, requested manage-bde wipe command and conversion state. For FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, 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_WIPE_NOT_ALLOWED_ON_TP_STORAGE failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

Related state to rule out

Do not merge this incident with a wipe that is not currently running; this code rejects starting the operation based on storage semantics. If both appear with FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE in one trace, preserve ordering because the first HRESULT normally identifies the prerequisite that caused later cleanup or fallback messages.

How to retest without losing evidence

Skip free-space wipe on the thin volume and use lifecycle controls appropriate to the backing storage when decommissioning.

After correcting the FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE condition is still active.
Before a FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE 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.

Get-ClusterSharedVolume | Format-List *
manage-bde -status

For FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, diagnosis should be driven by the target object, effective policy and captured state snapshot rather than by a generic remediation applied to every BitLocker error.

State checks specific to FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE

Checkpoint	How to interpret it for FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE
Before the call	Record the target identity and the pre-call cluster or thin-storage coordination state. For FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, the decisive boundary is that wiping free space is blocked on thin-provisioned storage because it would allocate otherwise unallocated extents.
At failure	Preserve thin-provisioning status, storage pool free capacity, volume allocation, requested manage-bde wipe command and conversion state. This proves whether FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE came from BitLocker itself or from a wrapper translating another result.
After correction	Skip free-space wipe on the thin volume and use lifecycle controls appropriate to the backing storage when decommissioning. The FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

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

Microsoft references

Reference set for FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE:

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