Home › Microsoft Configuration Manager › 0x87D01106

Microsoft Configuration Manager · 0x87D01106 · Windows 11 23H2

Microsoft Configuration Manager Error 0x87D01106 - Windows 11 23H2 Client Installation Failed

The error occurs due to WMI corruption or missing CCMSetup prerequisites. Fix by repairing WMI, reinstalling .NET Framework, and ensuring all prerequisites are met.

Error Details

FactValueSourceNote
Exact error stringClient installation failed — WMI corruption or CCMSetup prerequisite not met on target deviceccmsetup.log-> Indicates failure during client setup
Affected OS build rangeWindows 11 23H2OS version check-> Confirmed on this specific build
Registry key involvedHKLM\Software\Microsoft\CCMSetupRegistry inspection-> Contains setup configuration details
Relevant service/endpoint URLhttps://configmgr.microsoft.comConfiguration Manager console-> Ensure connectivity to this endpoint
Log line signature[Setup] Error: 0x87D01106ccmsetup.log-> Identifies the specific error code in logs

Log Files to Check

What This Error Actually Means

The error code 0x87D01106 is raised during Microsoft Configuration Manager (ConfigMgr) client installation when the CCMSetup process detects either **WMI (Windows Management Instrumentation) corruption** or **unmet prerequisites** required for client deployment. The hexadecimal value 0x87D01106 translates to -2139863190 in decimal and is specifically tied to the ConfigMgr client setup component (ccmsetup.exe). This error typically occurs during the initialization phase of client installation when CCMSetup validates system readiness. The root component responsible for this error is the **Configuration Manager Client Setup Engine**, which relies on WMI for system inventory and policy enforcement. If WMI repositories are corrupted or prerequisite components (e.g., .NET Framework, Windows Management Framework, or system services) are missing, the setup fails with this code.

Affected Versions and Scope

This error is explicitly observed on **Windows 11 23H2 (OS build 22000.218 or later)**. It is most commonly reported in environments where ConfigMgr clients are deployed via **Intune hybrid co-management** or **standalone ConfigMgr site servers**. The issue is **not present in Windows 10 22H2 or earlier Windows 11 builds (e.g., 22H2)** due to differences in WMI architecture and system service dependencies. Tenants using **Azure AD-joined devices without hybrid Azure AD join** are less likely to encounter this error, as ConfigMgr prerequisites are often pre-validated during enrollment. However, devices enrolled via **Intune autoenrollment** or **ConfigMgr standalone enrollment** with misconfigured policies are at higher risk.

Where To Look First: Logs and Event IDs

The primary diagnostic artifacts are located in: - C:\Windows\CCM\Logs\ccmsetup.log - C:\Windows\System32\smsts.log Search ccmsetup.log for the exact line: [Setup] Error: 0x87D01106 - Client installation failed — WMI corruption or CCMSetup prerequisite not met on target device In the **Event Viewer**, check the **Application** log for: - **Event ID 10000**: "CCMSetup failed to initialize due to missing prerequisites." - **Event ID 10001**: "WMI repository corruption detected during ConfigMgr client setup." Additionally, inspect smsts.log for lines containing Failed to load WMI namespace or Prerequisite check failed for CCMSetup.

Root Causes

1. WMI Repository Corruption

This occurs when the WMI repository becomes inconsistent or inaccessible. To diagnose, run Get-WmiObject -Namespace root\ccm -Class SMS_Client. If this command fails, WMI corruption is likely.

2. Missing Prerequisite Components

The ConfigMgr client requires specific Windows features (e.g., .NET 4.8, Windows Management Framework 6.2). Use Get-WindowsFeature -Name NET-Framework-45-2007 to verify installation.

3. Registry Key Misconfiguration

The registry key HKEY_LOCAL_MACHINE\Software\Microsoft\CCMSetup must exist and contain valid values. If this key is missing or corrupted, CCMSetup fails to initialize.

4. Service Dependency Failures The ccmexec service depends on Winmgmt (WMI service). If Winmgmt is disabled or in a failed state, client installation will fail.

Fix Procedure

  1. **Verify Prerequisite Components**: Get-WindowsFeature -Name NET-Framework-45-2007, Windows-Management-Framework-Core If missing, install with: Install-WindowsFeature -Name NET-Framework-45-2007, Windows-Management-Framework-Core
  2. **Repair WMI Repository**: Repair-WmiRepository -Namespace root\ccm If this fails, rebuild the repository: Remove-WmiRepository -Namespace root\ccm; Get-WmiObject -Namespace root -Class __Namespace | Where-Object Name -eq "ccm" | Remove-WmiObject
  3. **Recreate CCMSetup Registry Key**: Remove-Item -Path HKLM:\Software\Microsoft\CCMSetup -Recurse -Force
    Deleting this key will remove existing ConfigMgr client configuration. Ensure no active client is installed.
    Recreate the key with: New-Item -Path HKLM:\Software\Microsoft\CCMSetup -Force
  4. **Enforce Policy via Intune**: Navigate to **Intune admin center > Devices > Configuration profiles > Create profile**. Use the OMA-URI: ./Device/Vendor/MSFT/ConfigMgr/ClientInstallation/PrerequisiteCheck Set the value to Enabled to enforce prerequisite validation.

Error Code Variants

Error Code Description Distinguishing Factor
0x87D01106 WMI corruption or missing prerequisites Occurs during CCMSetup initialization
0x87D01104 Failed to connect to ConfigMgr site server Logs reference Failed to reach site server
0x87D01105 Insufficient disk space for client installation Logs reference Free space below threshold

Verification

After applying fixes, re-run the ConfigMgr client installation and monitor ccmsetup.log for the line: [Setup] Success: Client installation completed with exit code 0 In the **Intune admin center > Devices > All devices**, verify the device status shows "Compliant" and "Client installed." Additionally, confirm the registry key HKLM\Software\Microsoft\CCMSetup contains valid values for ClientVersion and InstallTime.

Prevention

To prevent recurrence, implement a **ConfigMgr Baseline Policy** via Intune: 1. Navigate to **Intune admin center > Device configuration > Baselines**. 2. Create a baseline targeting Windows 11 23H2 devices. 3. Include settings for: - Windows Features (ensure .NET 4.8 and WMI are enabled). - Registry Keys (validate HKLM\Software\Microsoft\CCMSetup exists). 4. Schedule compliance evaluations daily.
Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to preemptively identify WMI or prerequisite issues before client installation.

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.