Robopack Script Templates now support PSAppDeployToolkit 4.1.3

by Dean Ellerby |  27 August, 2025
Today we’re rolling out full PSAppDeployToolkit 4.1.3 support in Robopack Script Templates. 
That means you can create and maintain modern PSADT v4 packages with the latest UI model, improved process handling, and the 4.1.3 stability fixes, all from your usual Robopack workflow.

PSADT 4.1.3 shipped on 26 August 2025 and focuses on reliability and polish on top of the big 4.1.0 feature wave.

Why this matters

PSADT 4.1.x removed the long-standing need for ServiceUI to show dialogs when deploying as SYSTEM (Intune, ConfigMgr, etc.). PSADT now launches user-session UI securely without token manipulation, bringing a safer, more predictable experience and feature parity between the Fluent and Classic interfaces. Robopack Templates align with these changes so your packages behave consistently across estate and tooling.

What changed in Robopack Script Templates

We’ve refreshed the Script Templates to include an optional v4.1.3 Script Template you can select.
  • Default deploy mode is Auto (interactive when appropriate; silent when no user/process context applies)
  • Default Script Template is still 3.10.2, you can set this to 4.1.3 in Settings > Script Templates, or, create your own custom Script Template.

Add Template User Interface

When adding a custom script template, you'll see the following Add Template dialogue box:

How to get started

  • Go to Settings → Script Templates
  • Select the PSADT 4.1.3 template (or create your own custom variant).
  • Start building packages with the latest toolkit model—while keeping older versions available if you need them.

Before you switch!

If you use Custom App Settings that call PSADT commands, double-check them before moving to the PSADT v4.1.1 template. PSADT v4 introduces renamed commands, updated parameters, and a new session/UX model. Scripts that reference v3 commands may error or behave differently once the template targets v4.

Quick checks:
  • Audit any saved snippets that call PSADT functions (welcome prompts, process launches, restart prompts, MSI helpers, etc.)
  • Update v3 command names and parameters to their v4 equivalents.
  • Test in a pilot ring with the v4 template enabled before rolling out widely.
  • Not ready yet? Keep your default template on 3.10.2 and use a separate v4 template for new packages until everything is migrated.