MSIX packages must be digitally signed. For all-users installation, the certificate must be trusted at the machine level, not just the user level.
Get-AppxPackage -Name "YourAppPackageName" | Remove-AppxPackage -AllUsers
Before you run the commands, ensure you have: install msix powershell all users
The standard cmdlet Add-AppxPackage does not have a dedicated -AllUsers parameter in older PowerShell versions, but it achieves the same result if you run the command provisioning the package. MSIX packages must be digitally signed
To install for all users (current and future users), you must use the -RequiredContentGroupOnly or strictly specify the package path. Before you run the commands, ensure you have:
The Command:
Add-AppxPackage -Path "C:\Path\To\YourApp.msix"
Wait, how does that install for All Users?
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.
Add-AppxProvisionedPackage -Online -PackagePath "C:\path\to\your\file.msix" -SkipLicense
Get-AppxPackage -Name "*YourAppName*" -AllUsers