Application Notes
Deployment notes and known issues for commonly used applications.
Adobe Acrobat Reader DC
- Adobe Acrobat Reader shares the same Add/Remove Programs name as Acrobat Pro, which can cause detection conflicts
- If Creative Cloud is installed, the Reader installer may detect an existing Acrobat installation and fail. Use Custom App Settings with a pre-install PowerShell command to handle removal
- Radar Tracking is disabled for Adobe Acrobat because the shared product name causes detection confusion between Reader and Pro editions
- Workaround for detection: use file-based detection with
AcroRd32.exeinstead of registry-based detection
Google Chrome
- Chrome updates silently in the background, but the new file version is not written until the browser process is fully closed. Until then, Intune may report detection failures (error 0x87D300D9) because the file on disk still shows the old version
- This is expected behaviour — once the user closes and reopens Chrome, the version updates and detection succeeds on the next Intune check-in
- To avoid this, use Apps to Close in Custom App Settings with the process name
chromeso that PSADT prompts the user to close the browser before the update runs
Microsoft 365
- The MSIX package for Microsoft 365 has been disabled because the version in the app manifest does not match the actual version. This is an upstream vendor issue
- Use the Instant App for M365 deployment, not a manual upload of the 3.8 GB installer
Microsoft Teams
- The MSIX detection script may use text comparison instead of version comparison, which can cause incorrect detection results
- Workaround: manually edit the detection script to cast to
[version]type and use-gecomparison
Spotify
- Spotify fails with error code 23 when deployed in system context because the installer cannot run as administrator
- Deploy Spotify in User context and assign to user groups (not device groups)
- Best deployed without Custom App Settings
1Password
- 1Password can enter an update loop when installed in SYSTEM context due to permissions issues
- Deploy in User context for reliable updates
- If a newer version is already installed and deployment fails, enable Match newer versions in the patch flow and click Sync app settings
Notepad++
- Notepad++ packages in Robopack are sourced from the WinGet repository, not from the app's built-in updater. This means Robopack deployments are not affected by Notepad++ updater vulnerabilities
- If Notepad++ is running during installation, add
/closeRunningNppas an install parameter or use Apps to Close in Custom App Settings with the process namenotepad++
SQL Server Management Studio (SSMS)
- SSMS has separate repositories for v21 and v22 — ensure you are targeting the correct version
- Updates may fail if an in-place upgrade is attempted. Use Custom App Settings to configure an uninstall/reinstall approach instead
Docker Desktop
- Docker Desktop is temporarily disabled in Robopack because the testing VMs do not support the Hyper-V requirements
- Expected to be available again in Q1 2026
Firefox
- Multiple language versions of Firefox can cause Radar detection issues
- If a patch flow is not picking up new Firefox versions, check if a language filter is set that may be blocking the update
Citrix Workspace
- The WinGet version may be outdated compared to the vendor's direct download
- Watch for platform mismatches — the WinGet version may be x86 while your environment expects x64
Dell Command Update
- Installation may fail if .NET Desktop Runtime 8.x is not present. Use Custom App Settings to install the prerequisite in the pre-install phase
- Scripts in Custom App Settings must use PSADT format (e.g.
Start-ADTProcessfor PSADT v4)
Company Portal (MSIX)
- MSIX deployment may fail with error 0x8007EA61 or other errors
- Workaround: try disabling dependencies through Custom App Settings, or change the install context
Logitech G HUB
- DLL issues in system context prevent this application from being packaged
- Cannot be deployed through Robopack currently