Today we are going to have a look at the new PowerShell script installer feature that is available since January 2026 in Microsoft Intune.
It’s now possible to upload a PowerShell script as the installer instead of specifying a command line when adding a Win32 app package. A lot of applications can be installed using only a command line, but lots of people use a PowerShell script to perform additional steps, like changing a registry key, copying a file to a certain location or writing a log file to %programdata%\Microsoft\IntuneManagementExtension\Logs.
And of course, we could already use PowerShell scripts wrapped as Win32 package to install applications, but this new feature has a great benefit on the command line feature. When we wanted to use a PowerShell script, the script needed to be included inside the intunewin file in the past.
This meant that we had to rewrap the entire package, even though we only needed to change a typo in our PowerShell script. This is no longer needed when using the new PowerShell script installer feature. We can just wrap our installer files without the PowerShell files, and upload the PowerShell files to install and uninstall the application directly to the Intune portal.
So, when we previously only had the option to add a command line to install and uninstall an application, we now have a drop-down menu to select an (un)installer-type and select a custom script.
We can select our PowerShell script, like we already could for a detection script.
And we can now choose to enforce a script signature check and choose to run the script as a 32-bit process on 64-bit clients.
It’s as easy as that!
And as said, we can now just change the existing script, directly in the Intune portal, without rewrapping the source files and uploading the intunewin file. No, we can just select the new version of our PowerShell script and upload it directly to Intune. Finally!
That’s already it for this short post. Just a small new Intune feature, but one that makes our lives a bit easier 😊
Note: There is currently a UI issue.
When you create a new Win32 application in Intune, the dropdown menu is greyed out. At a character in the command line text box and the dropdown menu will be available.







1 Comment
Hi, thanks for this post !
When using this powersehll script, can we use path like “.\my_exe_file.exe” inside the script when the exe file is present at the root of the sources of the package ?
Thank you !