HRESULT 0x803100C2 (FVE_E_LIVEID_ACCOUNT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

BitLocker cannot save the recovery password because the specified Microsoft account is Suspended.

Previous	Next
FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED	FVE_E_LIVEID_ACCOUNT_BLOCKED

FVE_E_LIVEID_ACCOUNT_SUSPENDED

The failed prerequisite

FVE_E_LIVEID_ACCOUNT_SUSPENDED / 0x803100C2 marks a rejected BitLocker transition: recovery-password escrow to the specified Microsoft account is blocked because that account is suspended.

For FVE_E_LIVEID_ACCOUNT_SUSPENDED, note: Evaluate every fixed volume and the OS trust anchor together. When diagnosing FVE_E_LIVEID_ACCOUNT_SUSPENDED, remember: Automatic unlock and device-wide compliance can fail because a secondary volume is outside policy.

Diagnostic map

Layer	automatic Device Encryption
Proof to collect	account state, connected-account identity, escrow destination, network/service response and whether another approved escrow target exists
Different condition	a local failure to create the recovery password or a network timeout reaching account services
First safe change	restore the account or choose an enterprise-approved escrow destination before enabling protection that depends on successful backup

For FVE_E_LIVEID_ACCOUNT_SUSPENDED, note: Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. When diagnosing FVE_E_LIVEID_ACCOUNT_SUSPENDED, remember: It evaluates platform eligibility, account-backed recovery escrow, all applicable fixed volumes and protection state; failure of Auto-DE does not automatically mean manual BitLocker is unavailable.

A focused verification sequence

For FVE_E_LIVEID_ACCOUNT_SUSPENDED, record account state, connected-account identity, escrow destination, network/service response and whether another approved escrow target exists. For FVE_E_LIVEID_ACCOUNT_SUSPENDED, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_LIVEID_ACCOUNT_SUSPENDED, 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_LIVEID_ACCOUNT_SUSPENDED failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

Recommended operational response

For FVE_E_LIVEID_ACCOUNT_SUSPENDED, restore the account or choose an enterprise-approved escrow destination before enabling protection that depends on successful backup.
After correcting the FVE_E_LIVEID_ACCOUNT_SUSPENDED prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_LIVEID_ACCOUNT_SUSPENDED condition is still active.
Before a FVE_E_LIVEID_ACCOUNT_SUSPENDED 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.

msinfo32.exe
powershell -NoProfile -Command "Get-BitLockerVolume | Format-Table MountPoint,VolumeType,VolumeStatus,ProtectionStatus"

Interpretation checkpoint

FVE_E_LIVEID_ACCOUNT_SUSPENDED identifies a condition but not every owner of the surrounding state. Preserve the original caller, volume GUID and event sequence so the correction is applied at the right layer.

State checks specific to FVE_E_LIVEID_ACCOUNT_SUSPENDED

Checkpoint	How to interpret it for FVE_E_LIVEID_ACCOUNT_SUSPENDED
Before the call	Record the target identity and the pre-call automatic Device Encryption state. For FVE_E_LIVEID_ACCOUNT_SUSPENDED, the decisive boundary is that recovery-password escrow to the specified Microsoft account is blocked because that account is suspended.
At failure	Preserve account state, connected-account identity, escrow destination, network/service response and whether another approved escrow target exists. This proves whether FVE_E_LIVEID_ACCOUNT_SUSPENDED came from BitLocker itself or from a wrapper translating another result.
After correction	Restore the account or choose an enterprise-approved escrow destination before enabling protection that depends on successful backup. The FVE_E_LIVEID_ACCOUNT_SUSPENDED request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_LIVEID_ACCOUNT_SUSPENDED; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

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

Official references

Reference set for FVE_E_LIVEID_ACCOUNT_SUSPENDED:

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