Skip to main content

Known Limitations

This page lists current limitations in Robopack and their expected timelines. For workarounds, see Troubleshooting.

Platform support

LimitationDetailsStatus
ARM64 devicesRobopack does not yet support ARM64 Windows devices. The automated test system currently supports x64 and x86 only.Planned — H1 2026
macOSmacOS app deployment is not yet available. Approximately 7,500 macOS applications are planned.Planned — H1 2026

Deployment & patching

LimitationDetailsStatus
App dependenciesDependencies configured in Intune are lost when an app is updated via Robopack. Dependencies for custom apps are not yet supported natively. Workaround: handle dependencies within Custom App Settings using pre-install PowerShell to detect and install prerequisites.Planned — H1 2026
Scheduled deploymentsIt is not currently possible to schedule deployments for specific dates or times.Planned — Q1 2026
Cannot move apps between patch groupsOnce an app has a patch flow with Intune deployments, it cannot be moved to a different patch group. The app must be removed from the current group and added to the new one.By design
Pausing a wave does not pause IntunePausing a deployment wave in Robopack does not remove the assignment in Intune. The Intune deployment remains active.By design
Cannot reorder waves via drag and dropWaves must be deleted and recreated in the desired order.Not yet supported
Assignment templates not used by patch flowsAssignment templates are designed for the manual import process. Patch flows require groups to be specified directly in waves.By design
Intune metadata not preserved on updateWhen updating applications in Intune via Robopack, metadata such as Owner, Notes, and Categories is not preserved.Under consideration

Custom App Settings

LimitationDetailsStatus
One Custom App Setting per app per tenantYou cannot have multiple Custom App Settings for different user groups within the same tenant. One setting applies to the whole app. For multi-tenant setups, settings can differ per tenant.By design
Edit Package changes don't carry to new versionsChanges made in "Edit Package" apply to the current version only. Use Custom App Settings instead for persistent changes across versions.By design
Script Accessory file size limitApproximately 100 MB. This cannot be increased.Hard limit
Custom scripts not code-signed by RobopackRobopack signs Deploy-Application.ps1 and PSADT framework files, but not customer-uploaded custom scripts. If your tenant requires signed scripts, custom scripts must be signed separately.By design
Backtick character escapingAdding backtick characters (`) in Custom App Settings through the UI adds an extra backtick each time, preventing certain PowerShell escape sequences from working correctly.Known bug

Radar Tracking

LimitationDetailsStatus
Radar does not remove devices from groupsOnce a device is added to a Radar group, it is not automatically removed after a successful update or OS wipe.Under investigation
Adobe Acrobat Radar disabledRadar is disabled for Adobe Acrobat because the product name is shared between Reader and Pro editions, causing detection confusion.Known issue
Custom apps not supported in RadarRadar only works with Instant Apps. Custom-uploaded apps show as "Found but not available for patching".By design
Firefox multi-language Radar issuesMultiple language versions of Firefox cause Radar detection problems.Known issue

Roles & permissions

LimitationDetailsStatus
RBAC roles are limitedCurrent roles may not provide the granularity some organisations need. For example, Robopatch Writer can only modify flows the user created.More granular roles planned
Organisation Administrator required for Instant Apps in Patch GroupsOnly users with the Organisation Administrator role can add Instant Apps to Patch Groups.By design

User interface

LimitationDetailsStatus
No audit logsAudit logging for user actions is not yet available.Planned
No bulk app operationsCannot perform bulk actions on multiple apps simultaneously.Under consideration
No CSV/report export from portalNo direct export to CSV from the portal UI. The API can be used with scripting. Reports are available in preview at https://app.robopack.com/reports.In preview
Developer field not customizableAlways shows "robopack.com".Planned
UI language is English onlyMulti-language support for the Robopack user interface is planned but has no official release date.Planned
Custom App Settings not available via APIThe API does not yet support managing Custom App Settings programmatically.Planned

Application-specific

LimitationDetailsStatus
Docker DesktopTemporarily disabled due to VM/Hyper-V requirements on the testing infrastructure.Expected back Q1 2026
Microsoft 365 Copilot MSIXDisabled because the manifest file has a version reporting bug. Will be re-enabled once the vendor fixes it.Waiting on vendor
SpotifyCannot be deployed in system context. Spotify's installer is not enterprise-friendly and fails with error code 23 when run as administrator.Vendor limitation
Logitech G HUBDLL issues in system context prevent packaging.Cannot be packaged currently

Other

LimitationDetailsStatus
Cannot update installer in existing custom packageYou must upload a new package. Use Custom App Settings for supplementary file changes.By design
Default PSADT 3.10.2 template cannot be deletedThe default script template is a system template and cannot be removed or disabled.By design
Large file upload timeoutsVery large files (500 MB+) may cause timeout errors in the web interface. Try a different browser, or share files via SharePoint with support.Known issue
"Error code: Out of memory" when uploading custom appSome applications, such as Autodesk AutoCAD or Everway ClaroRead, cause the browser tab to crash with the message "Error code: Out of memory". The issue seems to only happen when using a Chromium-based browser such as Google Chrome or Microsoft Edge. Workaround: use a non Chromium-based browser such as Mozilla Firefox, LibreWolf, Waterfox, etc.Known issue
MSIX detection rule bugMSIX/Microsoft Store apps may not change their detection rule to "greater than or equal" when selected. The detection script uses text comparison instead of version comparison. Workaround: manually edit the detection script to cast to [version] type and use -ge comparison.Known bug