MDT 2013 Update 1 Release Notes and Known Issues

9/15 Update: We have re-released MDT 2013 Update 1. Please see this post with revised release notes and updated known issues.

The following information is deprecated, but kept live for historical reference.


This post is to serve as the release notes and known issues list for the current release of MDT 2013 Update 1 (v6.3.8290).

The list of known issues below provides a number of workarounds that are currently available to help unblock affected customers. We will revise the list as needed. Given the number of issues with this build we will release a newer build of MDT 2013 Update 1 in the next several weeks to address as many of these issues as we can. Watch this blog for more information.

Release Notes

TechNet documentation is not updated

The MDT product documentation published on TechNet is current as of MDT 2013; it has not yet been updated for MDT 2013 Update 1.

Do not upgrade from Preview to RTM

MDT 2013 Update 1 Preview should be uninstalled before installing the final MDT 2013 Update 1. Do not attempt to upgrade a preview installation or deployment share. Although the product documentation is not updated for MDT 2013 Update 1, the information on upgrading an installation still holds true.

Windows System Image Manager will fail to validate MDT Unattend.xml templates

The Windows System Image Manager (WSIM, a component of the Windows ADK used to create and modify unattended installation answer files) does not allow blank values which exist in the default MDT Unattend.xml templates. MDT removes blank values before injecting the file during deployment, so Windows always receives a valid XML answer file.

Integrating with System Center Configuration Manager

When integrating MDT with Configuration Manager, follow the version of the Windows ADK. MDT 2013 Update 1 only works with the Windows 10 ADK, so make sure it is used with a version of Configuration Manager that supports and also uses the Windows 10 ADK.

Image files larger than 4 GB are not split by default

Split image (.SWM) support is now off by default. It must be enabled by modifying %DeployRoot%\Control\Settings.xml with the following:


Using HideShell with Windows 10

The behavior of the HideShell option changed with Windows 10. Michael Niehaus explains this in great detail on his blog.

Known Issues

Disk partitioning issues


  • Recovery partition consumes the majority of the disk on BIOS systems
    • LTIApply fails with DISM error 112, There is not enough space on the disk.
  • Recovery partition is unnecessarily visible on both UEFI and BIOS systems
  • You can’t specify a custom partition layout containing a recovery partition for UEFI systems

Workarounds: Keith Garner provides some suggestions on his blog: uberbug06 and uberbug07.

Static IP not restored when using media deployment

When doing a media deployment and using a static IP the static IP does not get restored.


  • Modify Litetouch.wsf to enable MEDIA deployments (Keith Garner explains in this forum post)
  • Add an extra Apply Network Settings action (alternative suggested by Johan Arwidmark on his blog)

Static IP not set in Network Adapter Configuration Wizard

When initializing a deployment in Windows PE and clicking Configure Static IP Address, if you uncheck Enable DHCP and enter static IP information, the following Network Settings Error will display:

WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147467259

This warning may also be seen in the results screen and log files during a deployment.

Workaround: a static IP can be manually set from Windows PE using netsh, but otherwise there are no workarounds at this time.

Monitoring does not work after Windows 10 upgrade

After successfully upgrading a system to Windows 10 the MDT monitoring fails to report information. You will see the following warnings:

Unable to create WebService class

Workaround: None.

MDAC component fails being added to Windows PE

This is a known bug with DISM; it is external to MDT. DISM can sometimes fail to add the MDAC component to WinPE boot images. This seems to be a timing issue which most commonly occur when you are using SSD disks.


  • Remove MDAC. On the deployment share properties, Windows PE tab, Features subtab, uncheck Microsoft Data Access Components (MDAC/ADO) support.
  • If you need MDAC for database connectivity, you can try updating your boot images from a system where the %TMP% directory is located on a non-SSD drive. This is not a guaranteed workaround, but has been seen to work.

NOTE: we are also aware of reports of similar issues regarding Windows PowerShell and WMI components in Windows PE (as well as some functional issues with these components). We have not been able to reproduce these issues, and are working with the Windows team to investigate further. If you have a reproducible issue with these components in Windows PE, please open a case with Microsoft Support to troubleshoot.

Upgrade task sequences are displayed when not applicable

Windows 10 upgrade task sequences are available when starting a deployment from Windows PE or on a non-matching architecture, however the in-place upgrade scenario is only supported when started from the full OS (it cannot be started from Windows PE) and from the correct architecture.

Workaround: Modify your upgrade task sequence properties to exclude client platforms that are not applicable. On the task sequence properties, General tab, select This can run only on the specified client platforms and then choose platforms that you want to target, for example, All x86 Windows 7 Client. This example will exclude Windows PE and Windows 7 x64 systems.

Applications with a command file (.cmd) use a Windows system working directory

If you have an application that uses a command file (.cmd) as the installation command line it will be launched from C:\Windows\System32 instead of the application’s working directory.

Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.

Application bundles successfully install but log an error

Application bundles will successfully install but the following warning is logged in ZTIApplications.log:

SelectSingleNodeString(CommandLine) Missing Node.

as well as the following error:

Application <app bundle name> returned an unexpected return code: 87

Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.

Deployment Wizard error for Keyboard Locale

Changing the keyboard locale in the Deployment Wizard will result in a script error:

Type mismatch: 'SetNewKeyboardLayout'

This error is non-fatal. Click Yes and continue.


  • Specify the keyboard locale in CustomSettings.ini and hide this wizard page.
  • Edit %DeployRoot%\Scripts\DeployWiz_LanguageUI.xml to remove onchange="SetNewKeyboardLayout" from line 62.

ZTI: Offline installation of language packs or software updates fails

Using the "Install Language Packs Offline" or "Install Updates Offline" step in an MDT-integrated task sequence in Configuration Manager results in the language packs or updates not injected, and the following errors in the ZTIPatches.log:

ZTI ERROR - Unhandled error returned by ZTIPatches: Object required (424)

This error is only seen in logs, the deployment appears to be successful otherwise.

Workaround: apply updates and language packs online

Split image files do not apply

If you split a large image file to create .SWM file(s), then applying this split image file will fail.

Workaround: edit %DeployRoot%\Scripts\LTIApply.wsf, both lines 915 and 918, to add a colon and remove a space, for example on line 915 change:

sCmd = sCmd & " /SWMFile """ & sRWMPath & """"
sCmd = sCmd & " /SWMFile:""" & sRWMPath & """"

Do the same on line 918.

Deployment fails due to unattend.xml errors during oobeSystem

If you have edited unattend.xml and then start a deployment with the wizard page for administrator password enabled, or specified AdminPassword in CustomSettings.ini, the deployment will fail during Windows OOBE:

Windows could not parse or process Unattend answer file [C:\Windows\Panther\unattend.xml\ for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows=Shell-Setup].

Workaround: edit %DeployoRoot%\Scripts\ZTIConfigure.wsf lines 343 and 344 to append unattend: before PlainText. For example, on line 344 change:

oCurrent.parentNode.selectSingleNode("PlainText").text = "true"
oCurrent.parentNode.selectSingleNode("unattend:PlainText").text = "true"

Do the same on line 343.

ZTI: LTIBootstrap.vbs script not found

Towards the end of a MDT-integrated task sequence deployment in Configuration Manager a Windows Script Host popup will appear with a message similar to the following:

Can not find script file "C:\LTIBootstrap.vbs".

(The drive letter may be different depending upon the specific scenario.)

Workaround: Script changes are possible but difficult and challenging. Johan Arwidmark provides an option on his blog (see Issue #2).

LTI: Cleanup is not complete after image capture

After capturing an image and rebooting back to the drive, autologon is still configured and an error will appear about LTIBootstrap is not found. This is a minor, non-fatal error that does not affect the captured image.

Workaround: Script changes are possible but difficult and challenging, especially given the minor severity of the issue.

DISM returns error 87 when applying image

A deployment fails with the following error from DISM:

Error: 87 (The parameter is incorrect)

With further detail in the dism.log:

Failed to get the filename extension of the image file

Workarounds: This is seen when the server name is only two characters, for example DC, such that the /ImageFile parameter is similar to the following:

"\\dc\DeploymentShare$\Operating Systems\Windows 10 Enterprise x64\sources\install.wim"

Use a deployment share on a server whose name is three or more characters.

If you must use a server with a two-character name, specify its fully qualified domain name in bootstrap.ini, for example


Comments (95)
  1. Max says:

    Thank you.

  2. Hatschim says:


  3. Todd Stephens says:

    So I have to ask… When will we be getting a working version of MDT to replace this patched and broken one? Seems odd that the "release" version of MDT that "supports" Windows 10 is so broken. I use this for enterprise customers and this amount of work
    arounds and bugs is unacceptable.

  4. Claire Roberts says:

    Is this a known issue too?

    Updating the deployment share fails on copying background.bmp saying the file is being used by another process. I have even built a new server 2008 R2 and put just the Windows 10 ADK and MDT 2013 Update 1 on it with nothing in the deployment share and the update
    fails with this error. Had no issues on the preview releases!

  5. ivan says:

    I get a "Litetouch deployment failed, Return Code = -2147467259 0x80004005" error when deploying Windows 10 Pro x64 EN from a VLSC original ISO.
    Apart from the error all drivers installed fine, so I’m not sure whats really broken.

  6. JaredCEG says:

    I’m having the same issue as Ivan, except mine is on Windows 8.1. Windows 7 worked fine. However, I’ve found that it works on a VM.

  7. A. Feiner says:

    its time to hand the MDT team back to Michael Niehaus / Keith or give Johan Arwidmark the development because this is not your father’s MDT!,

  8. Dan M says:

    I am getting the same error as Ivan as well. It manifests when I deploy windows 7 64b including an image I captured this morning with the new MDT and ADK. Other then the error message there seems to be nothing wrong.

  9. @ Todd, It says there will be an update in a few weeks right in the post: "Given the number of issues with this build we will release a newer build of MDT 2013 Update 1 in the next several weeks to address as many of these issues as we can. Watch this
    blog for more information."

  10. Turge says:

    Maybe re-add the progress bar when applying/capturing a WIM? Seems kind of important, especially for a process that could literally take an hour with a slower connection.

  11. Todd Stephens says:

    @Justin… seeing that this is the release version of MDT that "supports" Windows 10 it shouldn’t have all these issues. Microsoft should have tested it, found these problems and NOT released it until it was done. Also, "several" doesn’t actually say when
    the next release will be. Several is simply more that 2. So sometime after 2 more weeks we will get a new version isn’t a good answer. The post also doesn’t say that these issues will be fixed, only that "as many of these issues as we can" will be fixed. So
    my questions still stands. When will a working version of MDT be released? This is unacceptable.

  12. pan123sel says:

    I completely agree with Todd, this version is full of bugs and too much of work for enterprises.

  13. JoeZeppy412 says:

    My MMC hangs every time I try to broswes for the path to the Extras folder or the background wallpaper under WinPE properties. Anyone seeing that?

  14. Max says:

    @#Turge, DISM in its current state does not provide them with progress output. I believe I saw somewhere on the Connect portal that they have a request in with the Windows team at Microsoft to add that functionality to DISM.

  15. Max says:

    My biggest issue is the amount of customizations I have to redo to some of the scripts due to them getting overwritten every time there is an update.

  16. @Ivan – please file an item on Connect with logs. Need more detail to determine.

    @Turge – My response from We made a conscious decision to switch to DISM. ImageX is deprecated. We have a DCR filed with Windows to provide better process output from DISM.

    @JoeZeppy412 – this is an old known issue with the MMC. When opening that pane, do the explicit change you need to make and then close it. Clicking around the page will cause it to hang. Reference

    To everyone else to which I’m not responding directly: thank you for your feedback and your passion for MDT. It’s not going unheard, I’m just not going to respond to every single comment. We strive to meet a wide variety of customer needs for this free tool,
    try to be as transparent as possible due to the rich community involvement, and will continue to iterate and invest in the product with your feedback.

  17. Todd Stephens says:

    Sorry @Aaron but you can’t really bring up the "free tool" thing. When an enterprise is paying many thousands of dollars for Software Assurance the tools Microsoft offers to deploy said software needs to work out of the box. It’s just that simple. Microsoft
    can’t fall back on "well it’s free, so deal with it". Anyway, I’ve said enough.

  18. tony says:

    I am experiencing a system license violation error BSD after deploying an in-place upgrade to Windows 10 on Windows 7/8.1 computers. Upgrade seems to work fine. Reboots and I can log in to the upgraded OS for the first time. After second reboot, system
    license violation blue screen. I am using KMS in my org. Upgrading manually without MDT 2013 U1 works fine.

  19. adam says:

    Would be nice if MDT brought back the Settings Per Task Sequence capability that was in MDT 2010.

  20. adam says:

    On the error of "Can not find script file "C:LTIBootstrap.vbs"." I found that is referenced in unattend.xml, simply deleting it fixes it.

    As far as the "Windows could not parse or process Unattend answer file [C:WindowsPantherunattend.xml for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows=Shell-Setup]."
    error, configuring unattend.xml and ZTIConfigure.wsf to use a plaintext password isn’t acceptable as the account’s password is now viewable in plain text.

  21. PeterAUS says:

    This is why we have an RTM +6 months rule too many bugs as of late.
    also you are not looked at in a good light by clients when you cannot deliver, even when its outside of your control.

  22. Max says:

    @adam, that would be nice. There is a way to modify a script yourself to make it work. They keep closing this suggestion on the connect portal as "postponed".

  23. Henning Ervik says:

    SYSTEM_LICENSE_VIOLATION in-place upgrade possible solution?

    After it happens, let boot a few times and try and fail the automatic repair.
    Get into a cmd window by using the troublshooting menus on the blue fancy blackground.
    In the cmd, type reg load "HKLMtemp" d:windowssystem32configSYSTEM
    (if your windows isn’t on D: in the PE environment check some first and select the right letter).
    Type regedit
    goto HKLMtempSetup , verify that there is no SetupType value there.
    Right click, New->dword (32-bit) value
    Call it "SetupType" without the quotes, value should be default (0).
    Reboot and windows will boot correctly.

    Please note: I have no official indication that this is a "good" solution so I’d really like someone from microsoft to post or comment and explain what is happening.
    After it’s confirmed it will hopefully be fixed in the next update, and a possible workaround could be adding a reg /add to the end of the task sequence.
    Let us know if this works for others as well, and if someone other than MS has a decent explenation as well that would be awesome. Thanks.

  24. tony says:

    @Henning Thanks for posting this up!! I’m going to try your possible solution now. Stay tuned! I’ll post the results. Amazing how you figured this out. Hopefully MS will chime in and have a fix soon.

  25. tony says:

    SYSTEM_LICENSE_VIOLATION in-place upgrade

    @Henning… Your solution worked for me! Only thing I did different was edit the registry after the post upgrade reboot.

    I found that the reg key SetupType isn’t even present. Adding it in does the trick. Thanks again for posting this up, I really do appreciate it.

    I think I will look into the possibility of adding the reg edit as a task sequence.

  26. JoeZeppy412 says:

    @Todd I don’t think he was saying its free deal with it, but yeah, I get where you’re coming from, Lots of us have built enterprise level production deployment solutions off of this, and when you get a new version, you kind of expect its going to work,
    not be worse than the version before it.

    Its kind of like having your Christmas bonus replaced by a membership to the jelly of the month club.

  27. tony says:

    SYSTEM_LICENSE_VIOLATION in-place upgrade

    I may have narrowed down the cause…

    When the upgrade task sequence runs, it copies scripts from the deploymentshare to the local machine MININTScripts directory.

    There are 2 scripts that I suspect might be causing the problem. The fist one is setupcomplete.cmd:

    @echo off

    for %%d in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist %%d:MININTScriptssetupcomplete.cmd (

    reg add "HKEY_LOCAL_MACHINESYSTEMSetup" /v SetupType /t REG_DWORD /d 2 /f
    reg add "HKEY_LOCAL_MACHINESYSTEMSetup" /v CmdLine /t REG_SZ /d "%%d:MININTScriptssetupcomplete.cmd" /f

    echo %DATE%-%TIME% Registered Setupcomplete.cmd in registry >> %%d:MININTSMSOSDOSDLOGSsetupcomplete.log)

    for %%d in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist %%d:MININTScriptsSetUpgradeStatus.wsf (cscript.exe %%d:MININTScriptsSetUpgradeStatus.wsf OSUpgrade:SUCCESS)

    for %%d in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist %%d:MININTScriptsLTIBootstrap.vbs (wscript.exe %%d:MININTScriptsLTIBootstrap.vbs )

    for %%d in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist %%d:MININTScriptsSetUpgradeStatus.wsf (cscript.exe %%d:MININTScriptsSetUpgradeStatus.wsf OSUpgrade:COMPLETED)

    The second one is SetUpgradeStatus.wsf Below are the interesting parts of this file. Looks like the reg keys for setuptype and cmdline are removed. See below:

    oLogging.CreateEntry " Upgrade: un-registering Setupcomplete.cmd" , LogTypeInfo
    oShell.RegDelete "HKEY_LOCAL_MACHINESYSTEMSetupSetupType"
    oShell.RegDelete "HKEY_LOCAL_MACHINESYSTEMSetupCmdLine"
    oLogging.CreateEntry " Upgrade: un-registed Setupcomplete.cmd sucessfully" , LogTypeInfo

    I’m not sure why these files exist or if they are needed but, if you look at the registry prior to running the upgrade task sequence, you will notice they both exist. After the upgrade completes, the reg keys are gone.

    SetupType default value of 0
    CmdLine default value is blank

    Can anyone confirm this? Please post up…

  28. Henning Ervik says:

    Awesome job digging Tony. I’m definatly going to do a test with with replacing the SetUpgradeStatus.wsf script line
    oShell.RegDelete "HKEY_LOCAL_MACHINESYSTEMSetupSetupType"

    with something like

    oShell.RegWrite "HKEY_LOCAL_MACHINESYSTEMSetupSetupType", 0, "REG_DWORD"

    and see how that works out while we’re waiting for an official response 🙂
    Guessing the above will most likely work like that, late in the evening here but I’ll try to post back if it’s a success tommorow.

  29. win8.1 to 10 upgrade with win 10 adk kit installed says:

    In this scenario it looks like it uses the dism from win10 instead of the 8.1 dism and that the setup process fails (sorry didnt save the log), anyone else seen the same behaviour? Uninstalling the adk for win10 from the workstation fixed it. Luckily it’s
    probably not so common for this to be present on client machines, but nice to know about.

  30. tony says:

    @Ty…Yes, my KMS server has been updated to activate Windows 10.
    Manually upgrading W10 works fine.

  31. @Tony and others re SYSTEM_LICENSE_VIOLATION – we’ve received several reports of this, but have not reproduced it. Several reports are without MDT so do not believe it to be something specific to MDT upgrade process. Please open a case with Microsoft Support
    to help troubleshoot. Also see this Connect item: – if you are able to get further details from an affected system (memory.dmp or bugcheck parameters from system event log), please share on that Connect item so that we can
    investigate further with the Windows licensing team.

    @Max – please share specific Connect item so that I can followup on the specific request.

    @win8.1 to 10 upgrade with win 10 adk kit installed – please file an item on Connect with more details, I don’t follow what you’re saying. Win10 in-place upgrade does not rely upon DISM.

  32. tony says:

    @Henning… Once again, your idea worked like a charm on a Windows 8.1 machine.

    I edited the SetUpgradeStatus.wsf to include the RegWrite as you suggested and it worked. No more BSD

    oShell.RegWrite "HKEY_LOCAL_MACHINESYSTEMSetupSetupType", 0, "REG_DWORD"

    I just tried to upgrade a Windows 7 machine which worked but upon reboot, I’m getting the broken trust relation error and can’t log into the domain. Boy, the hits just keep on coming. Thanks MS!

  33. tony says:

    @Aaron Thanks for the info! I tried the link you provided but get a page not found error.

  34. Ruben says:

    Regarding the SYSTEM_LICENSE_VIOLATION issue. I ran into it when upgrading without uninstalling AV that wasn’t yet compatible with Windows 10 (Kaspersky Endpoint). I uninstalled the AV, then retried the upgrade and it went without issue.

  35. win8.1 to 10 upgrade with win 10 adk kit installed says:

    Error was related to C:$WINDOWS.~BTSourcesSafeOSwinre.wim. and mounting it, I found a reference in some log file (I believe either setupact.log or setuperr.log under the $windows.~bt panther) to the dism living under %programfiles%windows kits etc.
    and it did work once the windows kit was uninstalled.. _maybe_ it’s just a coincidence. I did not perform a systrace, but mounting wim files is something I normally associate with dism, no? Uninstalling the windows 10 kit did fix the problem for me, but dont
    really have time to try it again or submit to connect as windows kits on workstations are not normal enough to really bother with except noting it _could_ be an issue.

  36. Henning Ervik says:

    Aaron: Thanks for the reply. In regards to SYSTEM_LICENSE_VIOLATION and my testing it’s been consistent (across several virtual machines and some physical) and always happens with MDT. The upgrade process does complete entirely, with no other errors than
    the one in the article regarding monitoring connection/webservice, but the SYSTEM_LICENSE_VIOLATION error is triggered on the first reboot AFTER the upgrade (and mdt processing) has finished. Does your testing include post-rebooting the machines (multiple
    times for good measure) and see that they still work? Same base OS images works without any error when running the upgrade from DVD directly. Tony diggings into SetUpgradeStatus.wsf and the deletion of HKEY_LOCAL_MACHINESYSTEMSetupSetupType (the same key
    which fixes our troubles when present) also indicates a MDT problem, the problem goes away if the key is added manually to a troubled machine AND normally upgraded working machines (I’ve checked a couple) have this key present. Of course there might be multiple
    causes for the SYSTEM_LICENSE_VIOLATION error (explaining why you have multiple nonconsistent reports with and without MDT), but the missing regkey one is consistent with MDT (for me) when testing with several virtual (I use vmware) and physical machines (mostly
    hp elitebooks).

    However, all my testing does include some third-party software and antivirus in the base-oses beeing upgraded, so there might be issues with these as well. For me the testing needs to resemble the real-world so applications are a part of that. The fact that
    the upgrades in my testing works fine when using media without MDT, meant I did not even troubleshoot down the AV/application route.

    Really hope you are able to reproduce somehow, it would be awesome to have a fix for the next toolkit update.
    Note: I also did a test on a already installed Windows 10 system (working fine and nromally) by manually deleting the HKEY_LOCAL_MACHINESYSTEMSetupSetupType registry key and rebooting the machine. Voila, it gives the SYSTEM_LICENSE_VIOLATION error upon reboot.

    (I’ll see if I find time to run a vanillla install or vm install from dvd without any third part applications and do the same regkey test to verify, but no promises).

  37. @Tony – re not able to access the link, are you registered on Connect?
    @Henning – thanks for the info. Can you access the Connect link above? Can you get the bugcheck parameters and/or the memory.dmp from an affected system to upload via Connect? That would be a huge help to investigate the cause.

  38. Huey says:

    This is a joke, admitting the issues and offering a workaround, yet no mention of a fixed release shocking!

  39. Huey says:

    Apologies, just re-read the article. Thanks for letting us know a fix is imminent.

  40. justin_ms says:

    Please do not re-release as Update 1, call it update 2. Don’t want to tell everyone to download after x date or build numbers. That’s nasty. Something like Update 1 MR1 is ok as well. Perhaps move to quarterly releases for MDT?, and re-write all those
    VBS as powershell :). On another note, please make re-ordering of applications in a bundle easier. It’s terribly inefficient to have to click the move up button 20 times.

  41. Horst2 says:

    How can i deploy Windows 10 PRO with MDT 2013 Update 1? Is this possible? Which *.ISO do i need to use for? That one from the Media Creation Tool cannot be imported???

  42. dwtwight says:

    I upgraded to MDT 2013 update 1 and since the upgrade all my ‘Post OS Task Installations Task Sequences’ have a problem. The MMC crashes with error below when I click the OS Info tab, it looks to be trying to populate the OS information same as it does
    for a ‘Standard Client Task Sequence’ and draws the screen the same way.

    Object reference not set to an instance of an object.

    I have uninstalled the update and reverted to using the MDT 2013 (ADK 8.1) / with a deployment share backup I took before the upgrade and now have no problem. When I perform the same action on my task sequences without applying update 1 the MMC does not crash
    and I get a message on the MMC saying ‘This task sequence does not install and operating system’. Looks like somehow this it not happening in Update 1 and it is trying to display OS information and obviously this is missing.

  43. Is anyone working on fixing the issue with Sysprep, after deploying W10E base from install.wim to a Surface, On capture of changes the sysprep just stops with hundreds of DCOM errors, mostly with Search.GatherNotify

  44. tony says:

    @Henning Great report on your findings. My finding are identical to yours. I’m going to build a vanilla Windows 7 machine, join it to the domain, install Office and attempt an in-place upgrade again. Hopefully it won’t come back with the failed trust relation

    After updating the SetUpgradeStatus.wsf I ran upgrades on 3 Windows 8.1 virtual machines joined to the domain and they all worked perfectly.

    I will report back asap…

    @Aaron I do have a connect account and the link doesn’t seem to work for me. I did find the thread regarding Configuration Manager on the Connect site. I will post up there as well.

  45. klosie says:

    @Tony Re: Accessing the Connect Link… I was also getting page not found and had a registered connect account, however, I had to go in to connect and join the Configuration Manager program to get to the link.

  46. Jack Mulliken says:

    Henning, that is a great find. It works when we add it manually to the device as well. When we try to force that key as part of a task sequence, it strips out which leads me to believe, something is removing it. I have a Premier case open with MS on the
    SYSTEM_LICENSE_VIOLATION issue with the upgrade and I passed that along to the Premier engineers. Hopefully, that helps them accelerate the official fix.

  47. Jack Mulliken says:

    I’m finding in the SetUpgradeStatus.wsf script (I don’t know when it’s called), there’s a line saying:

    oShell.RegDelete "HKEY_LOCAL_MACHINESYSTEMSetupSetupType"

    I’m going to comment it out now and see if that fixes the issue.

  48. Frank Trout says:

    What I have found so far is that SetUpgradeStatus.wsf is called from SetupComplete.cmd along with a few registry keys which are meant to be cleaned up in SetUpgradeStatus.wsf. I think the reg delete was meant to clean what was added during the SetupComplete.cmd.
    I commented out the reg delete and added a reg write to change the SetupType value from 2 to 0 and it seems to work so far.

  49. tony says:

    Thanks @Klosie Your advice was very helpful. I joined the discussion as you stated and the link is working.

  50. Henning Ervik says:

    Hello again. I tested the upgrade process with the edit to SetUpgradeStatus.wsf so that it sets the SetupType regkey to 0 instead of deleting
    it. I tested with two windows 7 (made with a patched mdt gold image + AV software) virtual machines with different languages. Both worked without any issues.

    @Tony It’s rather weird that you get the broken trust on win7. If I was in your boots I’d try to remove the network cable and see if I can log in with cached credentials,
    or log in with a local administrator to check if there is any more info in the logs about the issue. Setupact.log and Setuperr.log inside

    c:windowspanther (post-upgrade) on my machines has heaps of information regarding the sids and domain conversions as well as domain names from windows setup,

    I’m not sure but they might be helpful in debugging what’s going on.c:$windows.~BTSourcesPanther (hidden base folder) also has logs (this is definatly a live logging location during the upgrade).

    @Jack: Awesome that you have a case going. I think it will be a better option to set the SetupType to 0 instead of deleting it (see my former post).
    This is what "normal installations" have after, and leaving it at the value of 2 will probably cause it to try and run the cmdline (probably won’t do anything since
    THAT value is deleted, so should work, but 😛 I’m very exited to hear that you have an ongoing Premier case on this and hope a fix find it’s way to the next patch 🙂

    Setupcomplete.cmd seems to be triggered from the setup.exe commandline using switches (not sure if anyone has mentioned that) showing that this is indeed an MDT issue related
    to Setupcomplete.cmd and SetUpgradeStatus.wsf (just to confirm Tony’s findings). Checking the BDD.log and finding the upgrade command used shows the following switches:
    /PostOobe C:MININTScriptsSetupComplete.cmd /PostRollback C:MININTScriptsSetupRollback.cmd

    I wasn’t able to find the offical switches documentation, but this page third-party page explains them well:
    Which is consistent with where MDT copies the script folder prior to running the upgrade.

    The connect link is unfortunatly status "closed as external issue", hopefully someone can get it opened again.

  51. Horst2 says:

    How can i import Windows 10 Professional?

  52. Henning Ervik says:

    @Horst: I used volume license media from Microsoft Volume Licensing Site (, imported just fine from the CD. Means you need a open or volume
    license agreement to access though.

    I have also created a gold image (windows 10 installed from that media, with full updates) and done a "Sysprep and capture" task sequence (needs to be recreated with the latest mdt update to work) and am currently using that as a base/gold image for my bare-metal/"newcomputer"
    deployments (the in-place upgrade I understand it is a requirement to use the actual original microsoft media for, so I didn’t even test anything else there).

    Not sure if it’s the answer you want but just chiming in, in case that helps.

  53. Daniele Ghirardelli says:


    I think that images in ISO from the from the Media Creation Tool are push-button reset images (like the ones compressed with /compress:recovery of DISM):

    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.

    Look like MDT doesn’t manage wim using this type of compression.

    Use DISM to export the image from the Media Creation Tool ISO to a new wim changing the compression type:

    C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment
    Tools> dism.exe /Export-Image /SourceImageFile:E:sourcesinstall.wim /SourceInde
    x:1 /DestinationImageFile:C:ExportedWiminstall.wim /Compress:max

    and import to MDT the new wim.

    It worked for me.

  54. Horst2 says:

    @Daniele Ghirardelli Thanks, i will try it!

  55. Horst2 says:

    @Daniele Ghirardelli When i try your solution like this (yes, the image is in the correct place):

    C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeploym
    Tools>dism.exe /Export-Image /SourceImageFile:E:sourcesinstall.wim /Source
    x:1 /DestinationImageFile:C:ExportedWiminstall.wim /Compress:max

    I get this error in german:

    Tool zur Imageverwaltung für die Bereitstellung
    Version: 6.2.9200.16384

    Fehler: 11

    Es wurde versucht, eine Datei mit einem falschen Format zu laden.

    In egnlish: "Error: 11 – An attempt was made to load a program with an incorrect format"

  56. Henning Ervik says:

    @Horst: Your dism version number (6.2.9200.16384) is an old version of dism, make sure you have the windows 10 adk installed downloaded from (bottom of page) or direct link (
    Even with the correct version downloaded and installed I’ve seen it use the wrong one. If this happens try to use the shortcut for the windows kit to launch your cmd window and see if it shows the correct version number. I don’t have access to dism from this
    computer but the version number should definatly start with 10.0…something

  57. Daniele Ghirardelli says:


    You can have the Windows 10 ADK installed but If you are not starting dism from the Windows 10 ADK path (like this: C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Tools)
    you could run an older version of dism

    The command work with version 10.0.10240.16384 of Dism

    Make sure you have Windows 10 ADK installed
    search the link to open the ADK cmd in start menu
    right click on the link and run as administrator
    run the command:

    dism.exe /Export-Image /SourceImageFile:E:sourcesinstall.wim /Source
    x:1 /DestinationImageFile:C:ExportedWiminstall.wim /Compress:max

    (change the path for source and destination files if necessary)

  58. Bien says:

    We are a MS partner/reseller and will be deploying MDT 2013 update 1 to customer. Is technical support call for MDT

    supported by Microsoft premier support the same support policy as paid products such as Windows Server, SQL, Exchange server?

  59. FYI, for folks experiencing the blue screen with SYSTEM_LICENSE_VIOLATION – good news is we were able to reproduce the problem and have confirmed, as the community discovered, it is due to the removal of the setup registry keys. We’ve also confirmed the
    fix of changing the values instead of deleting the keys. Thanks to those of you that reported and helped identify the issue.

  60. Henning Ervik says:

    @Aaron: Awesome, thank you for the feedback on this 🙂

  61. tony says:

    @Aaron: Great!! Thanks!
    @Henning: I’ve been oShell.RegWrite "HKEY_LOCAL_MACHINESYSTEMSetupSetupType", 0, "REG_DWORD" to add the SetupType key back to the registry.

    What do you think about the CmdLine key? Do you think this will work? I haven’t tested it yet. Wanted to get your feedback on this…

    oShell.RegWrite "HKEY_LOCAL_MACHINESYSTEMSetupCmdLine", "", "REG_SZ"

    Since the CmdLine key is empty, I’m not sure using the double "" will write a blank entry for REG_SZ

  62. tony says:

    Edit my previous post:

    Hi Aaron. Thank you so much for the followup. I’m glad you were able to duplicate the problem. Can we expect an update to MDT to be released? Just to confirm the workaround, I have edited the SetUpgradeStatus.wsf file. Specifically the 2 lines that delete SetupType
    and CmdLine reg keys. I have changed the lines to read the following. Can you confirm this is correct? Notice I changed the command to perform a RegWrite instead of RegDelete. The only thing I’m not sure about is the CmdLine key. The default is REG_SZ value
    is blank on production machines. Not sure if my command will write a blank value. Testing is pending. Again, thanks for your help!

    oShell.RegWrite "HKEY_LOCAL_MACHINESYSTEMSetupSetupType", 0, "REG_DWORD"
    oShell.RegWrite "HKEY_LOCAL_MACHINESYSTEMSetupCmdLine", "", "REG_SZ"

  63. Mike P says:

    I’m getting the error message System.FormatException: Input string was not in a correct format" when running the task sequence wizard for client task sequence and my on OS locale is en-gb.

  64. tony says:

    I had to completely downgrade my MDT to an older version because of the issue with the update.
    Once it connected to the WDK for Windows 10, I could not go back and had to create a new deployment share.

  65. TestPilot says:

    If you are using this on a production server please don’t complain? Win10 is _not_ an enterprise OS to begin with.
    Still unable to defeat certain features via reg hacks & GPO. Updating to test this MDT however…. lots of bugs!

  66. says:

    I submitted a Bug on Connect at (make sure you click DETAILS) to see the full issue.
    This is marked as Fixed in an Upcoming release, but I see no mention of a resolution here or in the Connect comments.

  67. says:

    And get rid of ZTIWinRE in MDT as this doesn’t work as it should and is unnecessary in Windows 8.1 and Windows 10 as Setup/OOBE handles the move of WinRE.wim (assuming you have proper WinRE Tools Partition sizes). See

  68. I am looking for nay help in being able to successfully complete a Capture of W10E LTSB

    So far I have successfully deployed W10E LTSB to a Surface Pro 3, but on capture it will not complete the Sysprep with numerous Distributed COM errors in the System log.

    I have tried manually building from USB stick, and then capturing with the same result, Sysprep with numerous Distributed COM errors.

    I have tried both scenarios with another local Administrator account (not the default).

    The Distributed COM errors seem to point to Windows Search, starting with {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} (one error) and all subsequent errors being {9e175b6d-f52a-11d8-b9a5-505054503030}.

    {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} – Windows Search is confirmed running and is set to Automatic.

    Tried the following also with no luck…

    regsvr32 jscript.dll
    regsvr32 msxml6.dll
    regsvr32 msxml3.dll
    regsvr32 vbscript.dll

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform



    msdtc -uninstall (wait few seconds)
    msdtc -install (wait few seconds)
    Restart the machine

    Does anyone have any ideas of how to capture Windows 10 successfully, this is starting to get out of hand for a RTM product…

  69. Lars Fredrik Bach says:


    I am also experiencing some bugs with MDT 2013 Update 1 + Windows 10 deployment.
    When trying to use CS.ini and OSDComputerName=PC-%SERIALNUMBER% it fails during setup and reports that Untattended.xml is corrupt.
    When checking this in WISM it doesn’t report any errors and this is working for Win7 Deployments.
    When commenting out OSDComputerName-variable in CS.ini the deployment run as usual.

  70. I have found a partial fix for this, and actually got the Sysprep to go through, though the creating WIM failed.

    Ensure the Skip Rearm is not set to 1 anywhere

    Modified the Unattend on the Task sequence, removed Display group completely as it is deprecated, modified the XML in the folder for the task sequence, and removed Network Location which is also deprecated.

  71. Herman says:

    Using MDT 2013 Update 1 (w/ ADK for W10). Creating a reference image and just at the start of the "Creating WIM" a popup "can not find script file" pops up. The .wim file created is 3 mb and capture ends.

    Anyone with simmilar issue?

  72. Steve says:

    @herman. I had this issue too. The message said "Can not find script file "C:LTIBootstrap.vbs" most of the references I were seeing showed this issue for Zero touch deployments through not Lite touch. After clicking OK it created a 3 mb image file and

    The task sequence I was using was created from my MDT2010U1 setup (that was updated to MDT2012U1 and then to MDT2013U1). I created a new task sequence and my issue went away.

  73. klosie says:

    Maybe not a problem with MDT, but I remove the "Get Office", "Get Skype" and Solitaire apps, and they keep re-appearing, before and after the image capture, can’t seem to get rid of them. :/

  74. ShaneG says:

    @klosie – You need to "Remove-AppxPackage" and also "Remove-AppxProvisionedPackage", otherwise they will reappear. Check out this blog (for WIn8.1 but works the same on Win10):

  75. klosie says:

    @ShaneG – thanks, that was it, been banging my head on that for days.

  76. Anonymous says:

    208 Microsoft Team blogs searched, 57 blogs have new articles. 263 new articles found searching from

  77. ZubiDoobi says:


    i just applied the MDT update 1 and after deploying windows 10 i am getting this error: FAILURE(5627): 50 run dism exe

    does it have anything with these fixes or it is just DISM.exe crashing?


  78. Mitchawkes says:

    Result and different behavior in using Microsoft Deployment Toolkit 2013 Update 1 RTM

    The task sequence template (New Computer mode) generated several times and identically, may not work half the time ! Different behavior depending on the case !

    Indeed, the XML file (ts.xml) may be corrupted, causing a crash when installing a workstation.
    Furthermore , variable ‘PHASE ‘ may be ignored or empty .

    The XML file (applications.xml) is not entered identically for MDT applications. The tag regards restarting the workstation for applications is either empty or has the value : False

    My MDT server platform :
    – Windows Server 2008 R2 up-to- Date
    – Microsoft ADK installed 10
    – MDT 2013 Update 1 RTM
    – Active Directory 2008 R2

    But what does Microsoft ??


  79. Tim says:

    Hi, maybe someone can tell me what the error in the SetUpgradeStatus.log means. "Unable to create WebService class" – I got the same error in the BDD.log and my Deploymet will not finished. It hangs at the Step "Applications" form the Tasksequenze.

    Thank you!.

  80. Mathieu says:

    Hi Aaron,
    Any updates on the re-release of MDT2013U1 would be appreciated :
    -Which bugs will be correctes and which bugs won’t
    -Real ETA on release

    You Can’t expect dedicated Partners to adress POC with broken Tools 🙂

    Tank You very much for tour time


  81. Tim says:


    If I disable the Monitoring, I don’t get the massage "Unable to create WebService class" again, BUT I don’t get the Finish Summary after the Upgrade Prozess and on the C: Drive i see the Folder MININT. In all Logs i see now Error Massage and all Scripts Show
    the state Successfully. But why i don’t get the Finished Summary at the end from the Upgrade Prozess? Where I can have a look why the Process will not finish completely?
    Thank you for your time!

  82. Steve says:

    @Mathieu I too would like to know when fixes are to be released, the issue I had was the SYSTEM_LICENSE_VIOLATION error, this was apparently closed on the 1st September and it only involved not deleting two registry keys…. sounds like a simple fix to
    me, but why no further news on the re-release/patch?

  83. nick says:

    The new build still has problems. On a new CM12 R2 site with a fresh install of W10 ADK, it fails when creating a client task sequence with “Input string was not in a correct format.” It seems to occur at the stage of creating the MDT Settings package.
    As a test, I used a different path for the source files (the parent folder), and it worked. Ironically it didn’t have any problems creating the MDT Package which used the same folder structure that ended with a 1.0 folder.

  84. Josué says:

    Hi there,

    Regarding this known issue "Unable to create WebService class". I understand that it has been resolved with build 8298. I use this last build but I’m still getting this warning. I’m not doing an upgrade from a previous Windows version. I deploy a fresh Windows
    10 Ent. x64 with capture without nothing more than this. In my BDD.LOG I have:

  85. Ulysses Rumph says:

    Thanks for known issues.

    Ulysses Rumph,

  86. Craig Wilson says:

    Using MDT 2013 U1 and getting this error when I trying to deploy a VM after altering the DB and ZTIGather.xml to configure multiple NICs:

    FAILURE (7813): False: Verify there are partitions defined in this task sequence step

    Doesn’t matter if I leave the Format and Partition steps in the TS as default or if its customised to use 1 partition

    If I revert changes, the TS completes successfully

  87. Junz says:

    I found some bug on Deployment Wizard timezone and it happened frequently. During Deployment Wizard, it will allow to select timezone. for example i select "GMT+8 – Kuala Lumpur and Singapore" then proceed reimage. After it reimage complete, i see the
    timezone was not correct to what i select. It seem like using back to default timezone. Anyone got this problem?

  88. Brian D. Coryell says:

    LiteTouch media install (not pxe) to Surface Pro 3 with no keyboard does not provide a way to bring up the on-screen keyboard!

  89. Asa Pruiett says:

    the above registry fix worked for me

    Asa Pruiett,

  90. Ezequiel Graul says:

    I tried zero touch deployment & got error saying cannot find script.

    Ezequiel Graul,

  91. Shishir says:

    Lots of information available

  92. Justin Willenborg says:

    I am having an issue after upgrading to MDT 2013 Update 1 ReRelease. I have a few "Run Command Line" tasks that will not run anymore. They basically just use batch files that are stored on the local machine itself. For Example: I have it set to start in
    directory called "C:ITact" and in the Command Line input I put I enter "winact.bat" (this is a batch file that basically pulls the manufacturer license from the BIOS and activates it). This worked fine for MDT 2013 (before update) but now is not working
    for me. have tried using the the old ZTIapplications.wsf that people have mentioned that didn’t help. I have tried creating new task sequences and they still do not work. I have verified I am running the right version: 6.3.8298.1000. Please Help!


  93. Siegbert says:

    I am trying to make USB media and put a check mark to create the ISO files too, but the only thing gets created is deploy folder , no ISO boot manager files or anything else?

Comments are closed.

Skip to main content