Share via

Add a Package to a Windows PE Image

Applies To: Windows 7, Windows Server 2008 R2


This content applies to Windows 7. For Windows 8 content, see Windows Deployment with the Windows ADK.

This topic procedure demonstrates how to use Deployment Image Servicing and Management (DISM) to add packages to a Windows® Preinstallation Environment (Windows PE). image offline.

Windows PE 3.0 provides the following packages that you can add to your base image. You must add them to your image by using the DISM command with the /Add-package option.

Package Name Description


Additional font support for the following languages: ja-JP, ko-KR, zh-CN, zh-HK, and zh-TW.


HTML Application support. Enables the creation of GUI applications using the Internet Explorer script engine and HTML services.


The Media Setup feature package. All Setup files from the \Sources folder on the Windows media. Add this package when servicing Setup or the \Sources folder on the Windows media. Must be added with the Setup feature package. To add a new Boot.wim to the media, add either child package in addition to the Setup and Media packages. This package is required to support Windows Server® 2008 R2 installation.


Microsoft® Data Access Component support. Enables queries to SQL servers with Active Directory Objects (ADO). Example usage: building a dynamic Unattend from unique system information.


Enables Point-to-Point Protocol over Ethernet (PPPoE) support. Create, connect, disconnect and delete PPPoE connections from Windows PE.


Windows Script Host (WSH) support. Enables batch file processing using WSH script objects.


The Setup feature package (parent). All Setup files from the \Sources folder common to Client and Server.


The Client Setup feature package (child). The Client branding files for Setup. Must be added after the Setup feature package.


The Server Setup feature package (child). The Server branding files for Setup. Must be added after the Setup feature package.


The Windows Recovery Environment feature package. Provides a recovery platform for automatic system diagnosis and repair and the creation of custom recovery solutions.


Windows Management Instrumentation (WMI) support. A subset of the WMI providers that enables minimal system diagnostics.


The Windows Deployment Services tools feature package. Includes APIs to enable a multicast scenario with a custom Windows Deployment Services client and Image Capture utility.


  • The base Windows PE image does not contain all the packages listed above. You must use the DISM tool to install the appropriate packages. The packages are located in the directory \Windows OPK\Tools\PETools\_architecture or \Windows AIK\Tools\PETools\_architecture. For your optional components to work correctly, make sure the required language resources are installed on the client computer. The language resources are located in a folder named the same as the language installed in the directory listed above.

  • The winpe-xml package is now included in the base boot.wim.

  • The Windows PE-setup-package is the parent package of winpe-setup-client and winpe-setup-server. You must install winpe-setup before you install the child packages.

    For an example of how to build custom Windows PE images, see Windows PE Walkthroughs.

    To add a package to a Windows PE image offline

    1. Use the DISM tool to mount the base image to a local Windows PE directory. For example:

      Dism /Mount-WIM /WimFile:c:\winpe_x86\winpe.wim /index:1 /MountDir:c:\winpe_x86\mount
    2. Add a Windows feature to the base image by using the DISM command with the /Add-Package option. For example:

      dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\"
      dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\en-us\"

      Where <version> can be the OEM Preinstallation Kit (OPK) or the Automated Installation Kit (AIK).


    When adding packages, you must include both the language-neutral package and the language-specific package, as illustrated in the previous example.

    A list of installed packages can be obtained by using the **/GetPackages** option.  
    1. Repeat Step 1 for each package you want to install in the base image.

    2. Verify that the packages were installed by using the DISM command with the /GetPackages option to view all packages in the current image. For example,

      dism /image:c:\winpe_x86\mount /Get-Packages

    After the image is prepared, you can burn the image to media.


    If you choose to remove a package using DISM /Remove-Package, the functionality of the package will be remove from your Windows PE image, but the source file will still persist in the image. The size of your image will remain the same. To remove the file from the image, you must create a new image.

    For more information about managing packages, see Operating System Package Servicing Command-Line Options.

    See Also


    Deployment Image Servicing and Management Command-Line Options