Adds an app package (.appx) that will install for each new user to a Windows image.
PowerShell · Risk: High · Documentation Verified
Last verified: 2026-10-26
Microsoft Dism reference: Adds an app package (.appx) that will install for each new user to a Windows image. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Add-AppxProvisionedPackage. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / Dism · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-CustomDataPath
Specifies the location of a custom data file. The custom data file will be renamed custom.data and saved in the app data store.
-DependencyPackagePath
Specifies the location of a dependency package.
-FolderPath
Specifies a folder of unpacked app package files containing a main package and any dependency packages. This folder must also contain your application license.
-LicensePath
Specifies the location of the .xml file containing your application license.
-LogLevel
Specifies the maximum output level shown in the logs.
-LogPath
Specifies the full path and file name to log to. If not set, the default is %WINDIR%\Logs\Dism\dism.log. In Windows PE, the default directory is the RAMDISK scratch space which can be as low as 32 MB. The log file will automatically be archived. The archived log file will be saved with .bak appended to the file name and a new log file will be generated. Each time the log file is archived the .bak file will be overwritten. When using a network share that is not joined to a domain, use the net use command together with domain credentials to set access permissions before you set the log path for the DISM log.
-Online (required)
Specifies that the action is to be taken on the operating system that is currently running on the local computer.
-OptionalPackagePath
Specifies the path to an optional package that will also be provisioned. For more information on optional packages, see Optional packages and related set authoring.
-PackagePath
Specifies the location of the app package (.appx) to add to the Windows image. This package will be added for every new user account. 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. The *PackagePath* parameter is only supported for offline servicing when the technician computer is running a version of Windows that supports Windows 8 apps.
-Path (required)
Specifies the full path to the root directory of the offline Windows image that you will service. If the directory named Windows is not a subdirectory of the root directory, *WindowsDirectory* must be specified.
-Regions
Specifies what regions an app package (.appx or .appxbundle) must be provisioned in. The region argument can either be "all", indicating that the app should be provisioned for all regions, or it can be a semi-colon delimited list of regions. The regions will be in the form of ISO 3166-1 Alpha-2 or ISO 3166-1 Alpha-3 codes. For example, the United States can be specified as either "US" or "USA" (case-insensitive). When a list of regions is not specified, the package will be provisioned only if it is pinned to start layout. Note: Option is available on client OS.
-ScratchDirectory
Specifies a temporary directory that will be used when extracting files for use during servicing. The directory must exist locally. If not specified, the \Windows\%Temp% directory will be used, with a subdirectory name of a randomly generated hexadecimal value for each run of DISM. Items in the scratch directory are deleted after each operation. You should not use a network share location as a scratch directory to expand a package (.cab or .msu file) for installation. The directory used for extracting files for temporary usage during servicing should be a local directory.
-SkipLicense
Adds an app package without a license file. Only use *SkipLicense* with apps that do not require a license on Enterprise or Server versions of the operating system. Using *SkipLicense* in other scenarios can compromise an image.
-StubPackageOption
Specifies the stub preference of the package. If no stub package option is specified then the provisioned package version is set to the predefined stub preferences.
-SystemDrive
Specifies the path to the location of the BootMgr files. This is necessary only when the BootMgr files are located on a partition other than the one that you are running the command from. Use -SystemDrive to service an installed Windows image from a Windows PE environment.
-WindowsDirectory
Specifies the path to the Windows directory relative to the image path. This cannot be the full path to the Windows directory; it should be a relative path. If not specified, the default is the Windows directory in the root of the offline image directory.
Prerequisites
Windows with the Dism module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
Security considerations
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.
Examples
Example 1: Add an app package to the running operating system
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. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.