You do not always need to manually write these PowerShell scripts.
In modern Windows versions (1809+), simply running Add-AppxPackage as Administrator stages the package. However, to ensure it is provisioned (available for future users), you should use the Add-AppxProvisionedPackage cmdlet (see Method 2 below), which is the technically correct way for "All Users" deployment.
# Install the MSIX package for all users Add-AppxPackage -AllUsers -Path $msixPath install msix powershell all users
I can provide a tailored script format or an automated wrapper to suit those needs.
In modern Windows builds (Windows 10 1709+), Add-AppxPackage supports the -AllUsers parameter. This command attempts to stage the package for all users on the machine. You do not always need to manually write
: The absolute local or network path to your .msix or .appx file.
: Tells the cmdlet to act on the current operating system. -PackagePath : The absolute path to your .msix file. # Install the MSIX package for all users
Ensure Developer Mode or Sideloading is enabled under Settings > Update & Security > For developers (on Windows 10) or Settings > System > For developers (on Windows 11). Ensure the signing certificate is installed to the Local Machine -> Trusted People certificate store.
Traditionally, administrators used Add-AppxProvisionedPackage . This stages the app in the system image so that it is installed for every new user profile created.
Add-AppxPackage -Path "C:\Path\To\YourApp.msix"