HRESULT 0x803100B9 (FVE_E_WIPE_CANCEL_NOT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Wipe of free space is not currently taking place.

Previous	Next
FVE_E_POLICY_REQUIRES_RECOVERY_PASSWORD_ON_TOUCH_DEVICE	FVE_E_SECUREBOOT_DISABLED

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. Note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing this result, remember: Two volumes can both appear “encrypted” in a UI while being in very different states for a management API.

Note: Use the volume GUID and current storage topology as the stable identity. When diagnosing this result, 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. 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

record conversion/wipe status, command history, volume identity and whether another management process already completed or canceled the task. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
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 result 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

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

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 the result

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call volume state and geometry state. The decisive boundary is that the caller requested cancellation when no BitLocker free-space wipe operation is active.
At failure	Preserve conversion/wipe status, command history, volume identity and whether another management process already completed or canceled the task. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Refresh status and treat the operation as idempotent; do not start a new wipe merely to make cancellation succeed. The request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for it; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

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

References

Reference set for it:

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