Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | BitLocker drive encryption policy failed — Intune encryption enforcement blocked because prerequisites not met or TPM not ready | Windows Event Viewer logs | -> |
| Error code | 0x87D1338A | Intune device health overview | -> |
| Affected OS build range | Windows 11 22H2 (OS Build: 22621.194) | Microsoft documentation | -> |
| Relevant registry key or OMA-URI | OMA-URI: ./Device/Vendor/MSFT/Policy/Config/BitLocker | Intune admin center | -> |
| Service/endpoint URL | https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Devices | Azure Portal | -> |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Windows-BitLocker-Driver-Performance%4Operational.evtxC:\Windows\System32\winevt\Logs\Security.evtx
What This Error Actually Means
The error code0x87D1338A indicates a failure in enforcing BitLocker drive encryption policies through Microsoft Intune. Specifically, this error occurs when the system detects that either the prerequisites for BitLocker are not met or the TPM (Trusted Platform Module) is not ready. This issue is raised by the BitLocker driver during its initialization process, which is critical for enforcing device encryption as part of your organization's security policies.
BitLocker encryption relies heavily on the TPM to securely store cryptographic keys and ensure that data remains encrypted even if the device is lost or stolen. If the TPM is not properly initialized, configured, or recognized by the system, BitLocker cannot enforce its policies, leading to this error. Additionally, missing prerequisites such as the .NET Framework 3.5 or specific Windows features can also trigger this issue.
Affected Versions and Scope
This error is observed in devices running **Windows 11 22H2** with OS Build22621.194. It does not affect earlier versions of Windows 11 or other operating systems such as Windows 10. The scope of this issue is limited to devices enrolled in Microsoft Intune for device management and encryption enforcement. Tenants using Azure AD with Intune are particularly affected if they have deployed BitLocker policies across their fleet.
Where To Look First: Logs and Event IDs
To diagnose this issue, examine the following log files: 1. **BitLocker Driver Performance Log**:C:\Windows\System32\winevt\Logs\Microsoft-Windows-BitLocker-Driver-Performance%4Operational.evtx
Look for Event ID 204, which indicates that BitLocker encryption enforcement was blocked due to prerequisites not being met or the TPM not being ready.
2. **Security Log**:
C:\Windows\System32\winevt\Logs\Security.evtx
Search for Event ID 205, which provides additional details about BitLocker initialization failures, including specific reasons such as missing prerequisites or TPM issues.
Use the following PowerShell command to filter these events:
Get-WinEvent -LogName "Microsoft-Windows-BitLocker-Driver-Performance/Operational" | Where-Object { $_.Id -eq 204 }
Root Causes
The error can stem from several underlying issues:1. TPM Not Ready or Initialized
If the TPM is not properly initialized, BitLocker cannot store encryption keys securely. This often happens during device provisioning or after a system restore.2. Missing Prerequisites
BitLocker requires specific components to function correctly. Common missing prerequisites include: - .NET Framework 3.5 - Windows Management Instrumentation (WMI) services3. Incorrect BitLocker Policy Configuration
Misconfigured policies in Intune can prevent BitLocker from enforcing encryption. This includes issues with OMA-URI paths or policy scopes.Fix Procedure
Follow these steps to resolve the issue:- Check TPM Status:
Open PowerShell and run:
Get-Tpm -ErrorAction Stop | Select-Object TpmPresent, IsReady, Manufacturer, ModelEnsure thatTpmPresentisTrueandIsReadyisTrue. If not, initialize the TPM using:Initialize-Tpm -AllowClear -Force - Install Missing Prerequisites:
Enable .NET Framework 3.5 via PowerShell:
Add-WindowsCapability -Online -Name Rsat.NET-Framework-35-Winows-Server-Features~~~~0.0.1.0 - Verify BitLocker Policy Configuration:
Navigate to the Intune admin center and check:
Devices > Policies > Device policiesEnsure the OMA-URI./Device/Vendor/MSFT/Policy/Config/BitLockeris correctly configured. - Reset Device Enrollment:
If issues persist, reset device enrollment using:
dsregcmd /statusFollow up with:dsregcmd /unregister -allThen re-enroll the device.
Warning: Resetting enrollment can affect other Intune policies. Ensure a backup is available before proceeding.
Error Code Variants
| Error Code | Description |
|---|---|
0x87D1338A | BitLocker enforcement blocked due to prerequisites or TPM issues. |
0x87D1338B | BitLocker failed to initialize due to missing .NET Framework. |
0x87D1338C | TPM initialization failed during BitLocker setup. |
Verification
After applying fixes, verify success by: - Checking the Intune device health overview for a green status. - Reviewing the BitLocker logs for Event ID206, indicating successful encryption enforcement.
Use this PowerShell command to confirm BitLocker is active:
Get-BitLockerVolume | Select-Object VolumeType, ProtectionStatus
Prevention
To avoid recurrence: 1. Implement a baseline policy in Intune to ensure .NET Framework 3.5 and required Windows features are always installed. 2. Regularly audit TPM readiness across your fleet using:Get-Tpm -ErrorAction Stop | Select-Object TpmPresent, IsReady
3. Monitor device health in the Azure Portal at:
https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Devices
Tip: Use
Get-WinEvent -LogName "Security" | Where-Object { $_.Id -eq 205 } to quickly identify BitLocker initialization issues.