Maintain an Image Using a Configuration Set and DISM (Standard 8)

  • Article

7/8/2014

Learn how to maintain your Windows Embedded 8 Standard (Standard 8) image by using a configuration set and Deployment Image Servicing and Management (DISM).

There is more than one method that you can use to apply modules, CBS packages, and updates to Windows Embedded 8 Standard (Standard 8) images. However, the following procedure is the most efficient method, in addition to being the least vulnerable to user errors.

To apply modules, CBS packages, and updates to Standard 8 images, create a configuration set and resolve dependencies in Image Configuration Editor (ICE). You will then apply that configuration set by using Deployment Image Servicing and Management (DISM).

Note

DISM can only install modules and CBS packages; it cannot copy files referenced with path settings. If you require this copy functionality, you must use Image Builder Wizard (IBW).

Prerequisites

  • You have access to either a device currently running Standard 8 or to a Windows image (.wim) file that contains the Standard 8 image that you want to update.
  • You have created a validated configuration set using ICE.
    If you are deploying or redeploying feature sets, you must redeploy the appropriate languages for your image to satisfy dependencies. This is true even if you are not adding new languages to your image. Failure to do this can create an image that does not function correctly.
  • You have installed Windows Embedded 8 Standard Toolkit (Standard 8 Toolkit) on a development computer.
    The Standard 8 setup process performs several verifications, which rely on the target device's date and time settings. For optimal performance, confirm that the target device is set to the correct date and time.

To apply a configuration set to an offline image with DISM

  1. Create a directory on your development computer and mount your image to that directory by typing the following at a command prompt.

    MD C:\MyDir\Mount
DISM /Mount-Image /ImageFile:E:\images/myimage.wim /Index:1 /MountDir:C:\MyDir\Mount

  2. Apply the Autounattend.xml file created with your configuration set by typing the following at a command prompt, replacing <file_path> with the full path of your Autounattend.xml.

    DISM /Image:C:\MyDir\Mount /Apply-Unattend:<file_path>

  3. To verify that the Autounattend.xml file was applied:

    • To verify CBS packages were added to the image type the following at a command prompt.

      DISM /Image:C:\MyDir\Mount /Get-Packages

      The /Get-Packages command lists the corresponding .cab packages rather than return a list of .msu packages.

    • To verify modules were added to the image, type the following at a command prompt.

      DISM /Image:C:\MyDir\Mount /Get-Modules

  4. Unmount the image and commit your changes by typing the following at a command prompt.

    DISM /Unmount-Image /MountDir:C:\MyDir\Mount /Commit

Your offline image is now updated with the contents of your configuration set.

To apply a configuration set to a device with DISM

  1. Apply the Autounattend.xml file created with your configuration set by typing the following at a command prompt on your device, replacing <file_path> with the full path of the configuration set.

    DISM /Online /Apply-Unattend:<file_path>

  2. To verify that the Autounattend.xml file was applied:

    • To verify CBS packages were added to the image, type the following at a command prompt.

      DISM /Online /Get-Packages

      The /Get-Packages command lists the corresponding .cab packages rather than return a list of .msu packages.

    • To verify modules were added to the image, type the following at a command prompt.

      DISM /Online /Get-Modules

    Your device is now updated with the contents of your configuration set.

Troubleshooting

If you receive the error message Error 3: The system cannot find the path specified, then the ConfigSetRoot environment variable is overriding the command-line variable in DISM. This error message occurs when you perform an online installation, and occurs most often when you are installing from the original Standard 7 disk using the Create IBW disk from an Answer File option in Image Configuration Editor.

To fix this issue, remove the value of the environment variable ConfigSetRoot on the target device, and then repeat the procedure.

See Also

Concepts

Catalogs

Other Resources

Add Updates to an Image
Deployment Image Servicing and Management (DISM) Technical Reference