How to Force a Store App to Install for All Users on Windows 11

When you install an app from the Microsoft Store on Windows 11, it typically installs only for your user account. Other users on the same PC must install the app themselves, which wastes time and can cause confusion. This happens because Store apps use per-user deployment by default, even when you are an administrator. This article explains how to force a Store app to install for all users on a Windows 11 device using built-in tools and PowerShell commands.

Understanding App Provisioning on Windows 11

Windows 11 separates app installation into two categories: per-user and per-machine. Per-user apps are stored in the user’s profile folder and are not accessible to other accounts. Per-machine apps, also called provisioned apps, are stored in the system drive and are available to all users. The Microsoft Store installs apps as per-user by default, even when you run the Store as an administrator. This design prevents one user’s app from affecting another user’s system stability.

To install a Store app for all users, you must use the provisioning feature built into Windows 11. Provisioning registers the app package in the system image so that Windows automatically installs it for each user at sign-in. This method works for both new users who have never signed in and existing users who already have a profile. The provisioning process requires the app’s package name and root directory. You can obtain these from the Microsoft Store or from a downloaded .appxbundle file.

Prerequisites for Provisioning a Store App

Before you start, ensure the following conditions are met:

• You are signed in with an account that has local administrator privileges.
• The target app is a Store app that supports provisioning. Some apps, such as those that rely on per-user licensing or user-specific data, may not work correctly when provisioned.
• You have the app’s package name or the .appxbundle file. You can download the .appxbundle from the Microsoft Store using a tool like the Store Web Downloader or from a volume licensing portal.
• Windows 11 is fully updated to the latest version. Provisioning commands may behave differently on older builds.

Steps to Provision a Store App for All Users Using PowerShell

PowerShell provides the most direct method to provision a Store app. Follow these steps carefully.

1. Open PowerShell as Administrator
   Right-click the Start button and select Terminal Admin or Windows PowerShell Admin. Click Yes in the User Account Control prompt.
2. Obtain the App Package Name
   If you do not already have the package name, run this command to list all installed Store apps: Get-AppxPackage | Select Name, PackageFullName. Locate the app you want to provision and copy its PackageFullName value. You will need the entire string, such as Microsoft.WindowsCalculator_10.2103.8.0_x64__8wekyb3d8bbwe.
3. Get the App Package Root Directory
   The provisioning command requires the path to the app’s root folder. Use this command to find it: (Get-AppxPackage -Name "Microsoft.WindowsCalculator").InstallLocation. Replace the name with your app’s name. The output will be something like C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_10.2103.8.0_x64__8wekyb3d8bbwe. Copy that path.
4. Provision the App for All Users
   Run the following command: Add-AppxProvisionedPackage -Online -PackagePath "C:\path\to\app\root\directory" -SkipLicense. Replace the path with the one you copied from the previous step. The -SkipLicense parameter bypasses any license checks that might block provisioning. If the app requires a license file, you must include the -LicensePath parameter pointing to the .xml license file.
5. Verify the Provisioning
   Run Get-AppxProvisionedPackage -Online to confirm the app appears in the list. The DisplayName column should show your app. If you see an error, ensure the path is correct and that you have not exceeded the WindowsApps folder permissions.

Steps to Provision a Store App Using DISM

DISM is another built-in tool that can provision apps. It is useful when you need to add the app to a Windows image for deployment or when PowerShell is not available.

1. Open Command Prompt as Administrator
   Press Win + R, type cmd, then press Ctrl + Shift + Enter. Click Yes in the UAC prompt.
2. Navigate to the App Package Location
   Use the cd command to change to the directory where the .appxbundle file is stored. For example: cd "C:\Users\YourName\Downloads".
3. Run the DISM Provisioning Command
   Type: DISM /Online /Add-ProvisionedAppxPackage /PackagePath:"MyApp.appxbundle" /SkipLicense. Replace MyApp.appxbundle with the actual file name. If you have a dependency package, include it with the /DependencyPackagePath parameter.
4. Wait for Completion
   The operation may take several minutes. When you see the message “The operation completed successfully,” you can close the command prompt.

Common Issues When Provisioning Store Apps

“Access Denied” Error When Accessing the WindowsApps Folder

The WindowsApps folder is protected by Windows. Even administrators cannot browse it directly without taking ownership. To avoid this error, run PowerShell or Command Prompt as Administrator before attempting any operations on that folder. Do not change the folder permissions manually, as this can break other Store apps.

App Does Not Appear for Other Users After Provisioning

The provisioning command registers the app for future logins. Existing users must sign out and sign back in to see the app. If the app still does not appear, check that the app supports provisioning. Some apps, like Spotify or Netflix, use per-user licensing and may not function correctly when provisioned. In that case, each user must install the app from the Store individually.

Provisioned App Fails to Update

Provisioned apps update automatically through the Microsoft Store, but updates may fail if the app package is corrupted or if the user lacks write permissions to the app directory. To fix this, uninstall the app from all users using Remove-AppxProvisionedPackage -Online -PackageName "FullPackageName" and then re-provision it with the updated version.

Item	PowerShell Method	DISM Method
Command used	Add-AppxProvisionedPackage	DISM /Add-ProvisionedAppxPackage
Requires .appxbundle file	No, works with installed app directory	Yes, requires file path
Supports offline image	No, only online system	Yes, can target mounted images
License handling	Use -SkipLicense or -LicensePath	Use /SkipLicense or /LicensePath
Best for	Quick provisioning on a single PC	Deployment imaging (SCCM, MDT)

You can now force a Store app to install for all users on Windows 11 using either PowerShell or DISM. Start by provisioning a test app like Windows Calculator to confirm the process works on your device. For enterprise environments, consider using Microsoft Intune or Group Policy to deploy provisioned apps at scale. As an advanced tip, use the Add-AppxProvisionedPackage -LogPath C:\Logs\provision.log parameter to generate a detailed log if the command fails, which helps identify missing dependencies or permission issues.