Export (0) Print
Expand All

Add and Remove Drivers Offline

Published: October 22, 2009

Updated: July 8, 2010

Applies To: Windows 7, Windows Server 2008 R2

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

Deployment Image Servicing and Management (DISM.exe) is a command-line tool used to update offline Windows® images. There are two ways to install or remove drivers offline with DISM. You can either apply an unattended answer file to the offline image, or you can add or remove the drivers directly from the command prompt.

This topic includes:

Add Drivers to an Offline Image by Using DISM

When you use DISM to install a device driver to an offline image, the device driver is added to the driver store. The driver store is a location on the computer that contains all of the drivers for that computer. When Plug and Play runs, detected devices are matched with device drivers in the driver store.

Boot-critical drivers are reflected on the system. Driver reflection is the process of installing a driver on a computer that might or might not have a device for that driver. Typically, this involves copying the driver files to a destination location and creating the service.

  1. At an elevated command prompt, navigate to the Windows OEM Preinstallation Kit (Windows OPK) servicing folder, and type the following command to retrieve the name or index number for the image you want to modify.

    Dism /Get-WimInfo /WimFile:C:\test\images\install.wim
    
    An index or name value is required for most operations that specify a WIM file.

  2. Type the following command to mount the offline Windows image.

    Dism /Mount-Wim /WimFile:C:\test\images\install.wim /Name:"Windows 7 HomeBasic" /MountDir:C:\test\offline
    
  3. At a command prompt, type the following command to add a specific driver to the image.

    Dism /Image:C:\test\offline /Add-Driver /Driver:C:\drivers\mydriver.INF
    
    Multiple drivers can be added on one command line if you specify a folder instead of an .inf file. To install all of the drivers in a folder and all its subfolders use the /recurse option. For example,

    Dism /Image:C:\test\offline /Add-Driver /Driver:c:\drivers /Recurse
    
    To install an unsigned driver, use /ForceUnsigned to override the requirement that drivers installed on X64-based computers must have a digital signature. For example,

    Dism /Image:C:\test\offline /Add-Driver /Driver:C:\drivers\mydriver.INF /ForceUnsigned
    
  4. Review the contents of the %WINDIR%\Inf\ directory in the mounted Windows image to ensure that the .inf files were installed. Drivers added to the Windows image are named Oem*.inf. This is to ensure unique naming for new drivers added to the computer. For example, the files MyDriver1.inf and MyDriver2.inf are renamed Oem0.inf and Oem1.inf.

  5. At a command prompt, type the following command to commit the changes and unmount the image.

    Dism /Unmount-Wim /MountDir:C:\test\offline /Commit
    

Remove Drivers from an Offline Image by Using DISM

noteNote
You cannot remove drivers from a Windows Vista® with Service Pack 1 (SP1) or Windows Server® 2008 image. For more information, see Service a Windows Vista or Server 2008 Image

  1. At an elevated command prompt, navigate to the Windows OPK servicing folder, and type the following command to retrieve the name or index number for the image you want to modify.

    Dism /Get-WimInfo /WimFile:C:\test\images\install.wim
    
    An index or name value is required for most operations that specify a WIM file.

  2. Type the following command to mount the offline Windows image.

    Dism /Mount-Wim /WimFile:C:\test\images\install.wim /Name:"Windows 7 HomeBasic" /MountDir:C:\test\offline
    
  3. At a command prompt, type the following command to remove a specific driver from the image. Multiple drivers can be removed on one command line.

    Dism /Image:C:\test\offline /Remove-Driver /Driver:OEM1.inf /Driver:OEM2.inf
    
    WarningWarning
    Removing a boot-critical driver package can make the offline Windows image unbootable. For more information, see Driver Servicing Command-Line Options

  4. At a command prompt, type the following command to commit the changes and unmount the image.

    Dism /Unmount-Wim /MountDir:C:\test\offline /Commit
    

Add Drivers to an Offline Windows Image by Using an Unattended Answer File

It is important to note that all drivers in the directory and subdirectories that are referenced in the answer file are added to the image. You should manage the answer file and these directories carefully to address concerns about increasing the size of the image with unnecessary driver packages.

  1. Locate the device driver .inf files that you intend to install on your Windows image.

  2. Use Windows System Image Manager (Windows SIM) to create an answer file that contains the paths to the device drivers that you intend to install.

  3. Add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the offlineServicing configuration pass.

  4. Expand the Microsoft-Windows-PnpCustomizationsNonWinPE node in the answer file. Right-click DevicePaths, and then select Insert New PathAndCredentials.

    A new PathAndCredentials list item appears.

  5. For each location that you intend to access, add a separate PathAndCredentials list item.

  6. In the Microsoft-Windows-PnpCustomizationsNonWinPE component, specify the path to the device driver and the credentials used to access the file if the file is on a network share.

    noteNote
    You can include multiple device driver paths by adding multiple PathAndCredentials list items. If you add multiple list items, you must increment the value of Key for each path. For example, you can add two separate driver paths where the value of Key for the first path is equal to 1 and the value of Key for the second path is equal to 2.

  7. Save the answer file and exit Windows SIM. The answer file must be similar to the following sample.

    <?xml version="1.0" ?>
    <unattend xmlns="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
       <settings pass="offlineServicing">
          <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
             <DriverPaths>
                <PathAndCredentials wcm:keyValue="1">
                   <Path>\\networkshare\share\drivers</Path>
                   <Credentials>
                      <Domain>Fabrikam</Domain>
                      <Username>MyUserName</Username>
                      <Password>MyPassword</Password>
                   </Credentials>
                </PathAndCredentials>
             </DriverPaths>
          </component>
       </settings>
    </unattend>
    
  8. Mount the Windows image that you intend to install the drivers to by using DISM. For example:

    Dism /Mount-Wim /WimFile:C:\test\images\install.wim /Index:1 /MountDir:C:\test\offline
    
    An index or name value is required for most operations that specify a WIM file.

  9. Use DISM to apply the unattended installation answer file to the mounted Windows image. For example,

    DISM /Image:C:\test\offline /Apply-Unattend:C:\test\answerfiles\myunattend.xml
    
    For more information about applying an unattended answer file, see Unattended Servicing Command-Line Options.

    The .inf files referenced in the path in the answer file are added to the Windows image.

  10. Review the contents of the %WINDIR%\Inf\ directory in the mounted Windows image to ensure that the .inf files were installed. Drivers added to the Windows image are named Oem*.inf. This is to ensure unique naming for new drivers added to the computer. For example, the files MyDriver1.inf and MyDriver2.inf are renamed Oem0.inf and Oem1.inf.

  11. Unmount the .wim file and commit the changes. For example,

    Dism /Unmount-Wim /MountDir:C:\test\offline /Commit
    

If you need drivers for Windows Preinstallation Environment (Windows PE) to see the local hard disk drive or a network, you must use the windowsPE configuration pass of an answer file to add drivers to the Windows PE driver store and to reflect boot-critical drivers required by Windows PE. For more information, see Add Device Drivers by Using Windows Setup.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft