Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Win32 app installation timed out — installer ran longer than the configured maximum runtime (default 60 minutes) | Microsoft Intune logs | -> |
| Affected OS build range | Windows 11 23H2 | OS version details | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsIntune\Win32AppInstallTimeout | Registry configuration | -> |
| Relevant service/endpoint URL | https://graph.microsoft.com/v1.0/deviceManagement/mobileApps | Microsoft Graph API endpoint | -> |
| Log line signature | [Error] 0x800705B4 - Installation timed out after 60 minutes. | ApplicationDeployment.log | -> |
Log Files to Check
%ProgramData%\Microsoft Intune\Logs\ApplicationDeployment.log%ProgramData%\Microsoft Intune\Logs\DeviceManagementService.log
What This Error Actually Means
The error code0x800705B4 is a Windows system error indicating a timeout during a Win32 app installation orchestrated by Microsoft Intune. This error is raised by the Intune agent's application deployment component when the installer process exceeds the configured maximum runtime (default 60 minutes). The hexadecimal code translates to a Windows HRESULT value where 0x800705B4 specifically maps to ERROR_INSTALL_TIMED_OUT, a system-level error reserved for installation processes that fail to complete within their allocated time window. This error is distinct from generic timeout errors because it is explicitly tied to the Intune-managed Win32 app deployment pipeline, which enforces strict time constraints to prevent indefinite hangs during installation.
Affected Versions and Scope
This error occurs exclusively on devices running **Windows 11 23H2** (OS build 22621 or later). It is triggered when Intune policies or device configurations enforce the default 60-minute timeout for Win32 app installations. Earlier OS builds, such as Windows 11 22H2 (22000.x), may exhibit similar behavior but are not explicitly documented as being affected by this error code. The issue is not tied to specific tenant configurations but is amplified in environments where Win32 apps require extended installation times (e.g., large software suites, complex custom installers). Devices enrolled in co-management or hybrid Azure AD environments are equally susceptible, provided the Intune agent is managing the Win32 app deployment.Where To Look First: Logs and Event IDs
The primary diagnostic artifacts are located in the Intune log directory. Inspect%ProgramData%\Microsoft Intune\Logs\ApplicationDeployment.log for the exact error line:
[Error] 0x800705B4 - Installation timed out after 60 minutes.
Cross-reference this with %ProgramData%\Microsoft Intune\Logs\DeviceManagementService.log to identify upstream triggers, such as policy enforcement or Graph API communication delays. Use the following PowerShell cmdlet to parse logs:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object { $_.Message -match "0x800705B4" }
Event IDs **1002** and **1003** in the **Application** log (source: Microsoft-Windows-IntuneManagementExtension) often accompany this error, signaling deployment initiation and failure, respectively.
Root Causes
1. Installer Runtime Exceeds Policy Limit
The most common cause is an installer that legitimately requires more than 60 minutes to complete. This is often seen in enterprise applications with post-installation configuration steps. To confirm, check the installer's execution time inApplicationDeployment.log for prolonged activity before the timeout.
2. Network or Resource Contention
Slow network speeds or high CPU/disk utilization on the device can delay installation. UseGet-Process -Name "IntuneManagementExtension" to monitor resource usage during deployment. Network issues are often logged with Event ID **1004** in the same log source.
3. Antivirus/Endpoint Protection Interference
Real-time scanning or heuristic analysis by endpoint protection software can artificially inflate installation time. Look for "blocked" or "quarantined" entries in the antivirus logs, or useGet-MpComputerStatus to verify real-time protection status.
Fix Procedure
- Adjust the timeout registry key:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\WindowsIntune\Win32AppInstallTimeout" -Name "Value" -Value 9000000 -Type DWord(9000000 milliseconds = 150 minutes). - Deploy the change via Intune using an OMA-URI configuration profile:
./Device/Vendor/MSFT/WindowsIntune/Win32AppInstallTimeoutwith a payload of9000000. - Verify the policy using:
Get-CimInstance -Namespace root\cimv2 -ClassName Win32_Registry | Where-Object { $_.Keyname -eq "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsIntune\Win32AppInstallTimeout" } - Redeploy the Win32 app via Intune admin center > Apps > Win32 apps > [App Name] > Assignments.
Modifying the registry key on enrolled devices without a configuration profile may lead to inconsistent timeout settings and potential deployment failures.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x800705B4 | Installation timeout | Occurs after 60-minute threshold in ApplicationDeployment.log |
0x80070005 | Access denied | Logged when the Intune agent lacks permissions to write to the app's installation directory |
0x80073CF9 | Installation failed | Logged when the installer exits with a non-zero exit code, unrelated to timeout |
Verification
After applying the fix, monitorApplicationDeployment.log for a line containing:
[Success] Installation completed within 90 minutes.
In the Intune admin center, navigate to Devices > Windows > Windows 10 and later > [Device Name] > Apps to confirm the app status is "Success." Use the Graph API to validate:
Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices?$filter=deviceName eq 'DEVICE_NAME'"
Look for "deviceEnrollmentType": "windowsAutoEnrollment" and "complianceState": "compliant".
Prevention
To prevent recurrence, create a baseline configuration profile in Intune admin center > Devices > Windows > Windows 10 and later > Configuration profiles > Create profile with the OMA-URI:./Device/Vendor/MSFT/WindowsIntune/Win32AppInstallTimeout
Set the value to 9000000 and assign it to all devices requiring Win32 app deployments. Additionally, use PowerShell to audit existing policies:
Get-MgDeviceManagementDeviceConfiguration -Filter "name eq 'Win32 Timeout Policy'"
Use
Get-Content -Path "C:\ProgramData\Microsoft Intune\Logs\ApplicationDeployment.log" | Select-String "0x800705B4" to quickly identify recurring timeout events in large deployments.