Win32 app stuck on installing in Intune

A user reports that an app from Intune does not arrive. In the admin center it shows as pending or failed. This is how you find out where it is stuck and how to fix it.

The status in the admin center

Go to Apps > All Apps and select the app. Under Monitor, Device install status shows for each device the status, the details of that status and the last check-in. User install status shows for each user the number of installed, failed and not installed apps.

How Intune retries

How and when Intune tries again depends on the outcome:

When the installer returns a return code that is set as Retry in the app, the agent tries three times, five minutes apart. Intune adds default return codes when you create the app; you can change them.
A required app that is missing is offered again within about 24 hours, according to Microsoft.
When a download takes longer than 8 hours, Intune cancels it and starts again.
When the assignment has an installation deadline, the IME downloads the app but only installs it at the deadline. The Company Portal already shows Installing by then.

The IME fetches new assignments at its own check-in. Microsoft gives two intervals for it: every hour and at a restart of the service or the device (the page on Win32 apps), and every 8 hours (the page on the Intune Management Extension). Since late September 2026, Intune also sends a push notification when Win32 apps change. You do not have to wait: a sync from the Company Portal, Settings or the admin center also starts an IME check-in, and that is also how you have a failed required app tried again.

The logs you need

The logs of the Intune Management Extension are usually in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs. For Win32 apps the most important ones are:

AppWorkload.log: check-ins, installations, detection and applicability;
AppActionProcessor.log: detection and applicability;
IntuneManagementExtension.log: check-in, policies and reporting.

When the installation failed, you can also have those logs collected from the admin center, in the app’s installation details. You get there through Troubleshooting + support > Troubleshoot: select the user, the device, Managed Apps and the app. How that works and what the limits are is on Collect logs from an Intune device.

What Endpoint Toolbelt adds

With Endpoint Toolbelt, the user or the service desk fixes this on the device itself, without admin rights and without waiting for the next attempt:

Retry apps & policies makes the IME look again at once and shows for each app how far its last attempt got: download, hash check, unpacking, installation with its exit code, or not detected after the installation. A download that has stopped moving is reported as stuck.
When the download itself is the problem, Clear downloaded app content removes unpacked app files that are not in use, so they are downloaded again.
When that does not help, Full IME reset clears the app state, the downloads and the policy cache, and has the device fetch everything again.