Capture Windows 10 Image using MDT 2013

In this article we are going to show you how to capture reference Windows 10 image using Microsoft Deployment Toolkit (MDT). Later you can use deploy this Windows 10 image on multiple computers in your organization.

By using a fully customized Windows 10 image for deployment on computers, you can achieve a quick installation of the operating system with a set of necessary applications on the users’ workstation.

We assume, that you are already familiar with article Deploy Windows 10 using MDT 2013 and WDS and have already installed MDT on your Windows Server 2012 R2/2016/2019.

Note. When capturing a Windows 10 image, always install the latest version of the Windows ADK (Windows Assessment and Deployment Kit) on your Windows Server with the Microsoft Deployment Toolkit role installed. For example, to capture a Windows 10 v2004 image, you need to install the Windows ADK for Windows 10 2004.


Preparing Windows 10 Reference Computer for MDT Capture

Before you begin to capture Windows 10 image, you should prepare already deployed Windows 10 PC by installing required drivers, apps, latest Windows security updates, and performing necessary system configuration. This computer will be used to capture the Windows image.

Let’s take a look at the basic steps to follow when configuring a Windows 10 reference computer.

  1. Install Windows 10 Pro or Enterprise edition on a reference computer;
  2. Install device drivers;
  3. Enable .NET 3.5 Framework support (use the DISM command: Dism /online /Enable-Feature /FeatureName:”NetFx3″);
  4. Use Windows Update to download and install the latest security fixes;
  5. Remove unnecessary built-in Universal Windows Platform (UWP) apps (otherwise the sysprep mail fail). You can use the following PowerShell script to remove some of the unnecessarily Windows 10 built-in Window Store Apps, like Xbox, Games, etc:
    $AppsList = "Microsoft.3DBuilder","microsoft.windowscommunicationsapps","Microsoft.MicrosoftOfficeHub","Microsoft.SkypeApp","Microsoft.Getstarted","Microsoft.ZuneMusic","Microsoft.MicrosoftSolitaireCollection","Microsoft.ZuneVideo","Microsoft.Office.OneNote","Microsoft.People","Microsoft.XboxApp", "Microsoft.Messaging", "Microsoft.Microsoft3DViewer", "Microsoft.WindowsFeedbackHub", "Microsoft.GetHelp", "Microsoft.OneConnect"
    ForEach ($App in $AppsList)
      $PackageFullName = (Get-AppxPackage $App).PackageFullName
      $ProPackageFullName = (Get-AppxProvisionedPackage -online | where {$_.Displayname -eq $App}).PackageName
    if ($PackageFullName)
       remove-AppxPackage -package $PackageFullName
    if ($ProPackageFullName)
            Remove-AppxProvisionedPackage -online -packagename $ProPackageFullName
  6. Install Visual C++ Redist, office applications and other tools that your users use;
  7. Customize Windows Start Menu and Taskbar pinned apps and copy setting to new user profiles:
    $Path = "C:\PS\StartLayout.xml"
    Export-StartLayout -path $Path
    Copy-Item $Path -Destination “C:\Users\Default\AppData\Local\Microsoft\Windows\Shell”
  8. Disable MSFT Consumer Experience, First Logon Animation and Windows Defender(if third party security solution is used). Use the following PowerShell commands:
    # Disable the Microsoft Consumer Experience
    New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\ -Name CloudContent
    New-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\CloudContent' -name 'DisableWindowsConsumerFeatures' -PropertyType DWORD -Value '1'
    # Disable First logon Animation
    New-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System' -name 'EnableFirstLogonAnimation' -PropertyType DWORD -Value '0'
    #Disable Windows Defender
    Set-MpPreference -DisableRealtimeMonitoring $TRUE
    New-ItemProperty -Path “HKLM:\SOFTWARE\Policies\Microsoft\Windows Defender” -Name DisableAntiSpyware -Value 1 -PropertyType DWORD -Force
  9. Cleanup WinSXS component folder on Windows 10 using DISM:
    dism /Online /Cleanup-Image /AnalyzeComponentStore
    dism /online /Cleanup-Image /StartComponentCleanup
  10. Run Disk Cleanup for system drive C:, remove temporary files, delete the Windows Update cache (C:\Windows\SoftwareDistribution\download folder).

Creating Capture Task Sequence on MDT

The first step is to create a new Task Sequence, which will control the image capturing process.

  1. Run Deployment Workbench console and expand the branch Deployment Shares > MDT Deployment Share;
  2. Right click on Task Sequence and select New Task Sequence in the appeared menu;
    mdt capture image
  3. This starts the Task Sequence Wizard. Enter Task Sequence ID (w10Capt) and Task Sequence Name (Capture Windows 10 Image);
    capture windows 10 image
  4. Select Sysprep and Capture from list of predefined task sequence templates and click Next;
    mdt capture image windows 10
  5. Choose an operating system that matches the version of OS installed on a reference computer. In this case, it is Windows 10 Pro x64 install.wim (the operating system must be pre-imported into MDT);
    mdt sysprep and capture
  6. Choose Don’t specify a product key at this time and press Next;
    how to capture windows 10 image
  7. Fill the fields Full Name and Organization and click Next;
    capture windows 10 image mdt
  8. Select Don’t specify an Administrator password at this time;
    capture image mdt
  9. On Summary page click Next > Next > Finish;
    mdt capture windows 10

Important! Before continuing, check that MDT server configuration allows to capture OS image. To do this, open MDT Deployment Share properties and switch to the Rules tab. SkipCapture option must be set to NO.

mdt image capture

Update deployment share to regenerate boot media with WinPE environment.

How to Capture Windows 10 Reference Image with Microsoft Deployment Toolkit (MDT)?

Now you are ready to capture already installed Windows 10 image on a client computer. Power on PC and boot Windows 10 as usual. Verify that necessary applications, updates, and language packs are installed on Windows, Time Zone is configured and check other Windows settings.

  1. Open File Explorer and specify the network path to the DeploymentShare on MDT server. In our case, the path looks like this: \\\deploymentshare$. You may need to enter credentials to access shared network folder on the MDT server
  2. Open the folder Script, find and run (by double click) the script file LiteTouch.vbs
    capture image with mdt
  3. Wait until Windows deployment Wizard starts;
  4. Select Capture Windows 10 Image (we created it earlier) from the task sequence list;
    capture image windows 10
  5. Enter current local Administrator password, which will be used to logon Windows after reboot;
    capture image using mdt
  6. Select Capture an image of this reference computer and verify the UNC path to the folder on MDT server, which will be used to save Windows 10 WIM image file (in our case \\\deploymentshare$\Captures. You should have read/write NTFS permissions on this folder. After that specify the new .wim file name;
    capture image mdt windows 10
  7. On the next screen you need to enter the domain credentials to access shared folder on the MDT server over the network;
  8. Wait for some time to start Task Sequence;
  9. After completing the preparations, Sysprep task starts. Then the computer will reboot into WiNPE environment and begin to capture system image (during the process of image creating, the system will switch in the OOBE (Out-Of-Box Experience) sysprep mode, and the Windows 10 image is captured using the DISM tool); Note. Your Windows reference computer will boot from the LiteTouchPE_x64.iso boot image (with WindowsPE environment) located in the Boot folder in the Deployment Shar on the WDS server.
    mdt capture
  10. The process of capturing Windows 10 image takes quite a long time and after finished a wim file with Windows 10 image appeared in the Captures folder on the deployment share

Tip. If you want to make changes to the local administrator’s profile before capturing the reference image, you need to use the MDT parameter – CopyProfile=TRUE. These changes will be transferred to the WIM system image and applied to the user’s profile when you deploy a Windows 10 image on the target computer. The CopyProfile option allows you to make changes to the local administrator profile when configuring your reference Windows 10 device. They are then transferred to a .wim file during image capture and can be applied to the default user profile on deployed machines. Otherwise, any changes made to the user’s profile won’t be saved (such as wallpaper, desktop icons, Windows theme setting, etc.).

Later you can directly import this WIM file to the System Center Configuration Manager, Windows Deployment Services or MDT and use it to deploy Windows 10 to the workstations. Thus, you save a lot of time when installing drivers and applications on multiple computers.

Capture Image Window Task Sequence not Showing in the Deployment Wizard

In some cases, step 3 (Capture image) with the option to select the start of image capture doesn’t appear on client computers. The Windows Deployment Wizard simply skips the step in which you must select the “Capture an image of this reference computer” option. Instead, the user is prompted to specify computer details.

windows 10 capture image


If this problem appeared after upgrading the MDT version, then most likely it is related to a bug that has been confirmed by Microsoft Premier support. The version of the script ZTIUtility.vbs contains an error. To fix it, you need to manually edit the ZTIUtility.vbs file, find the lines:

If (oTS.SelectSingleNode("//step[@type='BDD_InstallOS']") is nothing) and (oTS.SelectSingleNode("//step[@type='BDD_UpgradeOS']") is nothing) then

And replace with:

If (oTS.SelectSingleNode("//step[@type='BDD_InstallOS' and @disable='false']") is nothing) and (oTS.SelectSingleNode("//step[@type='BDD_UpgradeOS' and @disable='false']") is nothing) then

Open the customsettings.ini file and make sure that the option is selected:




In addition, there is information that the capture window doesn’t appear if the parameter is specified:


Change it to SkipProductKey=YES, or edit the DeployWiz_ProductKeyVista.vbs file. Replace the line of code:

if oProperties("DeploymentType") = "UPGRADE" then

Change to:

if Property("DeploymentType") = "UPGRADE" then

After that, run the Capture task sequence again on the client computer, and make sure that the Capture Screen now appears in the Deployment Wizard.

I enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.
Latest posts by Cyril Kardashevsky (see all)


    1. Yes, it’s possible. But at first you have to integrate all the necessary drivers to Windows 10 image. You can do this through the MDT task sequence or directly to the wim file using dism.

    1. You can get it from the sources path, the file is called install.wim and check the indexes of it because most of these install.wim files have several indexes and each one correspond to a different version of the OS. i.e. index 1 home, index 2 pro, index… workstation pro

  1. I had the problem with “the Capture Image Window not Showing” the ZTIUtility.vbs fix worked for me.
    you are a genius !

  2. Hello, I cannot for the life of me capture an image or even have it prompt me for it in the Deployment wizard. All i have is Ready under the task Sequence in the Windows Deployment Wizard. I’ve checked all the scripts and the Rules but I can’t see the problem. Any ideas?

  3. See where it says to enter the Administrator password which is going to be used to enter Windows after reboot does not come up on my screen it just says”specify the network credentials” doesn’t accept the local admin account , only accepts the MDT admin account :

    I think the issue with the discrepancy between the local admin account of the machine to be captured and the admin account of MDT.

    From the donor machine I can successfully drill into the deployment share\scripts\Litetouch VBS then credentials screen pops up asking to enter the credentials to access the network share this obviously is the MDT admin account so I enter it and move next, then goes through Bootstrap and asks for credentials again saying “Specify credentials for connecting to network shares”. On some documentations this is the local administrator account to be used to access the donor machine after the reboot to continue with the capture process (after the sysprep goes through and machine reboots)

    When I enter the donor machine local admin account credentials it says wrong (but looks for the donor machine admin account after the reboot?), only accepts when the MDT server admin account details entered and moves to the next step. Then the machine goes through some process and reboots and I can see the system is trying to access the machine with the same details entered (the MDT administrator account) earlier were I think it should have been the local machines admin account which is not accepted?

    The other problem is that the local admin account is disabled but I have enabled it just to see if that was the issue but no luck. Also created an identical account on both the server and client with same passwords, both admins on server AND donor client, then the process just stalls after accepting the credentials. Really driving me nuts.

    The interesting thing is that when I do a fresh deployment I can capture that with no issues because the local and server admin accounts are the same (assuming that is the issue)

    this only happens when trying to capture an image which wasn’t deployed by the MDT server.

    Any help would be greatly appreciated

  4. Anyone figure this out? I’m working with Windows 10 version 21H2 and when I get to the Sysprep option and the unit reboots, I get an error that the DeploymentShare$ can’t be contacted, possibly invalid credentials. I can ping the server but the server cannot ping the machine from the server at this point. Once it fails, it changes the name of the donor computer and I have to start all over.
    I re-did the task sequence and took out the sysprep and the reboot unit sequences but my capture is only about 4,000Kb not near enough for the machine I’m working on.
    I can deploy 21H2 out to machines, but I cannot capture an image of a finished and prepped unit for cloning others on the network. My sanity is fading fast on this, and I’m about ready to build a FOG server and go back to what I know.
    I have version MDT 6.3.8456.1000 and both ADK’s are version 10.1.22000.1

  5. I had this headache Brian then realised I needed to change all references of “WDSSERVER1” to the IP address in any UNC path. so Right click your deploymentshare folder in MDT, select properties and change the path in the “General” tab and then make sure the Bootstrap.ini matches it. (\\\DeploymentShare$)
    Then regenerate the images etc.
    This worked for me after going round in circles for ages.

  6. It’s better practice to write Name of server not IP as for path. because IP can change often the Name does
    example; \\wds-server-mc1\deploymnetshare$ . better then\deploymentshare$

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.