Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x87D00607 | Intune Management Extension log | SYNC_E_NEED_RESTART |
| Affected build range | Windows 10/11 (All supported builds) | Microsoft Intune Documentation | OS independent for Win32 apps |
| Registry key involved | HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations | Windows Registry | Indicates pending reboot state |
| Relevant service/endpoint URL | https://intune.microsoft.com | Microsoft Intune Admin Centre | Apps > All apps > Device install status |
| Log line signature | Exit code: 3010 | IntuneManagementExtension.log | Search for 'Restart required' or exit code |
Log Files to Check
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.logC:\Windows\Logs\DISM\DISM.log
What This Error Actually Means
Error code 0x87D00607 is a specific status indicator within the Microsoft Intune Management Extension (IME) framework, mapping to the Windows error constant SYNC_E_NEED_RESTART. When you encounter this hex value in your deployment logs or device compliance reports, it signifies that the Win32 app installation process has technically completed its execution sequence, but the installer explicitly requested a system reboot to finalize configuration changes. This is not a failure of the Intune service itself, nor is it a network connectivity issue; rather, it is a state synchronization problem between the local Windows Installer service and the cloud-based compliance engine.
The component raising this error is the IntuneManagementExtension service running on the endpoint. When a Win32 app installer (whether an MSI, EXE, or script) returns an exit code of 3010 (Success with Reboot Required) or 1641 (Success with Reboot Initiated), the IME captures this return value. Instead of marking the application as "Installed" immediately, the IME flags the device status as pending a restart. The error 0x87D00607 is the IME's way of telling the administrator: "The payload executed successfully, but the operating system requires a reboot to complete the transaction. Until that reboot occurs, I cannot verify compliance."
This behavior is by design to prevent partial installations from being marked as compliant. If an application modifies system files, registry keys, or services that require a restart to take effect, marking it as installed before the reboot would result in a non-functional state. Therefore, 0x87D00607 is effectively a "soft failure" that resolves itself upon the next successful device check-in post-reboot.
Affected Versions and Scope
This error code is prevalent across all supported builds of Windows 10 and Windows 11, including Enterprise, Education, and Pro editions. It is not tied to a specific cumulative update or feature release but is inherent to how the Intune Management Extension interacts with the Windows Installer (MSI) engine and custom executable wrappers. The scope of impact includes any Win32 app deployment where the installer logic dictates a reboot requirement.
Tenant configurations that frequently encounter this issue include environments with aggressive update policies, devices enrolled via Autopilot with heavy application provisioning profiles, and organizations deploying large-scale software updates via Win32 apps rather than Windows Update for Business. It is important to note that this error does not affect iOS, Android, or macOS platforms, as their respective management agents handle reboot requirements differently (often requiring explicit user action or scheduled maintenance windows). In the Windows ecosystem, however, 0x87D00607 will appear on any device where the IME detects a pending reboot state triggered by an application installation.
Devices that are offline for extended periods may also exhibit this error persistently in the portal until they reconnect and perform a heartbeat check. The error is not version-specific to the Intune service backend but is dependent on the client-side IME version. Ensuring your devices are running the latest IME updates via Windows Update or Microsoft Endpoint Configuration Manager co-management can mitigate older bugs related to reboot detection, though the core logic of 0x87D00607 remains consistent.
Where To Look First: Logs and Event IDs
To diagnose why a device is stuck in this state or to confirm that the installation actually succeeded before the reboot flag was raised, you must inspect local logs on the endpoint. The primary source of truth is the Intune Management Extension log file located at C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log. You should search this log for the string 0x87D00607 or Restart required. Look specifically for lines indicating the exit code returned by the installer. A typical signature line will read: Exit code: 3010, confirming that the application itself signaled success but requested a reboot.
Additionally, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin. Look for Event ID 819, which often details the execution status of Win32 apps. Another critical log to review is C:\Windows\Logs\DISM\DISM.log if the installation involved system component servicing, though this is less common for standard Win32 apps. In the Intune Admin Center at https://intune.microsoft.com, navigate to Apps > All apps > [App Name] > Device install status. Here, you will see the device listed with a "Failed" status and the error code 0x87D00607. This portal view does not show the detailed exit codes, so local log analysis is mandatory for root cause determination.
Root Causes
Installer-Defined Reboot Requirement
The most common cause is that the Win32 app installer (MSI or EXE) explicitly returns exit code 3010. This is standard behavior for many enterprise applications, such as Adobe Creative Cloud, Microsoft Office updates, or driver packages. The installer modifies system resources that are locked by running processes, necessitating a reboot to release those handles. You can distinguish this cause by checking the IntuneManagementExtension.log for the specific exit code 3010 immediately following the installation command execution.
Pending Windows Update Reboot
A second frequent cause is a pending reboot from Windows Updates. If a device has downloaded and staged critical updates but has not yet rebooted, the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations may contain entries. The IME checks for this key before running new installations. If it detects pending file renames, it may preemptively flag subsequent installs as requiring a reboot, even if the specific app installer did not request one. This is a protective measure to ensure system stability.
Stale Reboot Flags from Previous Installations
Sometimes, a previous application installation failed or was interrupted, leaving behind reboot flags in the registry without actually completing the reboot. This "zombie" state causes all subsequent Intune deployments to fail with 0x87D00607. You can identify this by checking for the presence of reboot-related registry keys even when no recent Windows Updates or app installs have occurred.
Fix Procedure
- Verify Installation Success: First, confirm that the application is actually installed on the device. Use PowerShell to query the installed applications list:
Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*AppName*"}. If the app is present, the installation succeeded, and the issue is purely a compliance state mismatch. - Clear Pending Reboot Flags (If Stale): If you suspect stale flags are blocking progress, you can clear them via PowerShell. Run the following command to remove the pending file rename operations:
Remove-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager' -Name 'PendingFileRenameOperations' -ErrorAction SilentlyContinue. This forces the system to believe no reboot is pending. - Trigger a Manual Sync: Force the Intune Management Extension to re-evaluate the device state. Use the following cmdlet to trigger a sync:
Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices('{deviceId}')/syncDevice". Replace{deviceId}with the actual ID from the Intune portal. - Reboot the Device: If clearing flags does not resolve the issue, a physical reboot is required. Use the command:
Restart-Computer -Force. After the reboot, wait for the device to check in with Intune (typically 5-10 minutes). - Verify Compliance Status: Return to the Intune Admin Center at
https://intune.microsoft.com, navigate toApps > All apps > [App Name] > Device install status, and confirm the status has changed from "Failed" to "Installed".
PendingFileRenameOperations) can cause system instability if a critical Windows Update or driver installation is genuinely waiting for a reboot. Only perform this action if you have verified that no critical updates are staged and the device has been idle for an extended period without resolving the flag.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x87D00607 |
SYNC_E_NEED_RESTART | Installer returned 3010/1641; reboot required for completion. |
0x80070005 |
Access Denied | IME lacks permissions to execute the installer or write to the target directory. |
0x80070643 |
Installation Failed | Installer returned a non-success exit code (e.g., 1603); actual installation failure. |
0x87D00215 |
Download Failed | Network issue or content source unavailable; payload never reached the device. |
Verification
To prove the fix worked, you must observe two distinct states. First, in the local IntuneManagementExtension.log, search for the message App installation completed successfully followed by a compliance check that returns Installed. Second, in the Intune Admin Center, the device status for the specific app must transition from "Failed" to "Installed". You can also verify via PowerShell by checking the application's presence and ensuring no reboot flags remain: Test-Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager' -Name 'PendingFileRenameOperations'. If this returns False, the reboot flag is cleared.
Prevention
To prevent recurrence, configure the Win32 app assignment settings in Intune. Navigate to Apps > All apps > [App Name] > Assignments. Set the "Device restart grace period" to an appropriate value (e.g., 240 minutes) and enable "Notify user before restarting". This allows users to schedule reboots, reducing unexpected downtime. Additionally, for MSI packages you create, use tools like WiX Toolset or InstEd to remove the ForceReboot action from the install sequence if the reboot is not strictly required by the application logic. For devices with persistent reboot flags, consider deploying a PowerShell script via Intune that clears stale reboot keys during maintenance windows: Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object {$_.Id -eq 819} can help monitor these events proactively.
./Device/Vendor/MSFT/ManagedConfiguration/Policy/Reboot to query reboot status remotely via Graph API, allowing you to identify devices with pending reboots without logging into each machine individually.