Service an Applied Windows Image
Updated: October 20, 2013
Applies To: Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
Windows® image (.wim) files contain one or more volume images for a Windows® operating system. A volume image represents the captured volume or partition of a Windows operating system. If you have to re-capture a Windows image, or export a copy of a specific .wim file to another .wim file, or append a volume image to an existing .wim file, you can use the Deployment Image Servicing and Management (DISM) tool to apply the image, and then service the image when it is applied. Then you can boot to audit mode to resolve pending online actions, and add applications or make additional customizations.
To complete the walkthrough, you need the following:
A computer that has the latest version of the Windows Assessment and Deployment Kit (Windows ADK) tools installed on it.
Before you can apply a Windows image to a hard disk drive partition, you must create the hard disk partitions on the destination computer. For more information, see Hard Drives and Partitions.
You must have the master Windows image (.wim file) and the language packs, drivers, or other packages available in an available location to add them to the Windows image.
A bootable Windows PE disk. For more information, see WinPE: Create USB Bootable drive You can also apply the image from another operating system on the same computer, such as Windows® 8 or Windows® 7 with the latest ADK tools installed.
In this step, you boot to Windows PE and apply a Windows image so that it can be serviced offline.
On the destination computer, boot to Windows PE. For more information, see WinPE for Windows 8: Windows PE 5.0.
At a command prompt, apply the master Windows image using DISM. For example:
Dism /Apply-Image /ImageFile:C:\test\wim\install.wim /Index:1 /ApplyDir:C:\test\AppliedImages
For more information about DISM commands, see DISM Image Management Command-Line Options.
Use DISM to add packages to your master Windows image.
At a command prompt, run DISM with the /Add-Package option and point to the .cab or .msu package that you want to add to the Windows image. Multiple packages can be added on one command line. For example, type the following command to add multiple packages:
Dism /Image:C:\test\AppliedImages /Add-Package /PackagePath:C:\Test\Packages\package1.cab /PackagePath:C:\Test\Packages\package2.cab
For more information about these DISM command-line options, see DISM Operating System Package Servicing Command-Line Options.
You can also use DISM command-line options on an applied Windows image to add drivers, add language packs, change to a higher edition of Windows, or apply an unattended answer file. For more information, see:
Check the log file to verify that the package was successfully added.
Some packages and drivers that were added or removed could be in a pending state. This is usually because a restart is required to complete the action. Booting the image to audit mode will satisfy the restart requirement, and let you add applications and make additional customizations. For more information, see Boot Windows to Audit Mode or OOBE.
This walkthrough illustrates basic offline servicing of an applied Windows image in Windows PE. When you complete this process, the packages are added to the Windows image. You can now either run
sysprep /generalize /oobe to remove machine-specific customizations and recapture the image for later deployment, or run
sysprep /oobe to keep the specialized customizations and ship this computer. Using the
/oobe option will ensure that the computer starts in Out-of-Box Experience (OOBE) mode the next time that it is booted. For more information, see Sysprep (System Preparation) Overview.