PowerShell Logo Small


This is the built-in help made by Microsoft for the command 'Add-ProvisionedAppxPackage', in PowerShell version 5 - as retrieved from Windows version 'Microsoft Windows Server 2012 R2 Standard' PowerShell help files on 2016-06-23.

For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.


Adds an app package (.appx) that will install for each new user to a Windows image.


Add-AppxProvisionedPackage [-CustomDataPath <String>] [-DependencyPackagePath <String[]>] [-FolderPath <String>] [-LicensePath <String>] [-LogLevel <LogLevel>] [-LogPath
<String>] [-PackagePath <String>] [-ScratchDirectory <String>] [-SkipLicense] [-SystemDrive <String>] [-WindowsDirectory <String>] -Online [<CommonParameters>]
Add-AppxProvisionedPackage [-CustomDataPath <String>] [-DependencyPackagePath <String[]>] [-FolderPath <String>] [-LicensePath <String>] [-LogLevel <LogLevel>] [-LogPath
<String>] [-PackagePath <String>] [-ScratchDirectory <String>] [-SkipLicense] [-SystemDrive <String>] [-WindowsDirectory <String>] -Path <String> [<CommonParameters>]

Search powershellhelp.space


The Add-AppxProvisionedPackage cmdlet adds an app package (.appx) that will install for each new user to a Windows image. If the package has dependencies that are
architecture-specific, you must install the applicable architectures for the dependency on the target image. For example, you must install the x86 dependency on the x86

You cannot install an app package (.appx) on an operating system that does not support Windows® 8 apps. Apps are not supported on Server Core installations of Windows
Server® 2012, Windows® Preinstallation Environment (Windows PE) 4.0, or on any versions of Windows older than Windows 8 and Windows Server 2012.

To install and run apps on Windows Server 2012, you must install the Desktop Experience.

Use the Online parameter to specify the running operating system on your local computer, or use the Path parameter to specify the location of a mounted Windows image.

Use the PackagePath, DependencyPackagePath, and LicensePath parameters to specify the location of all the files that are needed to add the provisioned app package (.appx).
Use these parameters to provision line-of-business apps.

Use the FolderPath parameter to specify the location of a folder of unpacked app package (.appx) files that includes any dependency packages and a license file.

To add an app package (.appx) for a particular user, or to test a package while developing your app, use the Add-AppxPackage cmdlet instead.

For more information, including requirements for app package provisioning, see How to Add and Remove Apps and How to develop an OEM app that uses a custom file (Windows).



Online Version: http://go.microsoft.com/fwlink/p/?linkid=289347




Example 1

PS C:\>Add-AppxProvisionedPackage -Online –FolderPath c:\Appx

This command adds the app package, dependency packages, and license file from the c:\Appx folder to the running Windows operating system. The package will be installed for
the current user and any new user account created on the computer.

Example 2

PS C:\>Add-AppxProvisionedPackage –Path c:\offline –PackagePath c:\Appx\myPackage.appx –DependencyPath c:\Appx\dependency1\dependencyPackage.appx –LicensePath

This command adds the app package, myPackage.appx, to the Windows image mounted to c:\offline.