What does HRESULT 0x8031003B (FVE_E_NO_PROTECTORS_TO_TEST) mean?

 
Previous Next
FVE_E_INVALID_PROTECTOR_TYPE FVE_E_KEYFILE_NOT_FOUND

FVE_E_NO_PROTECTORS_TO_TEST

The pre-encryption test needs an unlock path

BitLocker can perform a restart-based hardware test before committing an operating-system volume to encryption. The test verifies that the configured TPM, PIN, startup-key media, and boot environment can release the key during early startup. FVE_E_NO_PROTECTORS_TO_TEST means there is no protector configuration for that test to exercise.

This status should not be bypassed by assuming that encryption itself will create a usable recovery path. A volume can be prepared or partially provisioned while protection remains incomplete. The meaningful distinction is between encryption state and protection state: encrypted sectors are not enough if no secure protector is enforced.

Diagnostic steps

  • Use manage-bde -status and -protectors -get to capture conversion, protection, and protector state separately.
  • Add the policy-approved protector and make sure recovery information is backed up before rerunning the hardware test.
  • For USB startup keys, verify that firmware can enumerate the device during preboot, not only after Windows loads.
  • Do not use -SkipHardwareTest as a generic fix when the deployment requires preboot validation.

References


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