DISM Overview

What's New in DISM

DISM in Windows 10 supports new features:

  • Full Flash Update (.FFU): DISM supports the Full Flash Update (.FFU) format, which captures an applies an entire drive, including partition information. This can make deployment faster and easier. See Windows full flash update images for more info.

  • Capabilities: This new Windows package type allows you to request services like .NET or languages without specifying the version. Use DISM to search multiple sources like Windows Update or your corporate servers to find and install the latest version. For more info, see Features on Demand.

  • Compress operating system and provisioning packages: Save space on a Windows image by running the operating system and other system files from compressed files. This replaces the WIMBoot features from Windows 8.1. See /Apply-Image /Compact and /Apply-CustomDataImage in DISM Image Management Command-Line Options for more info.

What is DISM?

Deployment Image Servicing and Management (DISM.exe) is a command-line tool that can be used to service and prepare Windows images, including those used for Windows PE, Windows Recovery Environment (Windows RE) and Windows Setup. DISM can be used to service a Windows image (.wim) or a virtual hard disk (.vhd or .vhdx).

DISM comes built into Windows and is available through the command line or from Windows PowerShell. To learn more about using DISM with PowerShell, see Deployment Imaging Servicing Management (DISM) Cmdlets in Windows PowerShell.

Image Requirements

DISM can be used to mount and service a Windows image from a .wim file, .ffu file, .vhd file, or a .vhdx file and also to update a running operating system. It can be used with older Windows image files (.wim files). However, it cannot be used with Windows images that are more recent than the installed version of DISM.

For a complete technical description of WIM, see the Windows Imaging File Format (WIM) white paper.

DISM can be used to service Windows images starting with Windows 7, Windows Server 2008 R2, and their associated versions of WinPE and WinRE. The commands and options that are available for servicing an image depend on which Windows operating system you are servicing, and whether the image is offline or a currently running operating system.

For a list of the supported platforms and architecture types, see DISM Supported Platforms.

Common Servicing and Management Scenarios

Image servicing and management solutions fall into two main categories:

  • Managing the data or information included in the Windows image, such as enumerating or taking an inventory of the components, updates, drivers, or applications that are contained in an image, capturing or splitting an image, appending or deleting images within a .wim file, or mounting an image.
  • Servicing the image itself, including adding or removing driver packages and drivers, modifying language settings, enabling or disabling Windows features, and upgrading to a higher edition of Windows.

Limitations

Version compatibility. DISM can be used with target images of older Windows operating systems, but not with target images of operating systems that are more recent than the installed version of DISM. For example, DISM from Windows 10, version 1511 can service Windows 10, version 1511 and version 1507 but not version 1607. To learn more, see DISM Supported Platforms.

Remote installation. Installing packages to a remote computer over a network is not supported.

Answer files. When you specify an answer file (Unattend.xml) for an image, only the settings specified in the offlineServicing configuration pass are applied. All other settings in the answer file are ignored. You can only specify one answer file at a time. For more information, see DISM Unattended Servicing Command-Line Options

Use an answer file to ensure package dependencies. Some packages require other packages to be installed first. Because of this dependency requirement, you should use an answer file if you are installing multiple packages. By applying an answer file by using DISM, multiple packages can be installed in the correct order. This is the preferred method for installing multiple packages.

Package installation order. Packages are installed in the order that they are listed in the command line. In the following example, 1.inf, 2.inf, and 3.inf will be installed in the order in which they are listed in the command line.

DISM.exe /image:"c:\images\Image1" /Add-Driver /ForceUnsigned /DriverName:"C:\Drivers\1.inf" /DriverName:"C:\Drivers\2.inf" /DriverName:"C:\Drivers\3.inf"

Multiple servicing commands are not supported. You can specify multiple drivers (1.inf, 2.inf) or packages, but you cannot specify multiple commands (such as /Add-Driver /Remove-Driver or /Add-Driver /Add-Package) on the same command line.

Wildcards. Wildcards are not supported in DISM command lines.

Where is DISM?

Deployment Image Servicing and Management (DISM.exe) is a command-line tool that can be used to service a Windows image or to prepare a Windows Preinstallation Environment (Windows PE) image. For more information about DISM see What is DISM?

DISM in Windows 10

DISM comes with Windows 10, in the c:\windows\system32 folder, but you can run DISM in the command prompt from any location. You have to be running from a Command Prompt as administrator to use use DISM.

DISM in the ADK

If you are running an older version of Windows, or you need a different version of DISM on your PC, download and install the Windows Assessment and Deployment Kit (Windows ADK), see Windows Assessment and Deployment Kit (Windows ADK) Technical Reference.

DISM appears in the Windows ADK here: C:\Program Files (x86)\Windows Kits\<version>\Assessment and Deployment Kit\Deployment Tools\<arch>\DISM

where <version> can be 8.0, 8.1, or 10, and <arch> can be x86 or amd64.

If you need to copy and ADK version of DISM to a PC that does not have the ADK, see Copy DISM to another computer.

DISM Reference (Deployment Image Servicing and Management)

Deployment Image Servicing and Management (DISM) Command-Line Options

Device Drivers and Deployment Overview

Language Packs

Understanding Servicing Strategies