| Previous | Next |
| STATUS_FVE_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE | STATUS_FVE_NOT_ALLOWED_ON_CSV_STACK |
STATUS_FVE_WIPE_NOT_ALLOWED_ON_TP_STORAGE
Meaning and context of STATUS_FVE_WIPE_NOT_ALLOWED_ON_TP_STORAGE
This is specifically about the free-space wipe operation on thin-provisioned storage. It does not say that the volume is unlocked, unencrypted, or generally unusable; the requested post-encryption operation is not compatible with that storage model.
Check whether the intended goal is encryption of future writes, removal of old unencrypted remnants, or storage reclamation. Those are different tasks. A thin-provisioned backing store can make a free-space overwrite operation inappropriate even when Used Space Only encryption itself is supported.
Do not treat this status as an invitation to write arbitrary data across free space. Verify the volume’s provisioning model and choose a documented disposal or sanitation process that matches the storage platform and retention requirements.
manage-bde wipefreespace | BitLocker thin-provisioned storage note | NTSTATUS reference
Native status interpretation
STATUS_FVE_WIPE_NOT_ALLOWED_ON_TP_STORAGE is 0xC0210033, an NTSTATUS error value. AllStat describes it as “BitLocker Drive Encryption does not support wiping free space on thin provisioned storage.”
Looking for a different code? Search another status or error code.