To install an MSIX package for all users on a Windows machine, you must the package using an elevated PowerShell session
. While standard MSIX installs are user-scoped, provisioning stages the application so it is automatically registered for every user who logs in. Primary Command for All Users Add-AppxProvisionedPackage
cmdlet (part of the DISM module) to install for all current and future users. powershell Add-AppxProvisionedPackage -Online -PackagePath "C:\Path\To\YourApp.msix" -SkipLicense Use code with caution. Copied to clipboard : Targets the currently running operating system. -PackagePath : Specifies the local path to the MSIX or MSIXbundle file. -SkipLicense
: Bypasses the need for an XML license file, which is usually required for Store-sourced apps but not for most sideloaded apps. Super User Important Prerequisites Administrator Rights : You must run PowerShell as an Administrator for these commands to work. Trusted Certificate
: The MSIX package must be signed. If it is a sideloaded app, the signing certificate must be installed in the machine's Trusted People store before installation. Dependencies install msix powershell all users
: If the app requires external frameworks (like VCLibs), you must provide them using the -DependencyPackagePath parameter. AVEVA™ Documentation Verification and Management Check Installation : To see all provisioned (all-user) packages, use: Get-AppxProvisionedPackage -Online Remove for All Users
: To uninstall the package so it no longer appears for new users:
Remove-AppxProvisionedPackage -Online -PackageName "YourPackageFullName" Check Current User Status : To see if it successfully registered for the Get-AppxPackage -Name "YourAppName" Advanced Installer
For more advanced deployment scenarios, Microsoft's official documentation on Managing MSIX with PowerShell or guides from Advanced Installer provide detailed parameter lists and troubleshooting tips. PowerShell script To install an MSIX package for all users
that automatically handles the certificate installation and dependencies along with the app?
MSIX PowerShell Cmdlets - Install MSIX files and MSIXBundles
This paper provides a comprehensive guide and technical analysis for IT professionals and system administrators on installing MSIX packages for all users using PowerShell. It covers the evolution of the technology, the specific cmdlets required, the critical dependencies, and a robust, scriptable solution.
Add-AppxProvisionedPackage -Online `
-PackagePath "C:\installers\MyApp.msix" `
-LicensePath "C:\installers\license.xml" `
-SkipLicense
-Online → installs to the running Windows image (local machine)-SkipLicense → bypasses license acceptance prompts (use only if legally allowed)-LicensePath → optional, for paid apps requiring a license fileTo install an MSIX package for all users, you need to use the -AllUsers parameter with Add-AppxPackage. Here's how: -Online → installs to the running Windows image
Add-AppxPackage -AllUsers -Path "C:\Path\To\YourApp.msix"
This command requires administrative privileges to execute.
-ForceApplicationShutdown SwitchIn enterprise environments, users often leave applications open. By default, MSIX installation will fail if the app is currently running (specifically during an update scenario, but good practice to include for fresh installs if the process is hanging). This switch ensures the installer can proceed by terminating active processes belonging to the package family.
Remove-Item -Recurse -Force $tempFolder
Microsoft provides a dedicated PowerShell module for managing MSIX specifically. This is useful if you are creating or modifying packages, but it also simplifies installation tasks.
Install-Module -Name MSIX -Force
Add-MSIXPackage -Path "C:\Path\To\YourApp.msix"
Note: This module generally wraps standard cmdlets but provides cleaner output and error handling.