To install an MSIX package for all users on a Windows machine, you must use provisioning cmdlets rather than standard installation commands . While Add-AppxPackage only installs an app for the current user, provisioning ensures the application is registered for every existing and future user profile on the device. The Core Command: Add-AppxProvisionedPackage The primary way to handle a machine-wide installation via PowerShell is through the Add-AppxProvisionedPackage cmdlet. Standard Syntax: powershell Add-AppxProvisionedPackage -Online -PackagePath "C:\Path\To\YourApp.msix" -SkipLicense Use code with caution. -Online : Specifies that the action applies to the currently running operating system. -PackagePath : The full path to your .msix or .msixbundle file. -SkipLicense : Required unless you have a specific XML license file; it prevents errors during the provisioning process. Why "All Users" Installation is Different Unlike traditional .msi installers that often have a "per-machine" flag, MSIX is fundamentally user-centric. User-Level ( Add-AppxPackage ) : Installs the app only for the person running the command. If another user logs in, they won't see the app. Provisioning ( Add-AppxProvisionedPackage ) : Stages the app at the system level. Windows then "installs" it for each user the next time they sign in. AVEVA™ Documentationhttps://docs.aveva.com Silent Install with MSIX - AVEVA™ Documentation
To install an MSIX package for all users via PowerShell, the package at the system level . Standard installation commands like Add-AppPackage only install the app for the current user. Recommended Method: Machine-Wide Provisioning Provisioning ensures the application is available for all current and future users who sign in to the device. Microsoft Community Hub Open PowerShell as Administrator. Run the following command: 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 full path to your .msixbundle -SkipLicense : Used if you do not have a specific XML license file (common for sideloaded apps). Super User Alternative: Using DISM can also be used from a command prompt or PowerShell for the same effect: Super User powershell Dism /Online /Add-ProvisionedAppxPackage /PackagePath: "C:\Path\To\YourApp.msix" /SkipLicense Use code with caution. Copied to clipboard How it Works Registration : Once provisioned, the app is automatically "registered" (installed) for every new user the first time they sign in. Existing Users : For users already signed in, the app typically appears immediately without requiring a logout. Installation Path : The app files are stored in the protected %ProgramFiles%\WindowsApps directory. Microsoft Learn Removing a Machine-Wide Package To completely remove a provisioned app for everyone, you must deprovision it and then remove it for existing users: Deprovision for all users powershell Remove-AppxProvisionedPackage -Online -PackageName "PackageFullName" Use code with caution. Copied to clipboard Remove for existing users (optional, if they have already registered it): powershell Remove-AppxPackage -AllUsers -Package "PackageFullName" Use code with caution. Copied to clipboard for a popular app, or do you need help extracting the full name of an installed MSIX? Installing Python install manager MSIX for all users · Issue #119
To install an MSIX package for all users via PowerShell, you must "provision" the package to the Windows image rather than just registering it for the current user. This process makes the application available to all existing users and ensures it automatically installs for any new users when they first sign in. Primary Command: Add-AppxProvisionedPackage The most effective way to accomplish a machine-wide installation is using the Add-AppxProvisionedPackage cmdlet from the DISM module . You must run PowerShell with Administrator privileges to execute this. powershell Add-AppxProvisionedPackage -Online -PackagePath "C:\Path\To\YourApp.msix" -SkipLicense Use code with caution. Copied to clipboard -Online: Specifies that the action applies to the currently running operating system. -PackagePath: The full path to your .msix or .msixbundle file. -SkipLicense: Used when you do not have a specific XML license file; it prevents errors during the provisioning process. Key Differences: Provisioning vs. Registration Understanding the difference between these two PowerShell commands is critical for "all users" deployments: Machine-wide Package Provisioning (Install for All Users)
To install an MSIX package for all users via PowerShell, you must provision the application at the system level. Standard installation cmdlets like Add-AppxPackage are user-scoped and only install the app for the current user. Feature Overview: Machine-Wide MSIX Provisioning Provisioning an MSIX package stages the application in the system image, making it available for every current and future user on the device. 1. Core PowerShell Cmdlet The primary command for machine-wide installation is Add-AppxProvisionedPackage . This requires administrative privileges. Command Syntax: powershell Add-AppxProvisionedPackage -Online -PackagePath "C:\Path\To\YourApp.msix" -SkipLicense Use code with caution. Copied to clipboard -Online : Targets the currently running operating system. -PackagePath : The full path to your .msix or .msixbundle file. -SkipLicense : Prevents errors (such as 0xc1570104 ) if a specific XML license file is not provided. 2. Alternative: DISM Tool You can achieve the same result using the Deployment Image Servicing and Management ( DISM ) utility, which is often preferred for offline image management or IoT environments. Command Syntax: powershell DISM /Online /Add-ProvisionedAppxPackage /PackagePath:"C:\Path\To\YourApp.msix" /SkipLicense Use code with caution. Copied to clipboard 3. Handling Unsigned Packages If you are deploying an unsigned package for all users, you must include the -AllowUnsigned flag and run the session as an administrator. Summary Table: Per-User vs. All-Users Per-User Installation All-Users (Provisioning) Primary Cmdlet Add-AppxPackage Add-AppxProvisionedPackage Permissions Standard User (usually) Administrator Required Scope Current logged-in user only Existing and future users Registration Immediate for current user Automatic upon next sign-in Important Considerations Create an unsigned MSIX package - Microsoft Learn install msix powershell all users
To install an MSIX package for all users on a Windows machine, you must provision the package at the system level . This ensures the application is automatically registered for every user who logs in. PowerShell Command for All Users The standard way to perform this is using the Add-AppxProvisionedPackage cmdlet in an elevated (Administrator) PowerShell window: powershell Add-AppxProvisionedPackage -Online -PackagePath "C:\Path\To\YourApp.msix" -SkipLicense Use code with caution. Copied to clipboard Breakdown of Parameters: -Online : Targets the currently running operating system. -PackagePath : The full file path to your .msix or .msixbundle file. -SkipLicense : Prevents errors (like 0xc1570104 ) if you do not have a separate XML license file, which is common for sideloaded apps. Alternative: DISM (Command Prompt) You can also use the Deployment Image Servicing and Management ( DISM ) tool, which achieves the same result: dism.exe /Online /Add-ProvisionedAppxPackage /PackagePath:"C:\Path\To\YourApp.msix" /SkipLicense Use code with caution. Copied to clipboard Key Differences: Add-AppxPackage vs Add-AppxProvisionedPackage Add-AppxPackage Add-AppxProvisionedPackage Scope Current User only All Users (Machine-wide) Persistence Only for the account that ran it Auto-registers for all new & existing logins Privileges Standard User (usually) Required Administrator Note : When you provision a package, it may not appear instantly for a currently logged-in user until they restart their session or the AppX Deployment Service triggers a refresh. Unlike a typical MSI package, you cannot just add a property (like ALLUSERS=1) and install the application per machine. With MSIX, Advanced Installer
To install an MSIX package for all users on a Windows system using PowerShell, you must use the Add-AppxProvisionedPackage cmdlet. Standard installation commands like Add-AppxPackage only install the application for the current user profile. Prerequisites Administrator Privileges : You must run PowerShell as an Administrator. MSIX Package : Ensure you have the .appxbundle file path ready. Dependencies : If the package requires specific frameworks (like .NET or VCLibs), you must have those paths available as well. Step-by-Step Installation Guide 1. Open PowerShell as Administrator Right-click the button and select Windows PowerShell (Admin) Terminal (Admin) 2. Install the Package for All Users Use the following command structure. Replace the placeholder path with your actual file location: powershell Add-AppxProvisionedPackage -Online -PackagePath "C:\Path\To\YourApp.msix" -SkipLicense Use code with caution. Copied to clipboard : Applies the change to the currently running operating system. -PackagePath : The full path to your MSIX file. -SkipLicense : Used if the application does not require a specific Windows Store license file ( 3. Including Dependencies (If Required) If your MSIX package has dependencies, you must include them in the command to ensure the app functions for all users: powershell Add-AppxProvisionedPackage -Online ` -PackagePath "C:\Apps\YourApp.msix" ` -DependencyPackagePath "C:\Apps\Framework1.msix" "C:\Apps\Framework2.msix" ` -SkipLicense Use code with caution. Copied to clipboard 4. Verify the Installation To confirm the package is provisioned (meaning it will install automatically for any new or existing user logging in), run: powershell Get-AppxProvisionedPackage -Online | Where-Object {$_.DisplayName -like "*YourAppName*" Use code with caution. Copied to clipboard Key Differences to Remember Add-AppxPackage : Installs for the current user only . Even if run as Admin, it stays within that specific profile. Add-AppxProvisionedPackage : Adds the app to the Windows image. It will be "staged" and installed for every user upon their next sign-in.
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 : 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 that automatically handles the certificate installation and dependencies along with the app? MSIX PowerShell Cmdlets - Install MSIX files and MSIXBundles To install an MSIX package for all users
How to Install an MSIX Package for All Users with PowerShell This article shows a reliable method to install an MSIX package so all users on a machine can use the app. It covers prerequisites, package signing, the command to register or install for all users, handling dependencies, and troubleshooting. Key points
MSIX is the modern app package format for Windows; by default installations can be per-user. To make an MSIX available to all users you typically install it per-machine using the App Installer service or by registering it in the system package repository. Installing for all users requires administrator privileges and a signed package (or developer mode enabled).
Prerequisites
Windows 10/11 with MSIX support. Administrative account or elevated PowerShell session. MSIX package (.msix or .appx) and any dependency packages. Package certificate if the package is signed with a private CA; the certificate must be trusted by the machine.
Prepare certificate (if needed)