HRESULT 0x803100C1: meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator.

Previous	Next
FVE_E_PROTECTOR_CHANGE_MAX_PASSPHRASE_CHANGE_ATTEMPTS_REACHED	FVE_E_LIVEID_ACCOUNT_SUSPENDED

FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED

Why this is not a generic disk error

The practical meaning of FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED is that the standard-user security context is not permitted to change the BitLocker password protector. The HRESULT is 0x803100C1.

Three decisions before remediation

Is the FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED target correct?: For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, use the volume or protector GUID and confirm its role; do not rely only on a drive letter or friendly name.
Is the FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED request allowed?: For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, resolve effective policy, Windows edition, caller token and management source for the key-protector lifecycle operation.
Is the FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED state stable?: For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, record conversion, protection, lock and reboot status before modifying anything.

For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, note: A BitLocker key protector wraps access to the volume master key. When diagnosing FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, remember: TPM, TPM+PIN, startup key, recovery password, password, certificate and Network Unlock protectors have different volume and policy rules; changing one is not the same as decrypting the volume. For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, note: Never capture PINs, passwords or recovery passwords in logs. When diagnosing FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, remember: IDs, types, policy, call result and attempt counters are sufficient for most diagnosis.

Why a common workaround is wrong

This should not be diagnosed as a password-format failure; authorization is evaluated independently of the proposed new secret. For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, that nearby condition needs a different corrective action and may produce a similar user-facing message.

Confirm the returning layer

For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, record caller token, elevation state, effective policy, target drive type and change versus reset API. For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, 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_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED 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 -protectors -get C:\npowershell -NoProfile -Command "Get-BitLockerVolume C: | Format-List KeyProtector,ProtectionStatus,VolumeStatus"

Correct the configuration deliberately

For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, perform the documented elevated reset/change operation or revise managed policy if delegated changes are intended.
After correcting the FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED condition is still active.
Before a FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED 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.

Treat FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED as a state label rather than a complete recovery plan. Confirm a successful retry with an updated BitLocker state query and a verified recovery path.

State checks specific to FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED

Checkpoint	How to interpret it for FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED
Before the call	Record the target identity and the pre-call key-protector lifecycle state. For FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED, the decisive boundary is that the standard-user security context is not permitted to change the BitLocker password protector.
At failure	Preserve caller token, elevation state, effective policy, target drive type and change versus reset API. This proves whether FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED came from BitLocker itself or from a wrapper translating another result.
After correction	Perform the documented elevated reset/change operation or revise managed policy if delegated changes are intended. The FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

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

References

Reference set for FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED:

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