Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Configuration profile remediation failed — policy conflict or unsupported Windows edition | Microsoft Endpoint Manager admin center logs | -> |
| OS build range | Windows 11 22H2 (Build 22621.1380) | System Information tool or About Windows settings | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsIntune\Runtime\State | Registry Editor (regedit) | -> |
| Relevant service/endpoint URL | https://endpoint.microsoft.com/ | Microsoft Endpoint Manager admin center | -> |
| Log line signature | Error Code: 0x87D1FDE8, Category: ConfigurationProfileRemediationFailed | Intune Management Agent logs | -> |
Log Files to Check
C:\ProgramData\Microsoft\IntuneManagementAgent\Logs\Application.logC:\Windows\System32\winevt\Logs\Microsoft-IntuneClient-Operational.evtx
What This Error Actually Means
The error code0x87D1FDE8 is raised by the **Intune Management Agent (IMA)** during configuration profile remediation. It indicates a failure to apply a policy due to either a **conflict between policies** (e.g., duplicate or mutually exclusive settings) or the **Windows edition being incompatible** with the configuration profile. This error is logged when the IMA detects that the target device’s operating system edition (e.g., Windows 11 Home) lacks the required features to enforce a policy, or when two policies attempt to configure the same setting with conflicting values. The error is categorized under ConfigurationProfileRemediationFailed, which is tracked in the Intune Management Agent logs and the Microsoft Endpoint Manager admin center.
Affected Versions and Scope
This error primarily affects **Windows 11 22H2 (Build 22621.1380)** devices enrolled in Intune. It is most commonly observed on devices running **Windows 11 Home edition**, as many Intune configuration profiles require Pro or Enterprise editions. Devices running **Windows 11 Pro, Enterprise, or Education editions** are generally unaffected unless misconfigured policies are applied. The issue does not occur on Windows 10 21H2 or later builds unless the same edition incompatibility exists. Tenants using **baseline configuration profiles** or **custom OMA-URI policies** targeting unsupported editions are at higher risk. Devices managed via co-management or hybrid Azure AD join are not immune but require additional validation of group policy and Intune policy alignment.Where To Look First: Logs and Event IDs
The primary log file to inspect isC:\ProgramData\Microsoft\IntuneManagementAgent\Logs\Application.log. Use Get-WinEvent -LogName "Microsoft-IntuneClient-Operational" or open C:\Windows\System32\winevt\Logs\Microsoft-IntuneClient-Operational.evtx in Event Viewer. Search for the exact log line:
Error Code: 0x87D1FDE8, Category: ConfigurationProfileRemediationFailed.
Event IDs 10016 (policy conflict) and 10017 (unsupported edition) in the Microsoft-IntuneClient-Operational log are directly associated with this error. Use PowerShell to filter logs:
Get-WinEvent -LogName "Microsoft-IntuneClient-Operational" | Where-Object { $_.Message -match "0x87D1FDE8" }.
Root Causes
1. Policy Conflict Between Intune and Local Group Policy
This occurs when a local Group Policy Object (GPO) or another Intune policy enforces a conflicting setting. For example, a firewall rule configured via GPO may clash with an Intune firewall profile. To identify, runGet-CimInstance -ClassName Win32_GroupPolicy and cross-reference settings with Intune policies.
2. Unsupported Windows Edition
Configuration profiles requiring features like BitLocker, device enrollment, or advanced security settings fail on Windows 11 Home. Check the edition with(Get-WmiObject -Class Win32_OperatingSystem).Caption. If "Home" is present, the error is guaranteed for profiles requiring Pro/Enterprise features.
3. Corrupted Intune Agent State
The registry keyHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsIntune\Runtime\State stores the agent’s operational state. If the LastRemediationStatus value contains 0x87D1FDE8, the agent failed to apply a policy. This can be resolved by resetting the registry value or reinstalling the Intune agent.
Fix Procedure
- Resolve Policy Conflicts:
Use
Get-IntuneDevice -Filter "id eq 'deviceID'"to identify the device. In the Intune admin center, navigate to Devices > All devices, select the device, and review assigned policies. Remove or adjust conflicting policies via Policies > Configuration profiles. - Upgrade Windows Edition:
For unsupported editions, run
Get-WindowsEdition -Onlineand useSet-WindowsEdition -Online -Edition Enterprise -LicenseKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXXto upgrade. Reapply the configuration profile. - Reset Intune Agent State:
Open Registry Editor and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsIntune\Runtime\State. SetLastRemediationStatusto0. Restart theIntelAMTservice withRestart-Service -Name "IntelAMT". - Reinstall Intune Agent:
Run
msiexec /x MicrosoftIntuneManagementExtension.msito uninstall, then reinstall usingMicrosoftIntuneManagementExtensionSetup.exefrom theC:\Program Files\Microsoft Intune Management Extensiondirectory.
Modifying the registry or reinstalling the Intune agent may disrupt device enrollment. Ensure a backup of the registry is taken before proceeding.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x87D1FDE8 | Policy conflict or unsupported edition | Logged when policies clash or OS edition lacks required features |
0x87D1FDE9 | Profile deployment timeout | Occurs when remediation exceeds 30-minute threshold |
0x87D1FDEA | OMA-URI syntax error | Invalid OMA-URI string in configuration profile |
Verification
After applying fixes, runGet-WinEvent -LogName "Microsoft-IntuneClient-Operational" | Where-Object { $_.Message -match "Remediation succeeded" } to confirm resolution. In the Intune admin center, navigate to Devices > All devices and verify the device’s compliance status is Compliant. The registry key LastRemediationStatus should return 0 if the agent state was reset.
Prevention
To prevent recurrence: 1. **Use Edition-Aware Policies:** In the Intune admin center, create device groups filtered by OS edition (e.g.,deviceOperatingSystem eq 'Windows 11 Pro') and assign edition-specific policies.
2. **Enforce Baselines:** Apply the Windows 11 Pro baseline via Devices > Windows > Baselines to ensure compatibility.
3. **Audit Policy Dependencies:** Use Get-IntunePolicy -Filter "devicePlatform eq 'windows10'" to audit policies and resolve overlaps.
Use
dsregcmd /status to quickly verify enrollment status and OS edition compatibility without opening logs.