What does HRESULT 0x80310040 (FVE_E_NOT_ALLOWED_IN_SAFE_MODE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes.

Previous	Next
FVE_E_TPM_DISABLED	FVE_E_TPM_INVALID_PCR

FVE_E_NOT_ALLOWED_IN_SAFE_MODE

Why this is not a generic disk error

The practical meaning of FVE_E_NOT_ALLOWED_IN_SAFE_MODE is that BitLocker management was requested while Windows is in Safe Mode, where only recovery-oriented access is supported. The HRESULT is 0x80310040.

Three decisions before remediation

Is the FVE_E_NOT_ALLOWED_IN_SAFE_MODE target correct?: For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, 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_NOT_ALLOWED_IN_SAFE_MODE request allowed?: For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, resolve effective policy, Windows edition, caller token and management source for the volume state and geometry operation.
Is the FVE_E_NOT_ALLOWED_IN_SAFE_MODE state stable?: For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, record conversion, protection, lock and reboot status before modifying anything.

For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing FVE_E_NOT_ALLOWED_IN_SAFE_MODE, remember: Two volumes can both appear “encrypted” in a UI while being in very different states for a management API. For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, note: Conversion status and protection status answer different questions: sectors can be encrypted while protectors are suspended, and a fully decrypted volume can still contain stale management context in a caller.

Why a common workaround is wrong

This should not be diagnosed as a service startup failure or an unsupported Windows edition; the operating environment is the controlling condition. For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, that nearby condition needs a different corrective action and may produce a similar user-facing message.

Confirm the returning layer

For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, record boot mode, WinRE/Safe Mode flags, requested WMI or manage-bde operation, target volume type and current protection status. For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, 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_NOT_ALLOWED_IN_SAFE_MODE 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 *"

Correct the configuration deliberately

For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, restart into normal Windows for configuration work; use Safe Mode only to recover access and preserve evidence.
After correcting the FVE_E_NOT_ALLOWED_IN_SAFE_MODE prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_NOT_ALLOWED_IN_SAFE_MODE condition is still active.
Before a FVE_E_NOT_ALLOWED_IN_SAFE_MODE 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_NOT_ALLOWED_IN_SAFE_MODE 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.

Safe Mode narrows BitLocker to recovery tasks

Safe Mode intentionally starts a reduced driver and service set. BitLocker can preserve access needed for recovery, but configuration changes such as adding protectors, changing policy-dependent state or beginning conversion are deferred to a normal boot. The volume itself may be healthy and fully readable.

Use the Safe Mode session to copy data or collect evidence, then restart normally for management changes. Reinstalling BitLocker components is not justified by this environment-specific restriction.

State checks specific to FVE_E_NOT_ALLOWED_IN_SAFE_MODE

Checkpoint	How to interpret it for FVE_E_NOT_ALLOWED_IN_SAFE_MODE
Before the call	Record the target identity and the pre-call volume state and geometry state. For FVE_E_NOT_ALLOWED_IN_SAFE_MODE, the decisive boundary is that BitLocker management was requested while Windows is in Safe Mode, where only recovery-oriented access is supported.
At failure	Preserve boot mode, WinRE/Safe Mode flags, requested WMI or manage-bde operation, target volume type and current protection status. This proves whether FVE_E_NOT_ALLOWED_IN_SAFE_MODE came from BitLocker itself or from a wrapper translating another result.
After correction	Restart into normal Windows for configuration work; use Safe Mode only to recover access and preserve evidence. The FVE_E_NOT_ALLOWED_IN_SAFE_MODE request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_NOT_ALLOWED_IN_SAFE_MODE; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

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

References

Reference set for FVE_E_NOT_ALLOWED_IN_SAFE_MODE:

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