| Previous | Next |
| STATUS_FVE_AUTH_INVALID_CONFIG | STATUS_FVE_DRY_RUN_FAILED |
STATUS_FVE_DEBUGGER_ENABLED
This is a boot-configuration integrity condition, not a normal disk-encryption failure. BitLocker is refusing the expected protected startup because boot debugging changes the validated environment.
Confirm whether debugging was intentionally enabled for development or troubleshooting, record the current BCD entries, and return the protected machine to its approved boot policy before re-enabling normal protection. Do not remove unrelated boot entries blindly.
This differs from STATUS_FVE_AUTH_INVALID_CONFIG, which is a broader unsupported or changed BCD result. Here the configuration problem is specifically boot debugging.
BitLocker preboot recovery guidance | BitLocker planning guide | Microsoft NTSTATUS reference
Looking for a different code? Search another status or error code.