HRESULT 0x8031006D (FVE_E_OS_VOLUME_PASSPHRASE_NOT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

A password cannot be added to the operating system drive.

Previous	Next
FVE_E_FIPS_PREVENTS_PASSPHRASE	FVE_E_INVALID_BITLOCKER_OID

FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED

Read this as a state-machine result

FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case a password protector was requested for the operating-system volume, where that protector type is not supported for preboot authentication.

For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, note: A BitLocker key protector wraps access to the volume master key. When diagnosing FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, 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.

What the code does not prove

The closest misleading interpretation is a fixed or removable data volume password policy; those volumes have different unlock semantics. For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, verify the returning method and state transition before assigning the incident to disk corruption, TPM failure or bad credentials.

Inspect the target, not just the message

For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, record volume type, requested protector type, current TPM/startup protectors, preboot input capability and effective startup-authentication policy. For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, 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_OS_VOLUME_PASSPHRASE_NOT_ALLOWED failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, note: A change operation authenticates the old protector and creates replacement wrapping data. When diagnosing FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, remember: An administrator reset follows a different trust path, which is why change and reset errors must not be merged.

A low-risk recovery path

For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, choose a supported OS-volume protector such as TPM, TPM+PIN, startup key or an approved combination and preserve recovery material.
After correcting the FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED condition is still active.
Before a FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED 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.

manage-bde -protectors -get C:\npowershell -NoProfile -Command "Get-BitLockerVolume C: | Format-List KeyProtector,ProtectionStatus,VolumeStatus"

Result interpretation for FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED

After correction, compare the new conversion, protection and lock state with the original snapshot. A different HRESULT after FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED is useful because it means the request crossed this boundary and reached the next prerequisite.

State checks specific to FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED

Checkpoint	How to interpret it for FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED
Before the call	Record the target identity and the pre-call key-protector lifecycle state. For FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED, the decisive boundary is that a password protector was requested for the operating-system volume, where that protector type is not supported for preboot authentication.
At failure	Preserve volume type, requested protector type, current TPM/startup protectors, preboot input capability and effective startup-authentication policy. This proves whether FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED came from BitLocker itself or from a wrapper translating another result.
After correction	Choose a supported OS-volume protector such as TPM, TPM+PIN, startup key or an approved combination and preserve recovery material. The FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

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

References

Reference set for FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED:

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