The PowerShell App Deployment Toolkit is an open-source tool that wraps your setup installer, allowing you to create complex installation and uninstallation logic using built-in commandlets and functions. It has gained popularity among software packagers and system administrators.
This article will cover its evolution, focusing on key changes and whether migrating to version V4.1 might be worthwhile for you. I will wrap up this article by showing you some examples of .ps1 scripts for popular applications so you can see the key differences.
PSADT Evolution
PSADT v1 was released in 2013 and included basic functions for installs (Execute-Process, Execute-MSI), file copying, and registry editing, to assist SCCM administrators in automating some install logic. For the next two years, 2014 and 2015, it gained traction and introduced basic UI elements such as install welcome and install finish prompts.
PSADT V3 was released in 2016, and by 2024, it had become increasingly accepted in the enterprise environment and received multiple improvements and new built-in commandlets along the way.
PSADT V4 was released in 2024, with a total revamp of the user interface, a completely new commandlet, and a change to the overall structure to make it modular. This was also consistent with the modern visuals of Windows 11.
In 2025, PSADT V4.1 was released, providing a better integration with Intune.
Why Migrate to V4.1?
Unless you were using Service UI, all scripts created and deployed through Intune did not interact with the device’s users before V4.1. This was also a problem if you wanted to deploy such apps using Autopilot during the OOBE experience.
Read more about the Service UI in this article.
Also, deploying while the user was away from the PC in a computer lock state would often result in a failed installation due to a misinterpretation of the correct install context.
Version 4.1 finally integrated the Service UI into the script and automatically detects whether the user is logged in to the machine and actively interacting with the explorer, or if the machine is in OOBE state and the app needs to be deployed differently.
So all you have to do now is to simply call the Invoke-AppDeployToolkit.exe with the install/uninstall parameters, and you are ready to go.
Another reason to upgrade to V.4.1 is the modern design of UI elements during installation. It works well with Windows 11, and believe me, the management and end users in an enterprise environment love to have a sleek, clean, and integrated user interface.
PSADT 3.x example:
PSADT 4.1 example:
If you made up your mind and decided to migrate, you have two options:
- Use the PSADT migration guide form to automate your migration of your current v3 scripts.
- Start from scratch with a PSADT v4.1 template, and try to map your old commands and functions from version 3.
If your client or the company you work for does not expect a full bulk package revamp, I recommend that you go for the second method and release the application package updates using the v4.1 template one at a time. This will help you get accustomed to the new PSADT cmdlets and learn the tool more efficiently.
To finish up, as promised, here are some PSADT scripts I created using both v3 and v4.1.
PS1 Script Templates
For v3, rename the .ps1 scripts to Deploy-Application.ps1, then place them in the root folder of the toolkit.
For v4_1, rename the .ps1 scripts to Invoke-AppDeployToolkit.ps1, then place them in the root folder of the toolkit.Make sure you place the necessary source files in the Files folder, regardless of the version
Final Takeaways
- PSADT has grown a lot over the years: from simple automation scripts to a modern, modular toolkit with a clean Windows 11-style interface in version 4.1.
- The biggest improvement in 4.1 is that it finally handles user interaction properly, especially during Intune and Autopilot deployments, without needing extra tools like ServiceUI.
- Deployments are now much easier: in most cases, you just call Invoke-AppDeployToolkit.exe and the toolkit figures out whether someone is logged in or if the device is still in OOBE.
- If you want to migrate, you can either use the official docs or gradually rebuild by using new templates. Most teams prefer updating packages one by one to learn the new commands and avoid breaking anything.
Conclusion
If you’re using PSADT in an enterprise environment, along with Intune or Autopilot, it’s worth moving to version 4.1 of it. It reduces headaches, modernizes the user experience, and makes your deployment process much easier.
Check out PacKit if you need a tool that bridges the gap between application packaging and deployment.
Here are a few of its post-packaging configuration and deployment capabilities:
- PSADT Wrapper
- IntuneWin Auto-Generator
- App Catalog – WinGet
- Command Line Finder
- Intune Detection Rules
- Intune OS Requirements
