โ† Windows & Intune
๐Ÿ“ฑ Intune

Fix Package Installation Failures in Intune

Diagnose and resolve Win32 app deployment errors using IME logs and policy refresh techniques. Covers the most common failure codes and their root causes.

โš ๏ธ
Common symptom: App shows "Failed" in Intune portal or never installs. Root cause is almost always in the IME logs โ€” start there.
Check IME Logs First

The Intune Management Extension logs everything โ€” always read them before trying anything else.

C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log

Open the log and search for the app name or error code. Common errors: 0x80070002 (file not found), 0x80004005 (access denied), 0x87D300C9 (app detection failed).


Force a Policy Sync

Make the device re-download and re-attempt the deployment immediately rather than waiting for the next check-in cycle.

# Option 1: PowerShell (run as admin)
Get-ScheduledTask | Where-Object {$_.TaskName -like "*PushLaunch*"} | Start-ScheduledTask

# Option 2: Company Portal app
# Open Company Portal โ†’ Settings โ†’ Sync

Verify Detection Rule

The most common cause of failure is a detection rule that doesn't match the actual installed state. Check file path, registry key, or MSI product code against what's actually on the device.

# Test file detection:
Test-Path "C:\Program Files\YourApp\app.exe"

# Test registry detection:
Get-ItemProperty "HKLM:\SOFTWARE\YourApp" -ErrorAction SilentlyContinue

# Test MSI product code:
Get-WmiObject Win32_Product | Where-Object {$_.Name -like "*YourApp*"} | Select Name,Version

Re-package & Re-upload if Needed

If the .intunewin file is corrupted or the install/uninstall scripts have errors, re-package from scratch.

IntuneWinAppUtil.exe -c C:\SourceFolder -s installer.exe -o C:\Output

Then in Intune: delete the old app and create a new Win32 app with the re-packaged .intunewin file.