Home › Microsoft Intune › 0x87D10D37

Microsoft Intune · 0x87D10D37 · Windows 11 23H2

Microsoft Intune Error 0x87D10D37 on Windows 11 23H2: Software Distribution Agent Installation Failure

The error occurs due to insufficient disk space or network issues preventing the Software Distribution Agent installation. Free up disk space or check network connectivity to resolve.

Error Details

FactValueSourceNote
Exact error stringSoftware Distribution Agent could not install — disk space or network conditionIntune Management Agent logs->
Affected OS build rangeWindows 11 23H2 and newerMicrosoft Intune documentation->
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneAgentRegistry Editor (regedit)-> Might be missing or corrupted.
Relevant service/endpoint URLhttps://endpoint.microsoft.comIntune Management Portal-> Check for updates or policies.
Log line signatureError installing agent due to resource constraintsC:\ProgramData\Microsoft\IntuneManagementAgent\Logs\IntuneSetup.log-> Look for this exact string in logs.

Log Files to Check

What This Error Actually Means

The error code 0x87D10D37 indicates a failure during the installation of the Microsoft Intune Software Distribution Agent. Specifically, this error is raised by the Intune Management Agent when it encounters either insufficient disk space on the target device or an unstable network connection preventing successful communication with the Intune service. The error originates from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneAgent registry key and is logged in both C:\ProgramData\Microsoft\IntuneManagementAgent\Logs\IntuneSetup.log and C:\Windows\System32\LogFiles\WMI\WMILogfile.txt. This issue typically occurs during the deployment or update process of Intune-managed applications.

Affected Versions and Scope

This error is documented to affect devices running Windows 11 23H2 and newer. It does not impact older versions of Windows, including Windows 10 or earlier builds of Windows 11. The issue is specific to environments where Intune is used for software distribution and management. Tenants utilizing Microsoft Endpoint Manager (MEM) with Intune integration are particularly susceptible if their devices fall within the affected OS build range.

Where To Look First: Logs and Event IDs

To diagnose this issue, examine the following log files: - C:\ProgramData\Microsoft\IntuneManagementAgent\Logs\IntuneSetup.log: Search for the exact error line Error installing agent due to resource constraints. - C:\Windows\System32\LogFiles\WMI\WMILogfile.txt: Look for entries related to Intune Management Agent communication failures. Additionally, review Event Viewer logs with the following Event IDs: - 1000: Indicates a failure in the Intune Management Agent service. - 4509: Signifies issues with WMI communication, which is critical for Intune operations. Use the PowerShell cmdlet Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to retrieve relevant diagnostic logs directly from the event viewer.

Root Causes

Disk Space Constraints

The most common cause is insufficient disk space on the target device. The Intune Management Agent requires a minimum of 1 GB of free space in the system directory (C:\Windows\System32). Use Get-PSDrive -Name C | Select-Object Free to check available space.

Network Connectivity Issues

The device may be unable to reach the Intune service endpoint at https://endpoint.microsoft.com. Verify connectivity using Test-NetConnection -ComputerName endpoint.microsoft.com -Port 443.

Corrupted Intune Management Agent Files

Damaged or incomplete installation files can prevent proper setup. This is often indicated by partial log entries in IntuneSetup.log. Use Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\IntuneAgent to inspect the agent's configuration.

Group Policy Conflicts

Misconfigured Group Policies can block Intune operations. Check for conflicting policies using gpresult /H gpresult.html.

Fix Procedure

  1. Free Up Disk Space: - Clear temporary files with Remove-Item -Path C:\Windows\Temp\* -Recurse -Force. - Use fsutil space query C: freebytes to monitor available space.
  2. Troubleshoot Network Connectivity: - Ensure the device can reach https://endpoint.microsoft.com via curl -I endpoint.microsoft.com. - Check firewall rules with netsh advfirewall show currentprofile.
  3. Reset Intune Management Agent: - Delete the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneAgent. - Restart the Intune Management Agent service via Restart-Service Winmgmt.
  4. Reinstall the Software Distribution Agent: - Download the latest agent from the Intune admin center. - Install using msiexec /i IntuneAgent.msi /qn.
Warning: Deleting the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneAgent will reset all Intune-specific configurations. Ensure you have backed up critical data before proceeding.

Error Code Variants

Error CodeDescription
0x87D10D36Insufficient privileges during installation
0x87D10D38Missing system dependencies
0x87D10D39Corrupted installation package

Verification

After applying fixes, verify success by: - Checking IntuneSetup.log for Successfully installed agent. - Confirming the Intune Management Agent status via Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'". - Ensuring the device appears in the Intune admin center under Devices > All devices.

Prevention

Implement the following measures: 1. Monitor disk space using New-WmiEventFilter -Name "DiskSpaceMonitor" -Query "SELECT * FROM Win32_PerfRawDataLogicalDiskLogicalDisk WHERE FreeMegabytes < 500". 2. Regularly audit network configurations to ensure uninterrupted access to https://endpoint.microsoft.com. 3. Establish a maintenance schedule for updating Intune components via the Intune admin center > Policies > Device policies.
TIP: Use dsregcmd /status to quickly verify device enrollment status and diagnose potential issues.
By following this guide, sysadmins can effectively troubleshoot and resolve the 0x87D10D37 error, ensuring smooth operation of Intune-managed devices.

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.