Problem

During the CC4 computer build process, after using the PXE boot or boot CD, the process fails with the error message 'Action exception: abort on fail - action "Check network connection". The system may also report under "Computer Build - Diagnostic Information", that the driver for the Network adapter is missing.

Causes and Resolutions

There are several possible causes for this problem:

• The right driver has not been added to the build console for the machine being built. Please check that you have the correct driver added.
  • Information on the drivers needed when building Windows 7 x86.
  • Information on the drivers needed when Building Windows 7 x64.
• ​If you have the correct driver, please either remove older versions of the same driver from the driver pool, or during the build process manually select the correct driver. Alternatively, you can try creating a new build CD which just has the required driver.
• You may have too many drivers in your driver pool; again the resolution to this is to create a new build CD which just has the required driver.

Manually Selecting the Correct Driver

Steps

• Add the required build process LAN driver to the build console. Please give the driver a suitable description which will allow you to identify it easily later, for example "[Stone 2014 H81M-P33] Realtek".

• During the build process of the client system you are prompted for the systems name and other details. As this stage, click the Drivers tab at the top
• Select the correct driver that is required (this is the driver that you added earlier - find it using the description that you gave to locate it more easily),

Creating a New Build CD with only the required LAN Driver

Steps

• Add the required build process LAN driver to the build console. Please give the driver a suitable description which will allow you to identify it easily later, for example "[Stone 2014 H81M-P33] Realtek".

• In the build console menu tree, go to Build and then right hand click on Build Disks. Then left click on New Build Disk...

• Follow the wizard to give the new build disk a Name and Description. These should allow you to identify the build disk as being for use with your Stone system.
• Click the Add Drivers button to add a specific driver. (If you have already created the Build disk and completed the wizard, right hand click on the new build disk and click on properties, to then be able to add drivers).

• Add the required LAN driver, using the description to find it in the list of drivers.

• Click on OK to finish adding the driver.
• Right hand click on the new Build disk to generate the image.

Applies to:

• Stone branded desktop and notebook products.

Problem

Large video drivers such as the Intel 4th Generation HD Graphics (Haswell) Video driver may not import into the Build Console unless certain updates are installed.

Cause

The cause is a limitation in the build console which cannot handle large driver packages. Typically, video drivers are the largest driver you will need to import into the system so this is the driver which may fail to import.

Resolution

If you are affected by this issue, download and install Update 141 for CC4, and then re-attempt the import process.

Applies to:

• Stone Desktop and Laptop PCs based on the Intel Haswell Platform or later, with CC4 packs

Driver Packs Available for CC4

We have recently introduced some new driver packs to increase the range of models that can be supported in the CC4 build console. Please use the instructions below to download the packs for your systems.

Step 1 - Download the SCCM Pack Summary

The SCCM Pack Summary contains links to Packs which are compatible with CC4, as well as LAN drivers for the build disk. The SCCM packs are ZIP files which can be downloaded, extracted, and then imported in the CC4 build console.

Download the pack summary and then find your model of machine in the list, for example, BOAMOT-476:

Step 2 - Download the Driver Pack

Download the driver pack by following the link in the SCCM column.

You will then be taken to a web page which shows you which operating systems have packs available, for example:

• Win8.1x64 - Windows 8.1, 64bit
• Win7x64 - Windows 7, 64bit
• Win8.1x86 - Windows 8.1, x86 or 32bit
• Win7x86 - Windows 7, x86 or 32bit

Download the pack that corresponds to the operating system that you are trying to run on your machines. Please note that Windows 8.1 is only supported on newer versions of CC4.

Step 3 - Import the Drivers from the Pack into Your Build Console

• Extract the contents of the ZIP pack file into a sub-folder.
• Follow your normal process to import the drivers into your RM build console from the sub-folder.

Step 4 - Find out Which Model of LAN Driver You Need for the Build Disk

In the SCCM Summary, it will tell you which brand or model of LAN Adapter driver you need for your system, for example, Realtek. 

Step 5 - Now Download the Windows PE Driver for Your Build Disk

The Windows PE Driver is needed for your build disk. This is often a different version of driver than the driver for the Windows that will eventually run on the machine.

For example, if you are planning to deploy Windows 7 x64 on the machines (the target operating system), its likely that you will need the Windows 7 x86 driver for your build disk, unless you have a very new version of CC4.

Sample Windows PE LAN Driver Chart from the SCCM Pack Summary

Download the Windows PE / Build Disk driver that you need by clicking on the link in the SCCM pack summary, as above.

Step 6 - After the System is Built, Install any Remaining Drivers

On some systems - mainly notebooks - there are some drivers, called non-INF drivers, which cannot be added to the CC4 build console. To use these drivers you will need to manually download them for your model from the Stone Driver Finder and then install them onto your built system.

Types of driver include:

• Hotkey software (needed for the onscreen display functionality on many Stone notebooks)
• Touchpad drivers
• Some camera drivers
• Intel Bluetooth drivers and software

Frequently Asked Questions

Which INF files do I need to Import from the Packs?

Most driver packages now include a small text file which tells you exactly which driver files you need to import into your build console. When about to import drivers, we recommend you print the list and work through it. Whilst most lists are quite short, it is important not to miss a driver, to ensure that you have no “Unknown Devices” in Device Manager at the end of the build process.

What If I Need Help Installing Drivers or to Build My Machine?

Please contact Stone support. We will be happy to help you with through the process.

Are the Build Disk Drivers Digitally Signed?

All drivers - including the Windows PE Drivers for the build disk - are digitally signed. We recommend that when adding drivers, tick the option box for "Digitally Signed Driver" where possible. 

What BIOS Settings Should I Use?

The best BIOS settings vary from model to model, but here are some general recommendations for building systems onto CC4 if you are deploying Windows 7.

What If There is No Pack Available for My Model?

Please contact your Stone account manager or Stone Support if your model is not listed as we may be able to add support for it. Known models for which there is no pack available include the Stone Classmate 3.

Applies to:

• Stone Desktop and Laptop PCs with CC4 / SCCM pack support (generally 2011 models and newer). (Last Updated 1/12/16).

CC4 Driver Packs Driver Import

The Driver packs are made up of folders containing drivers for specific items. For example, for a particular model, you may have AUDIO, VGA and LAN driver sub-folders.

Some of the drivers provided by the original component manufacturer are quite large and may contain lots of files. This article explains how to find out which files need to be imported.

Method

Drivers are made up of various system files including Driver Information Files, knowns as .INF files. Each CC4 driver pack includes in the ZIP package a small text file which tells you which INF files you need to import into the CC4 build console.

For example:

The Stone H81M-P-SI (BOAMOT-476) based needs these driver INF files importing from the driver folders:

By providing the names of the specific INF files required, this prevents you needing to manually work out which INF is needed, and prevents you from installing unnecessary files.

Instructions

• Import the drivers into your build console using the same method as you normally use.
• Don't forget to also add the network drivers for the Build Area - the Driver Packs Article contains more information on this.

Applies to:

• Stone Desktop and Laptop PCs with CC4 packs (generally 2011 models and newer)

LAN Drivers for the Build Process

If you are deploying Windows 7 32bit (x86) on CC4, the LAN drivers you need for the Build Area, to start the build process, must be either:

• Vista 32-bit (x86) drivers (Windows PE 2.0)
• Windows 7 32-nbit (x86) drivers (Windows PE 3.1) - only if you are running CC4 Update 133

These LAN drivers are used to either PXE boot the system, or to boot the system from CD, and then start the build process after connecting to the server.

Vista 32-bit drivers for supported models are included in the Driver Packs Summary.

LAN Drivers for the Operating System I want to Deploy

You will need the LAN drivers for Windows 7 x86 too, so that the system can connect to the network once it has built. These drivers are also included in the driver packs.

Applies to:

• Stone Desktop and Laptop PCs with CC4 packs (generally 2011 models and newer)

LAN Drivers for the Build Process

If you are deploying Windows 7 64bit (x64) on CC4, the LAN drivers you need for the Build Area, to start the build process, must be Windows 7 32-bit (x86) drivers.

This 32-bit Windows 7 driver is used to either PXE boot the system, or to boot the system from CD, and then start the build process.

Windows 7 32-bit drivers for supported models are included in the Driver Packs Summary.

LAN Drivers for the Operating System I want to Deploy

You will need the LAN drivers for Windows 7 x64 too, so that the system can connect to the network once it has built. These drivers are also included in the driver packs.

Applies to:

• Stone Desktop and Laptop PCs with CC4 packs (generally 2011 models and newer)

Previous Driver Packs Available for CC4

Please use the attached document to download driver packs for supported models. Please contact your Stone account manager if your model is not listed as we may be able to add support for it.

Recently added models as of May 2014:

• Stone (MSI) H81M-P33 (BOAMOT-464)*
• Stone (Asus) H81T (BOAMOT-471)*
• Stone (Asus) B85M-E (BOAMOT-463)*
• Stone (Asus) CS-B (BOAMOT-467)* (See note below)
• Stone (Asus) Q87-T (BOAMOT-470)* (See note below)
• N120 Netbook*
• NT310-H Notebook*

The following models however do NOT have pack support for CC4 at this time:

• Stone (Asus) Q87M-E (BOAMOT-462 / BOAMOT-473)

Windows 7 32bit (x86) Support for Some Models Requires CC4 Update 133

The Stone (Asus) CS-B (BOAMOT-467) and Stone (Asus) Q87-T (BOAMOT-467) do not have Windows Vista LAN drivers available. This means that Windows PE 2.0 support is not available. Windows PE 2.0 has been used to build machines into Windows 7 x86 system.

The solution is to have CC4 Update 133 installed. This allows PE 3.1 drivers (Windows 7 x86) to be used to build a machine as a Windows 7 x86 machine.

* Last Updated 13/5/14

Applies to:

• Stone Desktop and Laptop PCs with CC4 packs (generally 2011 models and newer)

Problem

Some versions of the Smart Technologies Product Drivers can cause problems when a USB 3.0 controller is installed in the system. This has been verified on Windows 7 and the 2010 version of the Smart Technologies driver package.

When you boot the system, the keboard and or mouse may be unresponsive until you remove them and then plug them back in.

Removing the USB 3.0 controller monitor program does not resolve the problem. The problem has been seen on H61, B75, Q77 and H81 systems.

Cause

The drivers themselves appear to cause system problems as they were not designed to be aware of USB 3.0 controllers. The issues are evident even if you are not using the USB 3.0 ports on the system.

Resolution

Either seek updated drivers from Smart Technologies, or if you are not connecting the Smartboard / Smarttable to the problem system, just uninstall the Smart Technologies driver package from Control Panel. The rest of the Smart Technology software will continue to function without the driver package.

Applies to:

• Desktop and Laptop products with USB 3.0 controllers, running Windows 7

Network Driver not Installed in Build Process

Issue

Older version of the Realtek Network driver for Windows 7 x86 (to support a system being built for Windows 7 x64) does not correctly support the N120's LAN interface when being used with WDS or CC4. The driver is not selected and therefore a network connection is not available to complete the build process.

You may get the error message 'Action exception: abort on fail - action "Check network connection"'.

Cause

The available driver not fully include a matching device ID for the adapter present in the notebook:

PCI\VEN_10EC&DEV_8136&SUBSYS_31101558&REV_06
PCI\VEN_10EC&DEV_8136&SUBSYS_31101558
PCI\VEN_10EC&DEV_8136&CC_020000
PCI\VEN_10EC&DEV_8136&CC_0200

The driver is sufficient to be used in a Windows 7 installation (either manually, using the setup program or even using DPINST) but it is not sufficient for WDS / CC4 to match the driver to the hardware during the hardware detection phase.

Resolution

The Realtek LAN Driver dated May 2014 or newer resolves this problem:

• Windows 7 x86
• Windows 7 x64
• Windows Vista x86

Applies to:

• Stone N120 Netbook (NOTCHA-258)

Issues

There are a number of issues regarding USB 3.0 controllers primarily with Windows 7. This article highlights some of the more common problems as well as work-arounds for them. A driver package tor the four most common groups of USB 3.0 controllers is available at the end of this article.

Problem 1 - Intermittent Device Response with Third Party Applications

Problem 2 - VMWare Player or VMWare Workstation USB Removable Device / Passthrough does not work

Problem 3 - Intel USB 3.0 Controller Driver May not Install through WDS / MDT / CC4 / SCCM

Problem 4 - Upgrade to Windows 8 will not proceed with the Manufacturer USB 3.0 driver Installed

Problem 5 - Smart Technologies Tablet or Smart Technologies Smartboard drivers cause the system keyboard and/or mouse to be Unresponsive

Problem 6 - Removal of EHCI Support From Intel Skylake and newer platforms means that Windows 7 can't use USB devices until an additional driver installed

USB 3.0 Controllers Affected

The main controllers addresses by this article are:

• Renesas1: Renesas first generation USB 3.0 Controller uPD720200 and uPD720200a, as used in the Intel 6 Series Desktop boards
• Renesas2: Renesas second generation USB 3.0 Controller uPD720201 and uPD720202 as used in some high end motherboards
• Intel7: Intel first generation USB 3.0 controller as Integrated into the 7 Series Intel Chipset, such as Q77, HM75 etc.
• Intel8/9: Intel second and third generation USB 3.0 controllers as integrated into the 8 and 9 Series Intel chipsets, such as the Q87.
• Intel 1x0: Intel fourth generation USB 3.0 controllers as integrated into the Skylake series chipsets such as the H110M, B150 and Q170.
• ASMedia 104x and 107x Controllers.

​Native support for most of these controllers is available from within Windows 8.1; the Windows 8 / Windows 8.1 in-box driver is not affected by the issues discussed in this article.

Problem 1 - Intermittent Device Response with Third Party Applications

Applications which monitor the USB ports on a system may not work, or USB devices in the system may have intermittent issues

Cause

The USB 3.0 Controllers above install their own port monitoring application by default. This notifies you, for example, if you plug a USB 3.0 device into a USB 2.0 port. The monitoring application monitors all ports on the system including USB 2.0 ports and issues can be seen across all ports in the system.

The conflict between the driver's port monitoring application and an add-application which is also probing the USB ports can cause either program to cease working, or the USB ports themselves may intermittently fail to respond or detect devices.

Resolution

• Renesas1, Intel7 and Intel8/9:
  • Uninstall the driver
  • Reboot
  • Reinstall the driver using the INF only method, using Device manager to install the basic driver components only. The monitoring application is not installed using this method, and the conflict is resolved.
• ​Renesas2 - either follow the method for Renesas1 above, or:
  • ​Uninstall the driver
  • Reboot
  • Reinstall the driver using the /v"NO_MONITOR=1" switch to prevent the monitoring application from being installed. In the Stone USB 3.0 driver package, this is also available as silentsetup_no_monitor.bat
• ASMedia
  • ​Uninstall the driver
  • Reboot
  • Install the driver in the Stone USB 3.0 driver package as this does not include a USB monitoring application.

See also Problem 5 for a similar issue around Smart Technologies Smartboard or Smarttablet drivers.

Problem 2 - VMWare Player or VMWare Workstation USB Removable Device / Passthrough does not work

In this situation VMWare products are not able to take control of the USB device and pass it through to the guest operating system. When you attempt to connect the device to the guest operating system, you get an error message that the device is in use on the host.

Resolution 1

Ensure the VMWare USB Arbitration service is running in Computer Management > Services.

Resolution 2

Use the same resolution as for Problem 1. Then once you have removed the USB monitoring program, you should be able to assign the USB device to the guest operating system.

Problem 3 - Intel USB 3.0 Controller Driver May not Install through WDS / MDT / CC4 / SCCM

When you use the INF driver and deploy this through a driver package, the Intel 7 or 8/9 driver may not install properly. The "Intel(R) USB 3.0 Root Hub" is listed in device manager as an Unknown device, or with a yellow exclamation mark on it. Device Manager reports that the driver is not installed correctly.

Cause

The cause is a problem with the way the driver and driver ID is constructed. The device has an ID of USB3\ROOT_HUB30&VID_8086_PID_1E31 whilst the driver does not have an INF that matches closely enough for the deployment process such as WDS to use it.

Resolution

• Reinstall the driver after the initial build of the system. This can be done either using the standard setup program, or, for larger scale deployments such as an SCCM build, use a task sequence and the silent setup option included in the Stone USB 3.0 driver package.
• If you require that the Intel USB monitor program is not installed you can still use the INF only method after the operating system has been installed. To do this programatically, use the drivers in the INF_Only folder and the install.bat file. This needs to be run with Administrative privileges.

Problem 4 - Upgrade to Windows 8 will not proceed with the Manufacturer USB 3.0 driver Installed

If you attempt to upgrade to Windows 8 from Windows 7 the upgrade checker may report that the USB 3.0 controller driver is not compatible.

Resolution

• Uninstall the USB 3.0 controller driver
• Upgrade to Windows 8
• Install the latest Windows 8 USB 3.0 controller driver IF Windows does not automatically install a driver during the upgrade. Use of the Windows in-box driver is recommended where possible.

Problem 5 - Smart Technologies Table or Smart Technologies Smartboard drivers cause the system keyboard to be Unresponsive

Similar to Problem 1, some versions of the Smart Technologies Product Drivers can cause problems when a USB 3.0 controller is installed in the system. This has been verified on Windows 7 and the 2010 version of the Smart Technologies driver package.

When you boot the system, the keboard and or mouse may be unresponsive until you remove them and then plug them back in.

Removing the USB 3.0 controller monitor program does not resolve the problem. The problem has been seen on H61, B75, Q77 and H81 systems.

Cause

The drivers themselves appear to cause system problems as they were not designed to be aware of USB 3.0 controllers. The issues are evident even if you are not using the USB 3.0 ports on the system.

Resolution

Either seek updated drivers from Smart Technologies, or if you are not connecting the Smartboard / Smarttable to the problem system, just uninstall the Smart Technologies driver package from Control Panel. The rest of the Smart Technology software will continue to function without the driver package.

Stone USB 3.0 Driver Package

A driver package is available that contains the most up to date Windows 7 USB 3.0 controller drivers for all six mentioned controllers as of 25/7/16. This package includes:

• The standard setup program
• Silent setup program (batch file)
• Silent setup program with no monitoring application - Renesas 2 controller only (batch file)
• INF installer only (no monitoring program)

Windows 7 Drivers for x86 and x64 are included. Download here.

Applies to:

• Desktop and Laptop products with USB 3.0 controllers, running Windows 7

This article discusses the various options available to customers building their Stone PC desktops or notebooks onto CC4. It is intended as general advice to assist customers looking for the guidance as to what they can do.

CC4 Service Release 1

This only supports Windows 7 x86 (32-bit) and does not support Windows 7 x64 (64-bit).

Windows 7 x86 on SR1

The automatic build process needs Vista x86 LAN drivers available. These drivers are not being maintained by component manufacturers often meaning that new models of system cannot be automatically built onto CC4 SR1.

Options:

• If Vista x86 LAN drivers are available, use the automatic build process
• If Vista x86 LAN drivers are not available, you will need to Smartclient the machine.
  • In the longer term, consider a server upgrade to support a wider range of client operating systems. For example, a vanilla Server 2012 network can support Windows 7 x86 as the WDS build process does not need to use Vista LAN drivers.

CC4 Service Release 2

This supports Windows 7 x86 (32-bit) and Windows 7 x64 (64-bit).

Windows 7 x86 on SR2

The automatic build process needs Vista x86 LAN drivers available. These drivers are not being maintained by component manufacturers meaning that new systems cannot be automatically built onto CC4 SR1.

Options:

• If Vista x86 LAN drivers are available, use the automatic build process
• If Vista x86 LAN drivers are not available, you will need to Smartclient the machine or build the machine as Windows 7 x64 instead.
  • In the longer term, consider a server upgrade to support a wider range of client operating systems. For example, a vanilla Server 2012 network can support Windows 7 x86 as the WDS build process does not need to use Vista LAN drivers.

Windows 7 x64 on SR2

The automatic build process needs Windows 7 x86 LAN drivers, which generally are immediately available for most systems.

CC4 SR2 with Update 133

Windows 7 x86 on SR2 with Update 133

With Update 133 support has been added for building Windows 7 x86 machines using Windows 7 x86 LAN drivers (Windows PE 3.1). This gets around the lack of up to date Vista LAN drivers as component manufacturers are often not making these available.

Options:

• If Windows x86 LAN drivers, use the automatic build process, selecting Windows PE 3.1.
• Alternatively, if Vista x86 LAN drivers are available, you could use the automatic build process, selecting Windows PE 2.0

Windows 7 x64 on SR2 with Update 133

The automatic build process needs Windows 7 x86 LAN drivers, which generally are immediately available for most systems.

CC4.5

This supports the building of Windows 8 and Windows 8.1 machines, using Windows PE 4.0/Windows 8 drivers to build Windows 8 machines, and Windows PE 5.0/Windows 8.1 drivers to build Windows 8.1 machines.

Where to Get CC4 Driver Pack for Stone Systems

Follow this link to see the latest driver packs available. This article gives links to the drivers and build instructions.

Applies to:

• Stone branded desktop and notebook products.

The Device

The device is a chipset component found on Intel Skylake and newer motherboards. It is part of Intel Platform Trust Technology (PTT) as can be used to provide TPM 2.0 functionality. The device can therefore be used to provide credential storage and key management, useful if you are deploying technologies such as Bitlocker.

Drivers and Software

This device is not installed by using the Intel Chipset Driver software or Intel Management Interface (MEI). The device is automatically supported in Windows 8 and Windows 10. The BIOS must be running in UEFI mode.

If you are using Windows 7 x64, or Windows Server 2008 R2, a Hotfix is available to add support for TPM 2.0 functionality. This will provide the driver support required. Again, the system must be running in UEFI mode.

Applies to:

• Stone systems with applicable chipsets including the Skylake H110 chipset.

The Device

The device is a BIOS component found on Asus motherboards to allow Asus utilities and software to communicate with BIOS components. For example, Asus USB 3.0 UASP boosting software may need this device to be working.

Drivers and Software

This device is not installed by using the Intel Chipset Driver software or Intel Management Interface (MEI). To find the drivers for this device, visit the Asus product support page for your product and look for an ACPI Driver under "Utilities".

Alternative Download Location

Please use these alternative download links if required:

• Asus B85M-E for Windows 7 and 8 is here (last updated 19/11/13).
• Asus Q87-T / Asus CS-B for Windows 7, Windows 8 and Windows 8.1 here (last updated 11/4/14)

Using this Driver With Windows Deployment Services (WDS)

We are aware that this driver may not import into Windows Deployment Services on Windows Server 2008R2 and Server 2012. As a work around, you will either need to install the driver manually into deployed systems, or use WDS to capture and deploy your own Install image which already has the driver included.

Applies to:

• Stone systems based on Asus motherboards including the B85M-E (BOAMOT-463), CS-B (BOAMOT-467), Q87-T (BOAMOT-470) and H81M-P-SI (BOAMOT-476).

WIM Files

Windows Image File are used to store boot-up images (for example, images that run Windows Setup from CD or USB, or Network Boot), Windows PE (again, from CD, USB or Network boot) or entire operating system images.

WIM files can be manipulated using systems such as MDT or WDS, to add drivers or distribute them out to clients.

On occasion, it can be necessary to manually mount a WIM file to add drivers, or to inspect the contents. This article will cover the basics.

• What Tools You Need
• WIM Index - Seeing What Images Are Contained Inside a WIM File
• Mounting the WIM File
• Adding Drivers to a Mounted Image
• Unmounting the File

The Tools You Need

You will need the Windows Assessment and Deployment Kit (ADK) to load images. For some image functions - for example, adding drivers, your ADK version must match, or be greater, than the version of the operating system contained inside the image. Sometimes the version of operating system you are running also matters. For example, the Windows 10 versions of the ADK are operating system specific. The 1511 version of the kit requires Windows 10, version 1511.

Windows ADK Page here.

Seeing What Images Are Contained Inside a WIM File

You can do this without mounting, or extracting, the WIM file.

Instructions:

• After installing the Windows ADK, open up the Deployment Tools Command prompt. This will give you easy access to the DISM.EXE utility.
• Run the command below against the WIM file, in this case, BOOT.WIM in the Stone folder.

dism /get-wiminfo /wimfile:"boot.wim"

• The Index number tells you how to reference the image with other DISM commands. For example, the Windows PE Image above can be accessed using Image Index 1.

Mounting the WIM File

• Make a directory for the mounted files. This directory should be empty. In the examples below, this d:\Mount.
• You will need the Index number of the image you want to mount, for example Index 1, from above.
• Again using the Deployment Services command prompt and DISM, run the command below.

dism /mount-wim /wimfile:"boot.wim" /index:1 /mountdir:"d:\mount"

• Or for reading only - without changes being permitted:

dism /mount-wim /wimfile:"boot.wim" /index:1 /mountdir:"d:\mount" /readonly

• This will then give you a folder that you can browse with Windows Explorer.

Adding Drivers to A Mounted Image

You can add drivers to an image using the DISM command.

• To add drivers from a specific driver INF file:

dism /Image:"d:\mount" /Add-Driver /Driver:"e:\drivers\video\mydriver.inf"

• To add drivers from a folder:

dism /Image:"d:\mount" /Add-Driver /Driver:"e:\drivers\video"

• And lastly, to add drivers from a folder and all subfolders:

dism /Image:"d:\mount" /Add-Driver /Driver:"e:\drivers" /recurse

Unmounting the File

When you are finished, the Image must be unmounted, even if you do not wish to save any changes.

• To unmount an image, without saving changes run the following:

dism /unmount-Wim  /MountDir:"d:\mount" /discard

• To unmount an image, saving any changes you have made instead run the following:

dism /unmount-Wim  /MountDir:"d:\mount" /commit

Applies to:

• Windows Server and Windows Client Deployment Tools