The application has been deploying through Intune all morning. Most laptops received it, but several machines are still showing an installation problem
This is exactly the kind of ticket where random troubleshooting can waste hours.
Instead, break the deployment into stages.
Step 1: Check the Assignment
Before looking through logs, confirm that the application is actually assigned to the affected device or user.
Check:
Required assignments
Available assignments
Included groups
Excluded groups
Assignment filters
Don’t troubleshoot software installation before confirming the software was supposed to be installed.
Step 2: Check the Installation Command
Review your install command.
An application that installs manually with:
setup.exe
may require silent arguments when deployed through enterprise management.
The exact switches depend on the installer.
For an MSI-based installer, silent operation may look like:
msiexec /i application.msi /qn
But never blindly copy installation arguments from another application.
Different packages use different installer technologies and command-line parameters.
Step 3: Test the Command Locally
Take your exact Intune installation command and test it on a clean test device.
Don’t test a different command.
Test the exact command being deployed.
This helps answer a fundamental question:
Is Intune failing, or does the installation command itself fail?
Step 4: Check Your Detection Rule
This is extremely important.
Installing an application and detecting an application are two separate steps.
Imagine Intune successfully installs an application but your detection rule looks for:
C:\Program Files\Company\App\App.exe
while the actual file is installed to:
C:\Program Files\Company Application\App.exe
The software could be working perfectly, but your detection logic is wrong.
Intune cannot determine success correctly if the detection rule doesn’t represent the installed application.
Step 5: Check Dependencies and Requirements
Consider whether the app depends on:
.NET components
Another application
A particular Windows architecture
A minimum Windows version
Available storage
A required reboot
Also review requirement rules in Intune.
The application may be working exactly as configured while the endpoint doesn’t satisfy your requirements.
Step 6: Investigate Intune Management Extension
For Win32 application deployment, the Intune Management Extension is one of the most important troubleshooting components.
Use the IME logs to follow the deployment process.
Instead of searching for random errors, try to establish:
Was the app evaluated?
Was it required?
Did the installer start?
What did the installation process return?
What happened during detection?
That gives you a story rather than a collection of unrelated log entries.
Step 7: Compare with a Successful Device
If 50 computers installed the app and three failed, use one of the successful devices as your control.
Compare:
Windows version
Architecture
Existing version of the app
Disk space
Group targeting
Dependencies
Security software
Installation context
The difference between the working and failing device often reveals the cause.
Final Thoughts
When an Intune application deployment fails, troubleshoot the deployment chain:
Assignment → Requirements → Download → Installation → Exit code → Detection
Don’t immediately rebuild the .intunewin package.
Find the stage that failed first.
Once you identify that stage, the problem becomes much easier to solve.