The core cmdlet for installation is Add-AppxPackage . However, for "All Users" deployment, the approach differs based on the Windows version.
# Define the path to the MSIX file $PackagePath = "C:\Path\To\YourApp.msix" # 1. Provision the package for all future user logins Add-AppxProvisionedPackage -Online -PackagePath $PackagePath -SkipLicense # 2. Extract the package full name from the MSIX file to register it for current users $PackageManifest = Get-AppxPackageManifest -PackagePath $PackagePath $PackageName = $PackageManifest.Package.Identity.Name # 3. Register the package for all currently existing profiles on the machine Get-AppxPackage -AllUsers -Name $PackageName | Foreach Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" Use code with caution. How to Verify the Installation
Let's break down the parameters:
# Install for current user (administrator session) Add-AppxPackage -Path $msix -ForceApplicationShutdown
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser install msix powershell all users
If you are developing or testing an application that has not been signed, you'll need a different approach. For unsigned MSIX packages intended for system-wide installation, you must use the Add-AppxPackage cmdlet with the flag, and it still must be run from an elevated PowerShell session.
: Prevents errors (like 0xc1570104 ) if you do not have a separate XML license file, which is common for sideloaded apps. Alternative: DISM (Command Prompt) The core cmdlet for installation is Add-AppxPackage
Get-AppxPackage -AllUsers -Name "PackageFullName" | Foreach Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" Use code with caution.
Whether you are an IT pro managing multiple devices or a developer testing a package, this guide will walk you through the process step-by-step. Provision the package for all future user logins