What does HRESULT 0x803100B9 (FVE_E_WIPE_CANCEL_NOT_APPLICABLE) mean?

FVE_E_WIPE_CANCEL_NOT_APPLICABLE

The exact BitLocker boundary

FVE_E_WIPE_CANCEL_NOT_APPLICABLE (0x803100B9) identifies the point where the caller requested cancellation when no BitLocker free-space wipe operation is active. For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing FVE_E_WIPE_CANCEL_NOT_APPLICABLE, remember: Two volumes can both appear “encrypted” in a UI while being in very different states for a management API.

For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, note: Use the volume GUID and current storage topology as the stable identity. When diagnosing FVE_E_WIPE_CANCEL_NOT_APPLICABLE, remember: Drive letters, mount points and cluster paths are presentation details and can point to the wrong object during recovery.

Do not confuse it with a nearby failure

Keep this separate from FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE, which prevents a wipe from starting on thin storage. For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, that distinction determines whether the next check belongs to policy, protector inventory, volume geometry, firmware, account escrow or the calling application's buffer contract.

Evidence that distinguishes the condition

• For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, record conversion/wipe status, command history, volume identity and whether another management process already completed or canceled the task. For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
• For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, 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_CANCEL_NOT_APPLICABLE failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"

Safe corrective sequence

1. For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, refresh status and treat the operation as idempotent; do not start a new wipe merely to make cancellation succeed.
2. After correcting the FVE_E_WIPE_CANCEL_NOT_APPLICABLE prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_WIPE_CANCEL_NOT_APPLICABLE condition is still active.
3. Before a FVE_E_WIPE_CANCEL_NOT_APPLICABLE 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.

For FVE_E_WIPE_CANCEL_NOT_APPLICABLE, the boundary above identifies which BitLocker state must change before a retry can be meaningful; repeating the call without changing that state only adds noise.

State checks specific to FVE_E_WIPE_CANCEL_NOT_APPLICABLE

Verification after the change

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

References

Reference set for FVE_E_WIPE_CANCEL_NOT_APPLICABLE:

• Microsoft: BitLocker operations guide
• Microsoft: manage-bde status
• Microsoft: GetConversionStatus method
• Microsoft: GetLockStatus method

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