Home › Microsoft Intune › 0x87D1041C

Microsoft Intune · 0x87D1041C · Windows 11 23H2

Intune Error 0x87D1041C: BitLocker Required for Windows 11 23H2

Root cause is missing BitLocker encryption; fix involves enabling BitLocker via Intune or manually.

Error Details

FactValueSource
Exact error stringDevice does not have required encryption policyIntune admin center - Device compliance
Affected build rangeWindows 11 23H2OS version reported in Intune
Registry key involvedHKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{F4E875FB-CD9F-11D2-BB6C-00C04FD918D0}Registry Editor
Relevant service/endpoint URLhttps://graph.microsoft.com/v1.0/deviceManagement/complianceManagementCapabilities/bitLockerMicrosoft Graph API endpoint
Log line signatureError code 0x87D1041C - Encryption is requiredIntune admin center logs

Log Files to Check

What This Error Actually Means

The error code 0x87D1041C, which translates to "Device does not have required encryption policy," is raised by the Microsoft Intune management system when a device fails to meet compliance requirements set forth in an assigned BitLocker encryption policy. Specifically, this error occurs if the device's OS drive (typically C:) lacks BitLocker encryption as mandated by the organization's security policies enforced through Intune. This ensures that sensitive data remains protected even if the physical device is lost or stolen.

Affected Versions and Scope

This issue affects devices running Windows 11 build 23H2 exclusively, where BitLocker encryption compliance is a mandatory requirement for accessing corporate resources under Conditional Access policies enforced by Intune. Devices on earlier builds of Windows 11 or other operating systems like Windows 10 may not exhibit this specific error due to differences in the way BitLocker and device management are implemented across versions.

Where To Look First: Logs and Event IDs

To diagnose the cause of the 0x87D1041C error, start by examining the following logs: - C:\Windows\System32\winevt\Logs\Microsoft-Windows-GroupPolicy%4Operational.evtx for any Group Policy-related issues that might be overriding Intune settings. - C:\ProgramData\Microsoft\IntuneManagementExtension\logs\IntuneManagementExtension.log to check the status of BitLocker and compliance checks performed by the Intune Management Extension. Event IDs 4096 (Group Policy client processing) and 1283 (BitLocker Drive Encryption) are particularly relevant. You can use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to retrieve recent events related to device management compliance checks.

Root Causes

BitLocker Not Enabled on OS Drive (C:)

This is the most common cause, especially for newly enrolled devices or those reinstalled from an image without BitLocker enabled. To confirm this issue, run manage-bde -status C: in an elevated Command Prompt and check if 'Protection Status' shows as 'Protection Off'.

TPM Chip Not Initialized or Incompatible Version

If the TPM chip is not ready for use or its version is 1.2, BitLocker cannot be automatically enabled even if it's required by Intune policies. Verify TPM status using tpm.msc, and ensure that the TPM version is at least 2.0.

Group Policy Conflicts with Intune Settings

Sometimes, local Group Policies can override BitLocker settings enforced via MDM (Intune). Use gpresult /h c:\gpresult.html to generate a report and inspect it for any conflicting policies under Computer Configuration > Windows Settings > Security Settings > BitLocker Drive Encryption.

Fix Procedure

  1. Check BitLocker Status: Open an elevated Command Prompt and run manage-bde -status C:. Additionally, use PowerShell with Get-BitLockerVolume C: | Select-Object VolumeStatus,ProtectionStatus.
  2. Verify TPM Initialization: Launch tpm.msc to ensure the TPM is 'Ready for use' and its version is 2.0.
  3. Resolve GPO Conflicts (if applicable): Use rsop.msc to detect conflicting Group Policy settings, then modify or remove them in the Group Policy Management Console (gpmc.msc).
  4. Enable BitLocker via Intune:
    In the Intune admin center, navigate to Endpoint security > Disk encryption > Create policy > Windows > BitLocker. Configure Encrypt devices to 'Require' and assign the policy to the affected device group.
  5. Alternatively, manually enable BitLocker with Enable-BitLocker -MountPoint C: -TpmProtector -UsedSpaceOnly.
  6. Synchronize Intune Policy: On the device, go to Settings > Accounts > Access work or school > select the account > Info > Sync. After syncing, check compliance status in the Intune admin center.
  7. Verify Device Group Membership: Ensure the device is a member of the correct Azure AD group by checking Entra admin center > Groups > Members.

Error Code Variants

Error Code Description Distinguishing Factors
0x87D1041C Device does not have required encryption policy Specific to BitLocker compliance failures in Windows 11 23H2.
0x87D1041D BitLocker key protection is missing or invalid This error occurs when the TPM chip fails to protect the BitLocker recovery key, often due to hardware issues.
0x87D10420 BitLocker encryption policy not met on all drives Differentiates from 0x87D1041C as it pertains to non-compliance across multiple drives, not just the OS drive.

Verification

After applying fixes, run manage-bde -status C: in an elevated Command Prompt to confirm 'Protection Status' shows as 'Protection On'. Next, initiate a compliance status sync on the device and check Intune admin center > Devices > select device > Sync. The compliance status should update to 'Compliant' within 15 minutes.

Prevention

To prevent recurrence of this issue, ensure that BitLocker encryption is enabled during initial Windows installation or deployment processes for all devices joining the organization's network. Additionally, implement a policy in Intune to automatically enable BitLocker on new devices and regularly audit Group Policy settings to avoid conflicts with MDM-enforced policies.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.