Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error code | 0x8031004A | BitLocker Setup Wizard / manage-bde | FVE_E_TPM_DISABLED |
| Affected OS Build Range | Windows 10 (1709+) / Windows 11 | Microsoft Docs | Requires TPM 2.0 for Win 11 |
| Relevant Registry Key | HKLM\SYSTEM\CurrentControlSet\Services\TPM\WMI | Registry Editor | Monitors TPM status |
| Service Endpoint | Trusted Platform Module (TPM) Base Services | services.msc | Must be Running |
| Log Line Signature | Event ID 770 or 773 | Microsoft-Windows-BitLocker-API/Management | Indicates TPM communication failure |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Windows-BitLocker-API%4Management.evtxC:\Windows\System32\winevt\Logs\System.evtx
What This Error Actually Means
The error code 0x8031004A, technically defined as FVE_E_TPM_DISABLED, is a critical failure state within the BitLocker Drive Encryption (BDE) subsystem. It indicates that while the operating system has detected the presence of a Trusted Platform Module (TPM) chip on the motherboard, the module is currently in a disabled, uninitialized, or non-responsive state. This prevents the BitLocker driver from establishing a secure channel to store the Volume Master Key (VMK) protector within the TPM's Non-Volatile Memory (NVRAM). Essentially, the hardware exists, but the software stack cannot interact with it due to firmware-level restrictions or initialization failures.
This error is raised by the FVEAPI.DLL component when an administrator attempts to enable encryption via the GUI wizard or command line. It signifies that the prerequisite for hardware-backed key storage—specifically, a ready and activated TPM 2.0 (on Windows 11) or TPM 1.2 (on Windows 10)—is not met. The system refuses to proceed because it cannot guarantee the integrity of the boot chain measurements without an active TPM to store the Platform Configuration Registers (PCRs). If ignored, BitLocker will fall back to software-only encryption if explicitly forced, but this is rarely the desired configuration in enterprise environments due to performance overhead and reduced security posture.
Affected Versions and Scope
This issue predominantly affects Windows 10 builds starting from version 1709 (Fall Creators Update) and all versions of Windows 11. These builds enforce stricter TPM requirements, particularly Windows 11, which mandates TPM 2.0 for installation and BitLocker functionality. The scope includes devices managed via Microsoft Intune, Configuration Manager (SCCM), or local group policies where automatic BitLocker enablement is configured. It frequently occurs in hybrid Azure AD joined environments where device compliance policies require BitLocker encryption.
The error does not typically affect Windows 7 or early Windows 10 builds that allow software-only FVE without TPM, nor does it impact devices using third-party full-disk encryption solutions like VeraCrypt or McAfee Endpoint Encryption. It is also distinct from errors related to network connectivity issues during key escrow (e.g., AD FS or Azure Key Vault failures). The scope is strictly limited to the local hardware-software handshake between the Windows Kernel, the TPM driver (tpm.sys), and the UEFI firmware settings.
Where To Look First: Logs and Event IDs
To diagnose 0x8031004A, you must inspect specific event logs that record TPM initialization failures. The primary log file is located at C:\Windows\System32\winevt\Logs\Microsoft-Windows-BitLocker-API%4Management.evtx. Within this log, look for Event IDs 770 and 773. Event ID 770 typically indicates that the TPM is not ready or has been disabled by the BIOS. Event ID 773 often accompanies this, detailing the specific failure reason during the BitLocker initialization attempt.
Additionally, check the System log at C:\Windows\System32\winevt\Logs\System.evtx. Filter for sources related to TPM-WMI or Microsoft-Windows-TPM-ReadyRole. A common signature is a warning stating that the TPM device is present but not enabled. You can also query the registry key HKLM\SYSTEM\CurrentControlSet\Services\TPM\WMI to verify if the WMI provider for TPM is registered and active. If this key is missing or corrupted, it may indicate a deeper driver issue rather than just a BIOS setting.
Root Causes
UEFI/BIOS Firmware Configuration
The most common cause is that the TPM module is disabled in the UEFI firmware. Manufacturers often label this as "TPM Device," "Security Chip," "PTT" (Intel), or "fTPM" (AMD). If set to "Disabled," "Hidden," or "Standby," the OS cannot access it. This often happens after a BIOS update resets settings to defaults.
TPM Initialization Failure
The TPM may be enabled in firmware but not initialized by the OS. This occurs if the Endorsement Key (EK) or Storage Root Key (SRK) is missing or corrupted. The TPM requires a one-time initialization process to generate these keys. If this process was interrupted or failed, the TPM remains in a "Not Ready" state.
Incompatible TPM Version
On Windows 11, a TPM 1.2 chip will trigger this error because the OS requires TPM 2.0. While Windows 10 supports TPM 1.2, certain BitLocker features (like hardware-based key protection) may be limited or behave unexpectedly if the firmware version is outdated and lacks proper support for modern PCR measurements.
Secure Boot Interference
If Secure Boot is disabled, some UEFI implementations block TPM access as a security precaution. BitLocker relies on Secure Boot to ensure the boot environment hasn't been tampered with. Disabling Secure Boot can inadvertently disable TPM functionality in some OEM implementations.
Fix Procedure
- Verify TPM Status via PowerShell: Run
Get-Tpmto check the current state. Look forTpmPresent: True,TpmReady: False, andTpmActivated: False. This confirms the hardware is seen but not usable. - Check UEFI Settings: Restart the device and enter UEFI setup (usually F2, Del, or F10). Navigate to the Security tab. Ensure TPM/PTT/fTPM is set to Enabled and Active. If you see an option for "Clear TPM," do not select it unless you have a recovery key backup, as this will wipe existing keys.
- Initialize TPM via GUI: If the TPM is enabled but not ready, open
tpm.msc(TPM Management Console). Click "Prepare the TPM" in the right-hand pane. Follow the wizard to initialize the module. This generates the necessary keys. - Verify Service Status: Ensure the Trusted Platform Module Base Services is running. Use
Get-Service -Name "TPMBaseServices". If it is stopped, start it withStart-Service -Name "TPMBaseServices". - Re-enable BitLocker: Once the TPM is ready, run
manage-bde -on C: -UsedSpaceOnlyto start encryption. Monitor progress withmanage-bde -status.
Clear-Tpm) will delete all stored keys, including BitLocker recovery keys if they were stored in the TPM. Ensure you have exported the recovery key to Azure AD or Active Directory before clearing the TPM, or you may lose access to encrypted data permanently.
Error Code Variants
| Error Code | Name | Description | Distinguishing Factor |
|---|---|---|---|
0x8031004A |
FVE_E_TPM_DISABLED | TPM is disabled or not owned. | Hardware present but firmware/OS block access. |
0x8031004B |
FVE_E_TPM_NOT_FOUND | No TPM detected. | Hardware missing or completely disconnected. |
0x80310052 |
FVE_E_TPM_INVALID_PCR | PCR measurement mismatch. | TPM is active, but boot configuration changed (e.g., driver update). |
0x80310054 |
FVE_E_TPM_COMMUNICATION_FAILURE | Driver communication error. | OS can see TPM but cannot send commands (driver crash). |
Verification
To prove the fix worked, run Get-Tpm again. You should now see TpmReady: True and TpmActivated: True. Additionally, check the BitLocker status with manage-bde -status. The output should show "Protection On" and list the TPM as a protector. In Intune, navigate to Intune admin center > Devices > Monitor > Device compliance and verify that the device reports as compliant for the BitLocker policy. You can also check the event log again; Event ID 770 should no longer appear after a successful initialization.
dsregcmd /status to verify device registration status. If the device is not properly joined to Entra ID, BitLocker key escrow may fail even if TPM is working. This command provides a quick overview of hybrid join and Azure AD join states.
Prevention
To prevent recurrence, enforce UEFI settings via Microsoft Endpoint Manager. Create a Configuration Profile in Intune: Intune admin center > Devices > Configuration profiles > Create profile > Templates > Custom OMA-URI. Use the following OMA-URI to ensure TPM is enabled: ./Device/Vendor/MSFT/TPM/Enable with a value of 1. Additionally, deploy a baseline security policy that includes BitLocker encryption requirements. This ensures that any device failing to meet TPM criteria is flagged as non-compliant before encryption attempts are made. Regularly update BIOS firmware through Intune Windows Update for Business or SCCM to avoid settings resets.