/Add-ProvisionedAppxPackage /FolderPath: /SkipLicense /CustomDataPath: /Add-ProvisionedAppxPackage /PackagePath: /DependencyPackagePath: ...

/Add-ProvisionedAppxPackage /FolderPath: [/SkipLicense] 
/Add-ProvisionedAppxPackage /PackagePath: 
  {[/LicensePath:] | [/SkipLicense]} 

  Adds one or more packages to the image. 

  Use /FolderPath to specify a folder of unpacked package files containing 
  a main app package (.appx), any dependency packages, and the license file, 
  or use /PackagePath to specify an .appx or .appxbundle file. You can use 
  /PackagePath when provisioning a line-of-business app online. 

  If the package has dependencies that are architecture-specific, you must 
  install all of the applicable architectures for the dependency on the target 
  image. For example, on an x64 target image, include a path to both the x86 
  and x64 dependency packages. When using the /FolderPath option you can also 
  include them both in the AppX_folder_path. 
  Use /CustomDataPath to specify the OEM custom data for the application. 
  Use /LicensePath with the /PackagePath option to specify the location of the 
  .xml file containing your application license. 

  Only use /SkipLicense with apps that do not require a license on a 
  sideloading-enabled computer. Using /SkipLicense in other 
  scenarios can compromise an image. 

      DISM.exe /Image:C:\test\offline /Add-ProvisionedAppxPackage 

      DISM.exe /Image:C:\test\offline /Add-ProvisionedAppxPackage 

      DISM.exe /Online /Add-ProvisionedAppxPackage 

      DISM.exe /Image:C:\test\offline /Add-ProvisionedAppxPackage 

English (United States)
Deutsch (Deutschland)
German (Germany)
Français (France)
French (France)