What does HRESULT 0x80310058 (FVE_E_PUBKEY_NOT_ALLOWED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Public key based protectors are not allowed on this drive.

Previous	Next
FVE_E_TRANSIENT_STATE	FVE_E_VOLUME_HANDLE_OPEN

FVE_E_PUBKEY_NOT_ALLOWED

The failed prerequisite

FVE_E_PUBKEY_NOT_ALLOWED / 0x80310058 marks a rejected BitLocker transition: effective policy or volume type disallows a public-key certificate protector for this drive.

For FVE_E_PUBKEY_NOT_ALLOWED, note: Policy troubleshooting must use the effective result, not a screenshot of one editor. When diagnosing FVE_E_PUBKEY_NOT_ALLOWED, remember: Domain GPO, local policy, provisioning packages and MDM can all populate BitLocker settings, and an existing protector can predate the current policy.

Diagnostic map

Layer	policy and authorization
Proof to collect	volume type, effective certificate-protector policy, certificate EKU, provider, private-key availability and requested protector method
Different condition	an invalid certificate or missing private key, which are checked only after the protector type is permitted
First safe change	use an allowed protector or change the managed policy after confirming recovery and compatibility requirements

For FVE_E_PUBKEY_NOT_ALLOWED, note: BitLocker evaluates the target volume together with effective Group Policy or MDM policy, Windows edition, caller authorization and the requested protector or management method. When diagnosing FVE_E_PUBKEY_NOT_ALLOWED, remember: A policy HRESULT therefore describes a rejected configuration decision, not evidence that encrypted sectors are damaged.

A focused verification sequence

For FVE_E_PUBKEY_NOT_ALLOWED, record volume type, effective certificate-protector policy, certificate EKU, provider, private-key availability and requested protector method. For FVE_E_PUBKEY_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_PUBKEY_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_PUBKEY_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.

Recommended operational response

For FVE_E_PUBKEY_NOT_ALLOWED, use an allowed protector or change the managed policy after confirming recovery and compatibility requirements.
After correcting the FVE_E_PUBKEY_NOT_ALLOWED prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_PUBKEY_NOT_ALLOWED condition is still active.
Before a FVE_E_PUBKEY_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 -status
gpresult /h bitlocker-policy.html

Interpretation checkpoint

FVE_E_PUBKEY_NOT_ALLOWED 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_PUBKEY_NOT_ALLOWED

Checkpoint	How to interpret it for FVE_E_PUBKEY_NOT_ALLOWED
Before the call	Record the target identity and the pre-call policy and authorization state. For FVE_E_PUBKEY_NOT_ALLOWED, the decisive boundary is that effective policy or volume type disallows a public-key certificate protector for this drive.
At failure	Preserve volume type, effective certificate-protector policy, certificate EKU, provider, private-key availability and requested protector method. This proves whether FVE_E_PUBKEY_NOT_ALLOWED came from BitLocker itself or from a wrapper translating another result.
After correction	Use an allowed protector or change the managed policy after confirming recovery and compatibility requirements. The FVE_E_PUBKEY_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_PUBKEY_NOT_ALLOWED; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

For FVE_E_PUBKEY_NOT_ALLOWED, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_PUBKEY_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_PUBKEY_NOT_ALLOWED 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_PUBKEY_NOT_ALLOWED:

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