Capture Image Pc

Return to site

Capture Image Pc

Image Capture Software Free
Screen Capture Pc
How to capture an image from a movie in Windows Media Player Updated: by Computer Hope When trying to capture an image or create a screenshot from a video in Microsoft Windows Media Player using the print screen button, the captured image is blank or black image.
-->Deployment Image Servicing and Management (DISM.exe) mounts a Windows image (.wim) file or virtual hard disk (.vhd or .vhdx) for servicing. You can also use the DISM image management command to list the image index numbers, to verify the architecture for the image that you are mounting, append an image, apply an image, capture an image and delete an image. After you update the image, you must unmount it and either commit or discard the changes that you have made.
Rename Windows partition as Windows, and the new image partition as Image. Create a new folder in this new partition, name the folder as Scratch. Later on when we boot reference machine from install media to capture image with DISM command, this folder will be needed to offer DISM enough temporary working space.
Yes I do install Hyper-V on a Windows 10 desktop and use that desktop to capture the image. MDT doesn't need to be installed on the same PC because you can just use a standalone media and load the ISO that MDT creates into Hyper-V.
This topic discusses DISM commands related to image management. To see other command-line options, see Deployment Image Servicing and Management (DISM) Command-Line Options. For more information about common DISM scenarios, see What is DISM?.
In addition to the command-line tool, DISM is available by using Windows PowerShell. For more information, see Deployment Imaging Servicing Management (DISM) Cmdlets in Windows PowerShell.
The following commands can be used to mount, unmount, capture, append, and delete and query .wim, .vhd and .vhdx files. These options are not case sensitive.
/Append-ImageAdds an additional image to a .wim file. /Append-Image compares new files to the resources in the existing .wim file specified by the /ImageFile argument, and stores only a single copy of each unique file so that each file is only captured once. The .wim file can have only one assigned compression type. Therefore, you can only append files with the same compression type.
This command-line option does not apply to virtual hard disk (VHD) files.
Important
Ensure that you have enough disk space for the /Append-Image option to run. If you run out of disk space while the image is being appended, you might corrupt the .wim file.
Syntax:

ParameterDescription
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/ConfigFilespecifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/BootableMarks a volume image as being a bootable image. This argument is available only for Windows Preinstallation Environment (WinPE) images. Only one volume image can be marked as bootable in a .wim file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
/NoRpFixDisables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside of the value specified by /ImageFile will not be captured.
Example:
/Apply-FFUFor FFU, this command applies a Full Flash Utility (FFU) or split FFU (SFU) to a specified physical drive.
Syntax:
ParameterDescription
/ImageFileThe path and name of the FFU image file that will be applied
/ApplyDriveThe path to the phyisical drive that will be imaged
/SFUfileOptional, for split FFUs that are captured with no compression. Use /SFUFile to reference split FFU files (SFUs). Pattern is the naming pattern and location of split files. Use a wildcard character when specifying the naming pattern. For example, 'E:imageinstall*.sfu' will apply all of the split files in the E:image directory named install1.sfu, install2.sfu, and so on.
Example:
/Apply-ImageFor WIM, this command applies a Windows image file (.wim) or a split Windows image (.swm) files to a specified partition. Beginning with Windows 10, version 1607, DISM can apply and capture extended attributes (EA).
For FFU, this command applies a full flash update (.ffu) image to a specified drive. It doesn't support applying an image from a virtual hard disk (.vhdx) file, though you can use this command to apply a full image to a VHD. FFU applies to Windows 10 only. While you can use this command to apply an FFU, use /apply-ffu instead.
This option doesn't support applying an image from a virtual hard disk (VHD), though you can use this command to apply images to a .vhdx file that's been attached, partitioned, and formatted.
Arguments for WIM:
Arguments for FFU
See /apply-ffu.
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
/NoRpFixDisables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside the value specified by /ImageFile will not be captured.
/SWMFileEnables you to reference split .wim files (SWMs). Pattern is the naming pattern and location of split files. Use a wildcard character when specifying the naming pattern. For example, 'E:imageinstall*.swm' will apply all of the split files in the E:image directory named install1.swm, install2.swm, and so on.
/ConfirmTrustedFileValidates the image for Trusted Desktop on a Windows 10, Windows 8.1, or Windows 8. This option can only be run on a computer running at least WinPE 4.0. When using /Apply-Image with the /ConfirmTrustedFile option in WinPE, always specify the /ScratchDir option pointed to a physical media location. This ensures that short file names will always be available. See DISM Global Options for Command-Line Syntax for more information about the default behavior of the /ScratchDir option. Beginning with Windows 10, version 1607, you can use /EA to apply extended attributes.
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/CompactApplies an image in compact mode, saving drive space. Replaces WIMBoot. For Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) only. 
Note: If you're applying an image in compact mode with the /ScratchDir option, make sure your ScratchDir folder is not on a FAT32-formatted partition. Using a FAT32 partition could result in unexpected reboots during OOBE.
/EANew in Windows 10, version 1607. Applies extended attributes.
/ApplyDriveSpecifies the logical drive, using the DeviceID. to get the device ID from the command line, type 'wmic diskdrive list brief'. Note: a VHD may appear with the name 'PhysicalDrive' in the description, for example, .PhysicalDrive2.
/SFUFileUse /SFUFile to reference split FFU files (SFUs). Pattern is the naming pattern and location of split files.
Examples:
/Capture-CustomImageCaptures the incremental file changes based on the specific install.wim file to a new file, custom.wim for a WIMBoot image. You can't capture an empty directory. The captured files are converted to pointer files. The custom.wim is placed in the same folder next to the install.wim.
Important
/Capture-CustomImage only captures the customization files. It can't be used to capture installation files into a new WIM.
Keep the install.wim and custom.wim files together. Don't switch out either the custom.wim file or the install.wim file.
You can only capture the custom image once. Don't remove or recapture a custom.wim after capturing the incremental file changes.
Syntax:
ParameterDescription
/CaptureDirSpecifies the directory to which the image was applied and customized.
/ConfigFileSpecifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
[/ConfirmTrustedFileValidates the image for Trusted Desktop on a Windows 10, Windows 8.1, or Windows 8. This option can only be run on a computer running at least WinPE 4.0.
Example:
/Capture-FFUCaptures an image of a physical drive's partitions to a new .ffu file.
You can capture the image as a full flash utility image (.ffu) file or a set of split ffu (.sfu) files;
Syntax:
ParameterDescription
/CaptureDriveThe physical drive to be captured. You can use diskpart to get drive number information. Uses the format .PhysicalDriveX, where X is the disk number that diskpart provides.
/PlatformIdsNot needed for desktop capture. Specifies one or more platform ids (separated with semicolon) to be added to the image. If not specified, platform id will be '*'.
/CompressSpecifies the type of compression used for when capturing. If you'll be splitting the FFU, specify none, as DISM doesn't support splitting compressed FFUs.
Examples:
Capture a desktop FFU:
Capture a desktop FFU that will be split:
/Capture-ImageCaptures an image of a drive to a new .wim file. Captured directories include all subfolders and data. You cannot capture an empty directory. A directory must contain at least one file. DISM can also optionally apply and capture extended attributes (EA).
You can capture the image as a Windows image (.wim) file or a set of split Windows image (.swm) files, but this option doesn't support capturing a virtual hard disk (.vhd/.vhdx) file. See /Capture-FFU if you are looking to capture an FFU.
Syntax:
ParameterDescription
/ConfigFileSpecifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/CompressSpecifies the type of compression used for the initial capture operation. The maximum option provides the best compression, but takes more time to capture the image. The fast option provides faster image compression, but the resulting files are larger than those compressed by using the maximum option. This is also the default compression type that is used if you do not specify the argument. The none option does not compress the captured image at all.
/BootableMarks a volume image as being a bootable image. This argument is available only for WinPE images. Only one volume image can be marked as bootable in a .wim file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
/NoRpFixDisables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside of the value specified by /ImageFile will not be captured.
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/EACaptures extended attributes. The switch must be explicitly specified to capture extended attributes. DISM will capture extended attribute bits if they are set in the components to be captured in the WIM image. If the bits are not set, DISM won't set them. Only the inbox components of CAB packages and drivers will have these extended attribute bits, not the AppX package components or Win32 application components. Extended attributes with prefix '$Kernel.' in name will be skipped because only user mode extended attributes are captured. If you use DISM in Windows 10, version 1607 to capture extended attributes and use an earlier version of DISM to apply the image, the operation will succeed but the extended attributes will not be set to the applied image.
Examples:
/Cleanup-MountpointsDeletes all of the resources associated with a mounted image that has been corrupted. This command will not unmount images that are already mounted, nor will it delete images that can be recovered using the /Remount-Image command.
Example:
To learn more, see Repair a Windows Image
/Commit-ImageApplies the changes that you have made to the mounted image. The image remains mounted until the /Unmount-Image option is used.
Syntax:
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/AppendAdds the modified image to the existing .wim file instead of overwriting the original image. The /CheckIntegrity and /Append arguments do not apply to virtual hard disk (VHD) files.
Example:
/Delete-ImageDeletes the specified volume image from a .wim file that has multiple volume images. This option deletes only the metadata entries and XML entries. It does not delete the stream data and does not optimize the .wim file.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax:
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
Example:
/Export-ImageExports a copy of the specified image to another file. The source and destination files must use the same compression type. You can also optimize an image by exporting to a new image file. When you modify an image, DISM stores additional resource files that increase the overall size of the image. Exporting the image will remove unnecessary resource files.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax:
ParameterDescription
/SWMFileEnables you to reference split .wim files. pattern is the naming pattern and location of split files. You can also specify wildcard characters. For example, 'E:imageinstall*.swm' will export the split files in the E:image directory named install1.swm, install2.swm, and so on.
/CompressSpecifies the type of compression used for the initial capture operation. The /Compress argument does not apply when you export an image to an existing .wim file, you can only use this argument when you export an image to a new .wim file. The maximum option provides the best compression, but takes more time to capture the image. The fast option provides faster image compression, but the resulting files are larger than those compressed by using the maximum option. This is also the default compression type that is used if you do not specify the argument. Use the recovery option to export push-button reset images. The resulting files are much smaller in size, which in turn, greatly reduce the amount of disk space needed for saving the push-button reset image on a recovery drive. The destination file must be specified with an .esd extension. The none option does not compress the captured image at all.
/BootableMarks a volume image as being a bootable image. This argument is available only for WinPE images. Only one volume image can be marked as bootable in a .wim file.
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
Example:
/Get-ImageInfoDisplays information about the images that are contained in a .wim, .ffu, .vhd or .vhdx file. When used with the /Index or /Name argument, information about the specified image is displayed, which includes if an image is a WIMBoot image, if the image is Windows 8.1, see Take Inventory of an Image or Component Using DISM. The /Name argument does not apply to VHD files. You must specify /Index:1 for FFU and VHDX files.
Syntax:
Examples:
/Get-MountedImageInfoReturns a list of .ffu, .vhd, .vhdx, and .wim images that are currently mounted, as well as information about the mounted image such as whether the image is valid, read/write permissions, mount location, mounted file path, and mounted image index.
Example:
/Get-WIMBootEntryUse /Get-WIMBootEntry to display WIMBoot configuration entries for the specified disk volume.
For more information about how to display WIMBoot configuration entries, see Take Inventory of an Image or Component Using DISM.
This only applies to Windows 8.1; this feature isn't supported in Windows 10.
Syntax:
Image Capture Software FreeExample:
/List-ImageDisplays a list of the files and folders in a specified image.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax:
Example:
/Mount-ImageMounts an image from a .ffu, .wim, .vhd or .vhdx file to the specified directory so that it is available for servicing.
When mounting an image, note the following:
The mount directory must be created, but empty.
An index or name value is required for all image types. WIMs can contain more than image. For FFU and VHD, use index:1.
Right click on iphone. Syntax:
ParameterDescription
/ReadOnlySets the mounted image with read-only permissions. Optional.
/OptimizeReduces initial mount time.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
Examples:
/Optimize-Image /WIMBootPerforms specified configurations to an offline image.
ParameterDescription
/WIMBootconfigure an offline image for installing on a Windows image file boot (WIMBoot) system.
/OptimizeReduces initial mount time. /Optimize-Image /WIMBoot only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. Only use /Optimize-Image with images that will be used for WIMBoot supported systems. If /Optimize-Image is used with a non-WIMBoot supported system image, Windows may not work as expected, after installation on a non-WIMBoot supported device.
Example:
/Remount-ImageRemounts a mounted image that has become inaccessible and makes it available for servicing.
Syntax:
Example:
/Split-FFUFor FFU, this command splits an existing full-flash update (.ffu) file into multiple read-only split .sfu files. DISM doesn't support splitting compressed FFUs. If you are splitting FFUs, make sure that your FFU was captured with the /compress:none option specificed.
This option creates the .sfu files in the specified directory, naming each file the same as the specified /SFUFile, but with an appended number. For example, if you use c:flash.sfu, you'll get a flash.sfu file, a flash2.ffu file, a flash3.sfu file, and so on, defining each portion of the split .sfu file and saving it to the C: directory.
Syntax for FFU:
ParameterDescription
/FileSizeSpecifies the maximum size in megabytes (MB) for each created file. If a single file is larger than the value specified in the /FileSize option, one of the split .swm files that results will be larger than the value specified in the /FileSize option, in order to accommodate the large file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/ImageFileSpecifies the path of a .FFU file, example: flash.ffu.
/SFUFileReferences split FFU files (SFUs). Pattern is the naming pattern and location of split files.
Example:
/Split-ImageFor WIM, this command splits an existing .wim file into multiple read-only split .swm files.
This option creates the .swm files in the specified directory, naming each file the same as the specified path_to_swm, but with an appended number. For example, if you set path_to_swm as c:Data.swm, this option creates a Data.swm file, a Data2.swm file, a Data3.swm file, and so on, defining each portion of the split .wim file and saving it to the C: directory.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax for WIM:
ParameterDescription
/FileSizeSpecifies the maximum size in megabytes (MB) for each created file. If a single file is larger than the value specified in the /FileSize option, one of the split .swm files that results will be larger than the value specified in the /FileSize option, in order to accommodate the large file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/ImageFileSpecifies the path of an image file, example: install.wim.
Example:
/Unmount-ImageUnmounts the .ffu, .wim, .vhd or .vhdx file and either commits or discards the changes that were made when the image was mounted.
You must use either the /commit or /discard argument when you use the /Unmount-Image option.
Syntax:
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/AppendAdds the modified image to the existing .wim file instead of overwriting the original image. The /CheckIntegrity and /Append arguments do not apply to virtual hard disk (VHD, VHDX), or FFU files.
Examples:
/Update-WIMBootEntryUpdates the WIMBoot configuration entry, associated with the specified data source ID, with the renamed image file or moved image file path.
Note:/Update-WIMBootEntry requires a restart in order for any updates to take effect.
Syntax:
ParameterDescription
/PathSpecifies the disk volume of the WIMBoot configuration.
/DataSourceIDSpecifies the data source ID as displayed by /Get-WIMBootEntry.
Example:
/Apply-SiloedPackageApplies one or more siloed provisioning packages (SPPs) to a specified image. This option is only available after running CopyDandI.cmd from the ADK for Windows 10, Version 1607, and running dism.exe /Apply-SiloedPackage from the target folder created by CopyDandI.cmd.
Note:/Apply-SiloedPackage can only be run once against a Windows image, but /PackagePath can used more than once in the same command to apply multiple SPPs. SPPs will be applied in the specified order, so a dependency should be specified before the SPP that depends on it.
For more information about siloed provisioning packages, and how to use CopyDandI.cmd, see Siloed provisioning packages.
Screen Capture PcTo find out how to work with siloed provisioning packages, see Lab 10: Add desktop applications and settings with siloed provisioning packages (SPPs).
ParameterDescription
/PackagePathSpecifies the path of a siloed provisioning package file.
/ImagePathSpecifies the path of the Windows image where you are applying the SPP.

Parameter	Description
/WIMBoot	Use /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/ConfigFile	specifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/Bootable	Marks a volume image as being a bootable image. This argument is available only for Windows Preinstallation Environment (WinPE) images. Only one volume image can be marked as bootable in a .wim file.
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/Verify	Checks for errors and file duplication.
/NoRpFix	Disables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside of the value specified by /ImageFile will not be captured.

Parameter	Description
/ImageFile	The path and name of the FFU image file that will be applied
/ApplyDrive	The path to the phyisical drive that will be imaged
/SFUfile	Optional, for split FFUs that are captured with no compression. Use /SFUFile to reference split FFU files (SFUs). Pattern is the naming pattern and location of split files. Use a wildcard character when specifying the naming pattern. For example, 'E:imageinstall*.sfu' will apply all of the split files in the E:image directory named install1.sfu, install2.sfu, and so on.

Parameter	Description
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/Verify	Checks for errors and file duplication.
/NoRpFix	Disables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside the value specified by /ImageFile will not be captured.
/SWMFile	Enables you to reference split .wim files (SWMs). Pattern is the naming pattern and location of split files. Use a wildcard character when specifying the naming pattern. For example, 'E:imageinstall*.swm' will apply all of the split files in the E:image directory named install1.swm, install2.swm, and so on.
/ConfirmTrustedFile	Validates the image for Trusted Desktop on a Windows 10, Windows 8.1, or Windows 8. This option can only be run on a computer running at least WinPE 4.0. When using /Apply-Image with the /ConfirmTrustedFile option in WinPE, always specify the /ScratchDir option pointed to a physical media location. This ensures that short file names will always be available. See DISM Global Options for Command-Line Syntax for more information about the default behavior of the /ScratchDir option. Beginning with Windows 10, version 1607, you can use /EA to apply extended attributes.
/WIMBoot	Use /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/Compact	Applies an image in compact mode, saving drive space. Replaces WIMBoot. For Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) only. Note: If you're applying an image in compact mode with the /ScratchDir option, make sure your ScratchDir folder is not on a FAT32-formatted partition. Using a FAT32 partition could result in unexpected reboots during OOBE.
/EA	New in Windows 10, version 1607. Applies extended attributes.
/ApplyDrive	Specifies the logical drive, using the DeviceID. to get the device ID from the command line, type 'wmic diskdrive list brief'. Note: a VHD may appear with the name 'PhysicalDrive' in the description, for example, .PhysicalDrive2.
/SFUFile	Use /SFUFile to reference split FFU files (SFUs). Pattern is the naming pattern and location of split files.

Parameter	Description
/CaptureDir	Specifies the directory to which the image was applied and customized.
/ConfigFile	Specifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/Verify	Checks for errors and file duplication.
[/ConfirmTrustedFile	Validates the image for Trusted Desktop on a Windows 10, Windows 8.1, or Windows 8. This option can only be run on a computer running at least WinPE 4.0.

Parameter	Description
/CaptureDrive	The physical drive to be captured. You can use diskpart to get drive number information. Uses the format `.PhysicalDriveX`, where X is the disk number that diskpart provides.
/PlatformIds	Not needed for desktop capture. Specifies one or more platform ids (separated with semicolon) to be added to the image. If not specified, platform id will be '*'.
/Compress	Specifies the type of compression used for when capturing. If you'll be splitting the FFU, specify `none`, as DISM doesn't support splitting compressed FFUs.

Parameter	Description
/ConfigFile	Specifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/Compress	Specifies the type of compression used for the initial capture operation. The maximum option provides the best compression, but takes more time to capture the image. The fast option provides faster image compression, but the resulting files are larger than those compressed by using the maximum option. This is also the default compression type that is used if you do not specify the argument. The none option does not compress the captured image at all.
/Bootable	Marks a volume image as being a bootable image. This argument is available only for WinPE images. Only one volume image can be marked as bootable in a .wim file.
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/Verify	Checks for errors and file duplication.
/NoRpFix	Disables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside of the value specified by /ImageFile will not be captured.
/WIMBoot	Use /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/EA	Captures extended attributes. The switch must be explicitly specified to capture extended attributes. DISM will capture extended attribute bits if they are set in the components to be captured in the WIM image. If the bits are not set, DISM won't set them. Only the inbox components of CAB packages and drivers will have these extended attribute bits, not the AppX package components or Win32 application components. Extended attributes with prefix '$Kernel.' in name will be skipped because only user mode extended attributes are captured. If you use DISM in Windows 10, version 1607 to capture extended attributes and use an earlier version of DISM to apply the image, the operation will succeed but the extended attributes will not be set to the applied image.

Parameter	Description
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/Append	Adds the modified image to the existing .wim file instead of overwriting the original image. The /CheckIntegrity and /Append arguments do not apply to virtual hard disk (VHD) files.

Parameter	Description
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.

Parameter	Description
/SWMFile	Enables you to reference split .wim files. pattern is the naming pattern and location of split files. You can also specify wildcard characters. For example, 'E:imageinstall*.swm' will export the split files in the E:image directory named install1.swm, install2.swm, and so on.
/Compress	Specifies the type of compression used for the initial capture operation. The /Compress argument does not apply when you export an image to an existing .wim file, you can only use this argument when you export an image to a new .wim file. The maximum option provides the best compression, but takes more time to capture the image. The fast option provides faster image compression, but the resulting files are larger than those compressed by using the maximum option. This is also the default compression type that is used if you do not specify the argument. Use the recovery option to export push-button reset images. The resulting files are much smaller in size, which in turn, greatly reduce the amount of disk space needed for saving the push-button reset image on a recovery drive. The destination file must be specified with an .esd extension. The none option does not compress the captured image at all.
/Bootable	Marks a volume image as being a bootable image. This argument is available only for WinPE images. Only one volume image can be marked as bootable in a .wim file.
/WIMBoot	Use /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.

Parameter	Description
/ReadOnly	Sets the mounted image with read-only permissions. Optional.
/Optimize	Reduces initial mount time.
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.

Parameter	Description
/WIMBoot	configure an offline image for installing on a Windows image file boot (WIMBoot) system.
/Optimize	Reduces initial mount time. /Optimize-Image /WIMBoot only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. Only use /Optimize-Image with images that will be used for WIMBoot supported systems. If /Optimize-Image is used with a non-WIMBoot supported system image, Windows may not work as expected, after installation on a non-WIMBoot supported device.

Parameter	Description
/FileSize	Specifies the maximum size in megabytes (MB) for each created file. If a single file is larger than the value specified in the /FileSize option, one of the split .swm files that results will be larger than the value specified in the /FileSize option, in order to accommodate the large file.
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/ImageFile	Specifies the path of a .FFU file, example: flash.ffu.
/SFUFile	References split FFU files (SFUs). Pattern is the naming pattern and location of split files.

Parameter	Description
/FileSize	Specifies the maximum size in megabytes (MB) for each created file. If a single file is larger than the value specified in the /FileSize option, one of the split .swm files that results will be larger than the value specified in the /FileSize option, in order to accommodate the large file.
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/ImageFile	Specifies the path of an image file, example: install.wim.

Parameter	Description
/CheckIntegrity	Detects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/Append	Adds the modified image to the existing .wim file instead of overwriting the original image. The /CheckIntegrity and /Append arguments do not apply to virtual hard disk (VHD, VHDX), or FFU files.

Parameter	Description
/Path	Specifies the disk volume of the WIMBoot configuration.
/DataSourceID	Specifies the data source ID as displayed by /Get-WIMBootEntry.

Parameter	Description
/PackagePath	Specifies the path of a siloed provisioning package file.
/ImagePath	Specifies the path of the Windows image where you are applying the SPP.

ParameterDescription
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/ConfigFilespecifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/BootableMarks a volume image as being a bootable image. This argument is available only for Windows Preinstallation Environment (WinPE) images. Only one volume image can be marked as bootable in a .wim file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
/NoRpFixDisables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside of the value specified by /ImageFile will not be captured.
Example:
/Apply-FFUFor FFU, this command applies a Full Flash Utility (FFU) or split FFU (SFU) to a specified physical drive.
Syntax:
ParameterDescription
/ImageFileThe path and name of the FFU image file that will be applied
/ApplyDriveThe path to the phyisical drive that will be imaged
/SFUfileOptional, for split FFUs that are captured with no compression. Use /SFUFile to reference split FFU files (SFUs). Pattern is the naming pattern and location of split files. Use a wildcard character when specifying the naming pattern. For example, 'E:imageinstall*.sfu' will apply all of the split files in the E:image directory named install1.sfu, install2.sfu, and so on.
Example:
/Apply-ImageFor WIM, this command applies a Windows image file (.wim) or a split Windows image (.swm) files to a specified partition. Beginning with Windows 10, version 1607, DISM can apply and capture extended attributes (EA).
For FFU, this command applies a full flash update (.ffu) image to a specified drive. It doesn't support applying an image from a virtual hard disk (.vhdx) file, though you can use this command to apply a full image to a VHD. FFU applies to Windows 10 only. While you can use this command to apply an FFU, use /apply-ffu instead.
This option doesn't support applying an image from a virtual hard disk (VHD), though you can use this command to apply images to a .vhdx file that's been attached, partitioned, and formatted.
Arguments for WIM:
Arguments for FFU
See /apply-ffu.
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
/NoRpFixDisables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside the value specified by /ImageFile will not be captured.
/SWMFileEnables you to reference split .wim files (SWMs). Pattern is the naming pattern and location of split files. Use a wildcard character when specifying the naming pattern. For example, 'E:imageinstall*.swm' will apply all of the split files in the E:image directory named install1.swm, install2.swm, and so on.
/ConfirmTrustedFileValidates the image for Trusted Desktop on a Windows 10, Windows 8.1, or Windows 8. This option can only be run on a computer running at least WinPE 4.0. When using /Apply-Image with the /ConfirmTrustedFile option in WinPE, always specify the /ScratchDir option pointed to a physical media location. This ensures that short file names will always be available. See DISM Global Options for Command-Line Syntax for more information about the default behavior of the /ScratchDir option. Beginning with Windows 10, version 1607, you can use /EA to apply extended attributes.
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/CompactApplies an image in compact mode, saving drive space. Replaces WIMBoot. For Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) only. 
Note: If you're applying an image in compact mode with the /ScratchDir option, make sure your ScratchDir folder is not on a FAT32-formatted partition. Using a FAT32 partition could result in unexpected reboots during OOBE.
/EANew in Windows 10, version 1607. Applies extended attributes.
/ApplyDriveSpecifies the logical drive, using the DeviceID. to get the device ID from the command line, type 'wmic diskdrive list brief'. Note: a VHD may appear with the name 'PhysicalDrive' in the description, for example, .PhysicalDrive2.
/SFUFileUse /SFUFile to reference split FFU files (SFUs). Pattern is the naming pattern and location of split files.
Examples:
/Capture-CustomImageCaptures the incremental file changes based on the specific install.wim file to a new file, custom.wim for a WIMBoot image. You can't capture an empty directory. The captured files are converted to pointer files. The custom.wim is placed in the same folder next to the install.wim.
Important
/Capture-CustomImage only captures the customization files. It can't be used to capture installation files into a new WIM.
Keep the install.wim and custom.wim files together. Don't switch out either the custom.wim file or the install.wim file.
You can only capture the custom image once. Don't remove or recapture a custom.wim after capturing the incremental file changes.
Syntax:
ParameterDescription
/CaptureDirSpecifies the directory to which the image was applied and customized.
/ConfigFileSpecifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
[/ConfirmTrustedFileValidates the image for Trusted Desktop on a Windows 10, Windows 8.1, or Windows 8. This option can only be run on a computer running at least WinPE 4.0.
Example:
/Capture-FFUCaptures an image of a physical drive's partitions to a new .ffu file.
You can capture the image as a full flash utility image (.ffu) file or a set of split ffu (.sfu) files;
Syntax:
ParameterDescription
/CaptureDriveThe physical drive to be captured. You can use diskpart to get drive number information. Uses the format .PhysicalDriveX, where X is the disk number that diskpart provides.
/PlatformIdsNot needed for desktop capture. Specifies one or more platform ids (separated with semicolon) to be added to the image. If not specified, platform id will be '*'.
/CompressSpecifies the type of compression used for when capturing. If you'll be splitting the FFU, specify none, as DISM doesn't support splitting compressed FFUs.
Examples:
Capture a desktop FFU:
Capture a desktop FFU that will be split:
/Capture-ImageCaptures an image of a drive to a new .wim file. Captured directories include all subfolders and data. You cannot capture an empty directory. A directory must contain at least one file. DISM can also optionally apply and capture extended attributes (EA).
You can capture the image as a Windows image (.wim) file or a set of split Windows image (.swm) files, but this option doesn't support capturing a virtual hard disk (.vhd/.vhdx) file. See /Capture-FFU if you are looking to capture an FFU.
Syntax:
ParameterDescription
/ConfigFileSpecifies the location of a configuration file that lists exclusions for image capture and compress commands. For more information, see DISM Configuration List and WimScript.ini Files.
/CompressSpecifies the type of compression used for the initial capture operation. The maximum option provides the best compression, but takes more time to capture the image. The fast option provides faster image compression, but the resulting files are larger than those compressed by using the maximum option. This is also the default compression type that is used if you do not specify the argument. The none option does not compress the captured image at all.
/BootableMarks a volume image as being a bootable image. This argument is available only for WinPE images. Only one volume image can be marked as bootable in a .wim file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/VerifyChecks for errors and file duplication.
/NoRpFixDisables the reparse point tag fix. A reparse point is a file that contains a link to another file on the file system. If /NoRpFix is not specified, reparse points that resolve to paths outside of the value specified by /ImageFile will not be captured.
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/EACaptures extended attributes. The switch must be explicitly specified to capture extended attributes. DISM will capture extended attribute bits if they are set in the components to be captured in the WIM image. If the bits are not set, DISM won't set them. Only the inbox components of CAB packages and drivers will have these extended attribute bits, not the AppX package components or Win32 application components. Extended attributes with prefix '$Kernel.' in name will be skipped because only user mode extended attributes are captured. If you use DISM in Windows 10, version 1607 to capture extended attributes and use an earlier version of DISM to apply the image, the operation will succeed but the extended attributes will not be set to the applied image.
Examples:
/Cleanup-MountpointsDeletes all of the resources associated with a mounted image that has been corrupted. This command will not unmount images that are already mounted, nor will it delete images that can be recovered using the /Remount-Image command.
Example:
To learn more, see Repair a Windows Image
/Commit-ImageApplies the changes that you have made to the mounted image. The image remains mounted until the /Unmount-Image option is used.
Syntax:
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/AppendAdds the modified image to the existing .wim file instead of overwriting the original image. The /CheckIntegrity and /Append arguments do not apply to virtual hard disk (VHD) files.
Example:
/Delete-ImageDeletes the specified volume image from a .wim file that has multiple volume images. This option deletes only the metadata entries and XML entries. It does not delete the stream data and does not optimize the .wim file.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax:
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
Example:
/Export-ImageExports a copy of the specified image to another file. The source and destination files must use the same compression type. You can also optimize an image by exporting to a new image file. When you modify an image, DISM stores additional resource files that increase the overall size of the image. Exporting the image will remove unnecessary resource files.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax:
ParameterDescription
/SWMFileEnables you to reference split .wim files. pattern is the naming pattern and location of split files. You can also specify wildcard characters. For example, 'E:imageinstall*.swm' will export the split files in the E:image directory named install1.swm, install2.swm, and so on.
/CompressSpecifies the type of compression used for the initial capture operation. The /Compress argument does not apply when you export an image to an existing .wim file, you can only use this argument when you export an image to a new .wim file. The maximum option provides the best compression, but takes more time to capture the image. The fast option provides faster image compression, but the resulting files are larger than those compressed by using the maximum option. This is also the default compression type that is used if you do not specify the argument. Use the recovery option to export push-button reset images. The resulting files are much smaller in size, which in turn, greatly reduce the amount of disk space needed for saving the push-button reset image on a recovery drive. The destination file must be specified with an .esd extension. The none option does not compress the captured image at all.
/BootableMarks a volume image as being a bootable image. This argument is available only for WinPE images. Only one volume image can be marked as bootable in a .wim file.
/WIMBootUse /WIMBoot to append the image with Windows image file boot (WIMBoot) configuration. This only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. This feature isn't supported in Windows 10.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
Example:
/Get-ImageInfoDisplays information about the images that are contained in a .wim, .ffu, .vhd or .vhdx file. When used with the /Index or /Name argument, information about the specified image is displayed, which includes if an image is a WIMBoot image, if the image is Windows 8.1, see Take Inventory of an Image or Component Using DISM. The /Name argument does not apply to VHD files. You must specify /Index:1 for FFU and VHDX files.
Syntax:
Examples:
/Get-MountedImageInfoReturns a list of .ffu, .vhd, .vhdx, and .wim images that are currently mounted, as well as information about the mounted image such as whether the image is valid, read/write permissions, mount location, mounted file path, and mounted image index.
Example:
/Get-WIMBootEntryUse /Get-WIMBootEntry to display WIMBoot configuration entries for the specified disk volume.
For more information about how to display WIMBoot configuration entries, see Take Inventory of an Image or Component Using DISM.
This only applies to Windows 8.1; this feature isn't supported in Windows 10.
Syntax:
Image Capture Software FreeExample:
/List-ImageDisplays a list of the files and folders in a specified image.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax:
Example:
/Mount-ImageMounts an image from a .ffu, .wim, .vhd or .vhdx file to the specified directory so that it is available for servicing.
When mounting an image, note the following:
The mount directory must be created, but empty.
An index or name value is required for all image types. WIMs can contain more than image. For FFU and VHD, use index:1.
Right click on iphone. Syntax:
ParameterDescription
/ReadOnlySets the mounted image with read-only permissions. Optional.
/OptimizeReduces initial mount time.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
Examples:
/Optimize-Image /WIMBootPerforms specified configurations to an offline image.
ParameterDescription
/WIMBootconfigure an offline image for installing on a Windows image file boot (WIMBoot) system.
/OptimizeReduces initial mount time. /Optimize-Image /WIMBoot only applies to Windows 8.1 images that have been captured or exported as a WIMBoot file. Only use /Optimize-Image with images that will be used for WIMBoot supported systems. If /Optimize-Image is used with a non-WIMBoot supported system image, Windows may not work as expected, after installation on a non-WIMBoot supported device.
Example:
/Remount-ImageRemounts a mounted image that has become inaccessible and makes it available for servicing.
Syntax:
Example:
/Split-FFUFor FFU, this command splits an existing full-flash update (.ffu) file into multiple read-only split .sfu files. DISM doesn't support splitting compressed FFUs. If you are splitting FFUs, make sure that your FFU was captured with the /compress:none option specificed.
This option creates the .sfu files in the specified directory, naming each file the same as the specified /SFUFile, but with an appended number. For example, if you use c:flash.sfu, you'll get a flash.sfu file, a flash2.ffu file, a flash3.sfu file, and so on, defining each portion of the split .sfu file and saving it to the C: directory.
Syntax for FFU:
ParameterDescription
/FileSizeSpecifies the maximum size in megabytes (MB) for each created file. If a single file is larger than the value specified in the /FileSize option, one of the split .swm files that results will be larger than the value specified in the /FileSize option, in order to accommodate the large file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/ImageFileSpecifies the path of a .FFU file, example: flash.ffu.
/SFUFileReferences split FFU files (SFUs). Pattern is the naming pattern and location of split files.
Example:
/Split-ImageFor WIM, this command splits an existing .wim file into multiple read-only split .swm files.
This option creates the .swm files in the specified directory, naming each file the same as the specified path_to_swm, but with an appended number. For example, if you set path_to_swm as c:Data.swm, this option creates a Data.swm file, a Data2.swm file, a Data3.swm file, and so on, defining each portion of the split .wim file and saving it to the C: directory.
This command-line option does not apply to virtual hard disk (VHD) files.
Syntax for WIM:
ParameterDescription
/FileSizeSpecifies the maximum size in megabytes (MB) for each created file. If a single file is larger than the value specified in the /FileSize option, one of the split .swm files that results will be larger than the value specified in the /FileSize option, in order to accommodate the large file.
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/ImageFileSpecifies the path of an image file, example: install.wim.
Example:
/Unmount-ImageUnmounts the .ffu, .wim, .vhd or .vhdx file and either commits or discards the changes that were made when the image was mounted.
You must use either the /commit or /discard argument when you use the /Unmount-Image option.
Syntax:
ParameterDescription
/CheckIntegrityDetects and tracks .wim file corruption when used with capture, unmount, export, and commit operations. /CheckIntegrity stops the operation if DISM detects that the .wim file is corrupted when used with apply and mount operations.
/AppendAdds the modified image to the existing .wim file instead of overwriting the original image. The /CheckIntegrity and /Append arguments do not apply to virtual hard disk (VHD, VHDX), or FFU files.
Examples:
/Update-WIMBootEntryUpdates the WIMBoot configuration entry, associated with the specified data source ID, with the renamed image file or moved image file path.
Note:/Update-WIMBootEntry requires a restart in order for any updates to take effect.
Syntax:
ParameterDescription
/PathSpecifies the disk volume of the WIMBoot configuration.
/DataSourceIDSpecifies the data source ID as displayed by /Get-WIMBootEntry.
Example:
/Apply-SiloedPackageApplies one or more siloed provisioning packages (SPPs) to a specified image. This option is only available after running CopyDandI.cmd from the ADK for Windows 10, Version 1607, and running dism.exe /Apply-SiloedPackage from the target folder created by CopyDandI.cmd.
Note:/Apply-SiloedPackage can only be run once against a Windows image, but /PackagePath can used more than once in the same command to apply multiple SPPs. SPPs will be applied in the specified order, so a dependency should be specified before the SPP that depends on it.
For more information about siloed provisioning packages, and how to use CopyDandI.cmd, see Siloed provisioning packages.
Screen Capture PcTo find out how to work with siloed provisioning packages, see Lab 10: Add desktop applications and settings with siloed provisioning packages (SPPs).
ParameterDescription
/PackagePathSpecifies the path of a siloed provisioning package file.
/ImagePathSpecifies the path of the Windows image where you are applying the SPP.
Example:
Related topics Learning has never been so easy! 
Simplified instructions on capturing an image using the Microsoft Deployment Toolkit. Several assumptions are made in this document and are noted at the beginning.
The attached Word file is a complete copy of this How-to with better formatting.
 5 Steps total Step 1: Notes• These instructions assume you have a basic understanding of OS Deployments and the Microsoft Deployment Toolkit (MDT).
• The source (aka 'reference') computer you are capturing should be in a workgroup, not joined to your domain. Disjoin your domain before continuing if necessary.
• You must have the same OS you're trying to capture on the 'reference' computer loaded into MDT – if your source computer is running Windows 7 Enterprise with Service Pack 1 x64 then that DVD/OS must be loaded into MDT
• For these instructions the computer running MDT will be referred to as MDT1 and the deployment share will be Deploymentshare$
• These instructions will not include hitting 'Next', etc. unless that is the only action on a screen
MDT_Capture_Image.docx
Step 2: Prepare your source (reference) computerInstall your operating system and any other customizations on the computer you are going to capture.
Step 3: Set-up MDT to capture your image1. Open MDT, then expand Deployments, then expand your deployment share
2. Right click 'Task Sequences' and select 'New Task Sequence'
 a. Task Sequence ID: Capture
 b. Task Sequence name: Capture Image
3. Select the 'Sysprep and Capture' Task Sequence template
4. Select your Operating System
5. Do not specify a product key at this time
6. OS Settings screen – modify as desired
7. Admin Password - enter the password you wish for the local administrator account
8. Continue until you get a Finish button to click
9. Right-click your deployment share and select 'update deployment share'
Step 4: Capture your image by running the task sequence1. Log in to the computer you are trying to capture
 a. Typically this would be with the local administrator account since the computer should not be joined to the domain and usually during the build process local accounts are not added
2. Open a CMD windows and enter the following
 a. Net use * MDT1Deploymentshare$
 b. When prompted enter credentials for a user who has Write permissions to the MDT1Deploymentshare$ folder in the format of: domainuser
 i. Note: typically this would be a user with Domain Administrative rights
 c. When prompted enter the password for the user entered above
3. Enter the following to run the Litetouch sequence
 a.  MDT 1Deploymentshare$scriptslitetouch.vbs
 b. Depending on your deployment share is set-up (i.e. which screens to skip) you may need to select 'Deploy Computer', enter a username and password, etc.
 c. When you get to the Task Sequence window select your 'Capture Image' sequence
 d. Select the 'Capture an image of this reference computer' option
 i. It should default the MDT shareCaptures folder and a default file name
 e. Once the sequence starts running it will reboot into WinPE, Sysprep and capture the image for you. The image will be placed here:  MDT 1Deploymentshare$Captures 
 i. NOTE: Be patient – depending on how large the image is this can take a while
Step 5: Import your Captured ImageIn order to use your custom image you must import it into your Deployment Share's Operating Systems folder. Once there it becomes available under the 'InstallInstall Operating System' sectiontask in your Task Sequence
1. Open the Microsoft Deployment Toolkit program
2. Expand the Deployment Shares, then your deployment share until you see the 'Operating Systems' folder
3. Right-Click 'Operating Systems' and select 'Import Operating System'
4. Select 'Custom image file' 
5. Browse to the folder that contains your custom image file – typically this would be the 'Captures' folder on the computer running MDT
6. Double-click the captured WIM file to select it and return to the prior screen
7. Select the 'Move the files to the deployment share….' checkbox in order to save space in your deployment share
8. Setup files are not needed
a. The setup files are contained in the ISO/DVD version of the operating system you should have imported to the Deployment Share previously
9. Destination folder name
a. It will be helpful later if use a unique name such as Gold-2015-01-08 for the folder name 
After running these steps you should have a custom Windows Image file (.WIM file) that you can deploy to your computers.
Updated 1/8/2015 to include the 'Import your captured image' step (also included in the attached document).
 Published: Dec 09, 2013 · Last Updated: Jan 08, 2015 
37 CommentsSonora
mikemike2 Jan 5, 2015 at 05:31pm 
I am trying to run this process on Asus T100 i folllow all steps however process fails with 20 errors i need help. I took screen shot of errors but cannot post here ? 
Jalapeno
ToledoTown Feb 17, 2015 at 10:09pm 
I had to run the net use command to get past initial errors. Doesn't make much sense to me..
Sonora
Brandon Russell Aug 3, 2015 at 03:34pm 
After I run the litetouch.vbs command the process runs but I never receive the 'Capture an image from this reference computer' option. It just closes out and goes back to the desktop. Please help!!!
Cayenne
DHeck1961 Aug 3, 2015 at 03:41pm 
Try setting the Share and Security permissions on the folder where the captured WIM file is being saved to Everyone with Full permissions. I've had issues on occasion getting the capture to run and that usually fixes it.
Sonora
Brandon Russell Aug 3, 2015 at 04:07pm 
Just tried that, it still did not work. I am at a total loss with these capture images, I have been working on this process for a month with no luck. >:0
Anaheim
Eli.G Aug 10, 2015 at 08:14am 
Brandon, 
1st i recommend making the reference computer on a virtual machine, so if you have problems you can always load the snapshot.
2nd, when you stat the script, you will see under c: a folder name MININT.
open the BDD log and with trace32 (can be found with ConfigMgr 2007 Toolkit V2) [https://www.microsoft.com/en-us/download/details.aspx?id=9257]
you will get more info view that log.
if you made changes to bootstrap.ini you can comment all of them by adding # at the beginning of each line and try again.
If no go, please post your log here or send a link to where you uploaded this log
Pimiento
marksimpson2 Aug 27, 2015 at 02:50pm 
Getting the same fail as Brandon. Noticed in the bdd.log the process was looking for a non existant folder for the ts.xml file. I renamed the folder from to what it was looking for (a folder with the same name of the wim image???). It fails again but this time the MININT folder is absent.
Cayenne
DHeck1961 Aug 27, 2015 at 03:11pm 
The Bootstrap.ini file is in the Deployment Share folder - look in the 'Control' folder. 
One other issue that can occur when trying to capture an image is that a 'full set' of OS files (i.e. an import from the ISO or DVD) must be in the MDT share before you try to capture. The 'Full set' of files includes all the setup files (including Sysprep) which are required. If your custom image to capture is Windows 7 SP1 x86 then you must have that ISO/DVD loaded as an operating system.
As mentioned above by Eli.G - it's always best to work with Virtual Machines - I put a 'pause' in the capture sequence just before Sysprep runs so I can take a Checkpoint (Hyper-V) or Snapshot (VMWare) of the workstation. If the capture fails you can jump back in time to the Checkpoint/Snapshot, resolve the error and then try the capture again without having to rebuild your entire custom image from scratch.
Pimiento
marksimpson2 Aug 28, 2015 at 09:04am 
Great advice, thanks. My work machine is a little under specced which is why I haven't gone virtual. That makes a lot of sense though.
I'm thinking the problem must be with my imageunattend.xml or the settings in Deployment Workbench, although I created a capture image recently from an identical source without issue. 
Cayenne
DHeck1961 Aug 28, 2015 at 12:18pm 
Always fun when it works one day, but not the next, eh?
Any error messages?
Other things that have tripped me up during a capture include permissions on the drive/share where the capture file is being saved (both file and share permissions). Since it did work for you before it doesn't sound like a permissions issue. Lack of free drive space on the target drive is another one that's burned me before - checking that is one of the reasons I put a Pause in the Task Sequence right before Sysprep.
In case you're not familiar with pausing the Task Sequence - they have a built in script that will do it for you. Just add a standard 'Run command line' item to your Task Sequence where you want it to pause and for the 'command line' use the following (including the double quotes): cscript.exe '%scriptroot%LTISuspend.wsf'
New horizons animals. It will give you a message on screen that your sequence is paused (it disappears after a few seconds) and leaves an icon on the desktop to resume the sequence. Once you're done reviewing the build or doing any manual tasks you need to accomplish (checkpoint/snapshot a VM for example) simply double-click the icon to continue.
Pimiento
blchapman Sep 3, 2015 at 01:15pm 
Thanks! I followed the instructions and everything is working great. I'm in the process of putting MDT and WDS into production now :-)
Pimiento
baghavansingh Oct 5, 2015 at 07:23am 
I been working in production environment. what we are trying is capture a reference image with all the user settings. but when I try to sysprep with default settings in MDT 2013 it clean up all the user settings and gives me fresh boot!!! what i need is 1 reference image with all the settings to multiple clients.. ( Hope you all know Terrabyte unlimited it take image backup with all the settings and file . while restore it gives me the same state of backup ) Please help me to do the same in MDT 2013 .. and im running on windows server 2012 R2
Pimiento
IHSDUBAI Jan 13, 2016 at 12:28pm 
@toledotown I had to run the net use command to get past initial errors. Doesn't make much sense to me..
Same here! Anyway thanks to the OP. It helped me a lot. 
Pimiento
f4rr3ll Feb 8, 2016 at 06:41pm 
Brandon I was having similar problems, just in case anyone else is, make sure in your Deployment Share>Properties>Rules you have 'SkipCapture=NO' mine was defaulted to 'YES' so I wasn't getting the capture prompts. Hope this helps!
Poblano
DavidDartz Jul 21, 2016 at 11:09pm 
Hi All,
I have followed these instructions to the letter however I am stuck at 4.c (When you get to the Task Sequence window select your 'Capture Image' sequence). The 'LiteTouch.vbs' script definitely runs, and a number of dialog boxes flash up on the screen however I am never presented with the option to to choose a task sequence.
If anybody can offer any advice on how to get the Task Sequence to display it will be greatly appreciated.
Kind Regards,
Davo
prev
1
2
3
next