Windows 10 ADK release and MDT 2013 Update 1 plans

The Windows ADK for Windows 10 is now available at (The page also includes other Windows kits; remember for deployment you only need the Windows ADK for Windows 10.)

The MDT product team is working hard to finalize MDT 2013 Update 1, and currently plan on releasing it in August. We know how excited and eager you are to start using MDT for Windows 10 deployments so are doing what we can to signoff this release as quickly as possible.

Note that System Center 2012 R2 Configuration Manager SP1 currently supports both deployment of Windows 10 using a Windows 10 boot image, as well as the in-place upgrade scenario.

-- Aaron Czechowski, Senior Program Manager

This posting is provided "AS IS" with no warranties and confers no rights.

Comments (80)
  1. Josh says:

    What is the version number on the release? Is it the 10.0.26624.0 build?

  2. @Josh – yes, for some reason the adksetup shows v10.0.26624 but it does install the 10.0.10240 components.

  3. Erik says:

    What about MDOP 2016 ?

  4. maarten says:

    Only for System Center 2012 R2 Configuration Manager SP1 currently supports both deployment of Windows 10 using a Windows 10 boot image and not for System Center 2012 Configuration Manager SP1?

  5. Bryan says:

    Does deploying Windows 10 REQUIRE a Windows 10 based boot image?

  6. Rom S says:

    any thoughts on whether mdt release will be able to upgrade a deployment share created by mdt update 1 preview?

  7. @Erik re MDOP – no idea, sorry 🙁
    @maarten: 2012 R2 SP1 and 2012 SP2, technically the same thing, just different brands.
    @Bryan: I’ve heard it works, but technically the deployment tools do not support forward compatibility. So to deploy Windows 10 in a properly supported manner and reduce your potential risk, you need to use a Windows 10 boot image to deploy Windows 10.
    @Rom S: I think our primary test coverage is on MDT 2013 RTM to U1. From Preview *might* work, your mileage may vary.

  8. thomas says:

    Keep up the good work !

  9. Jack Fetter says:

    @Bryan No, not required technically. You can deploy Windows 10 (I’ve been doing it for 6 months via SCCM 2012 R2 OSD and testing with apps as new builds come out) using the 6.3 Boot Images (W8.1), you just have to add a task to update DISM.EXE and the
    DISM Folder under WindowsSystem32 in the WinPE before your "Add Drivers" section. I see no reason now that the ADK 10 is out to continue as the 10.0.10240.16384 Boot Disks now work with no tweaks/cheats…

  10. Jack Fetter says:

    Thanks for the ADK 10 guys! I’ve been waiting on it after not being able to test USMT with the preview build. Only issue (not so bad after you do it once) is you have to build the Windows 10 Boot Disks manually if your already running SCCM 2012 R2 SP1,
    seems the SP1 upgrade would have forced the issue is installed after ADK 10, live and learn, it’s not so bad once you do it…

  11. allenpu says:

    Nice to hear that.Thanks for your hard work

  12. Tobi says:

    It’s called MDOP 2015 and will be released in late August.

  13. allman says:

    Should I uninstall ADK 8.1 from SCCM 2012 R2 SP1 and then install ADK for Windows 10?

  14. Matthew says:

    When are pe 10 boot images going to be editable from the console?

  15. @allman, Matthew: more details coming on that shortly via ConfigMgr blog (

  16. Mark says:

    I hope you guys plan on signing your scripts considering Device Guard relies heavily on having all things signed. When I go to edit unattend.xml I have a ton of whitelist warnings from runcmd.cmd and I’d never be able to run MDT if Device Guard was enabled
    on a Windows 10 system.

  17. @Mark – no plans to sign MDT scripts at this time. Feel free to file feedback on Connect.

  18. Anonymous says:

    Hello all, I hope your summer is going well! As you know Windows 10 is here and has hit general availability

  19. Dave Franklyn, MVP Windows IT Pro says:

    You said the finalized MDT 2013 Update 1 will be ready mid-August. What are you going to call it? May I suggest "MDT 2015"? Does that have nice compliant ring to it? Or how about "MDT for Windows 10"? Seriously, though, Aaron, what will it be called? I’m
    writing courseware and would really like to stop typing "MDT 2013 Update 1 Preview for Windows 10"!

  20. Rafael says:

    @Aaron @Dave Even better, release it already. I need to start deploying Windows 10 using ConfigMgr with MDT integration as soon as possible.
    Thanks in advance!

  21. Phillip says:

    Why release the operating system for you can support it? Shouldnt this have been done and ready by now.

  22. @Dave Franklyn – it will be MDT 2013 Update 1. The reason has to do with our defined support lifecycle and need to continue to support customers with legacy deployment requirements.
    @Rafael – we still have to complete final testing and release procedures to drive quality. You can use ConfigMgr today (without MDT) to deploy Windows 10.
    @Philip – release of the tools always follows the OS to ensure that the tools are tested and verified (prior to release) with the final version of the OS that is shipped to customers.

  23. Leo Jacob says:

    Hey Aaron, i’m sure you have zero influence/stake over it, and it isn’t a perfect world, but it does seem silly to release an enterprise OS and not have the enterprise tools to deploy it at its launch. really, the tools should be tested and verified during
    its build, not after. I mean consider all the corporations that need to have their services and products ready for windows 10 at launch, if they’re excepted to deliver that to be successful, then one should absolutely expect the same from the company responsible
    for the very tools to deploy their own product. i mean the xbox and surface products are ready for windows 10 at launch, why not MDT/SCCM.

  24. Phillip says:

    Thank you Jake…. Unless they are foreseeing huge issue with their final product. Or put all the developing time into code that tracks and sends info to M$.Instead of supporting their "Enterprise Ready" Operating System.

  25. richsmif says:

    Highly disappointed that MDT is NOT fully working with enterprise at the moment. Eagerly waiting.

  26. Rafael says:

    @Aaron Thanks for keeping all of us informed; I really appreciate it. I’m sure MDT 2013 U1 will be released when you and your team think is ready.

  27. Frank says:

    Why kiss Microsoft’s butt about this. My company pays ALOT of money for volume licensing and ect. They have nothing for me to deploy this. Also there is no RSAT for Windows 10 either. They sure did drop the ball on this release.

  28. Aaron Arnold says:

    This happens every time there is a new OS the OS gets released and then we wait for all the tools needed to deploy and use the OS nothing different. I’m not really sure why everyone thinks that Windows 10 is going to be different on this one. In fact I’m
    surprised the SCCM got any support for it before the OS was released.

  29. will says:

    The Windows ICD fails when I try and load an install WIM from Windows 10 pro to make a custom image.

  30. jim says:

    Have to agree with Frank. I was pleasantly surprised the ADK was actually ready before launch.

  31. jim says:

    Also, we use standalone MDT and not ConfigMgr to do OS deployments, so that is not a solution. We wait again…

  32. Johny says:

    Hope it gets released soon. There is some improvement compared to Win8: ADK is already here, ConfigMgr support is done with SP1, Too bad we have to wait on MDT/RSAT to fully use the OS in an enterprise environment.

    I do understand the frustration, especially since ConfigMgr 2012 R2 SP1 has already been released well before official windows 10 release with capabilities to install Windows 10. This means that from the latest builds onwards nothing much has changed in the
    installer logic, else ConfigMgr SP1 would also not be possible to install Windows 10. Just saying I don’t really understand the delay with MDT.

  33. Jack says:

    I was hoping for a whole new deployment product with a completely redesigned deployment process from the ground up. I guess that was wishful thinking on my part.

  34. Mykel says:

    @JAck – that wouldnt be good. lots of organizations of highly customized deployment shares. revamping mdt would require a heavy investment in testing and redeployment

  35. BigDally says:

    Do we have an ETA on when the final MDT for Windows 10 will be released, instead of just "August"?

  36. FancyPants says:

    I would say someplace in between now and the 31st, but those dates are subject to change.

  37. Anyone says:

    Any info on release date?

  38. Rehan Shafiq says:

    I cant access my account. when I logged in and click on WIKI an error message is generated page is not available, but from different account it worked fine. kindly guide me. does my account disable from TechNet ? I cant post article on view is available
    for me.

  39. richsmif says:

    Still shocked at Microsoft taking so long on MDT. I work for a Microsoft gold partner and we are waiting for this almost daily! SHOCKING

  40. Smith says:

    Just give us a date´…

  41. Gabriel says:

    Any update on this?

  42. Amil says:

    C’mon guys! We are getting overly desperate here… At least give us a date.. Our clients are getting anxious as well!

  43. Jason says:

    Soon ™

  44. Todd says:

    Take your time, make it right, I run a corporate environment and want a smooth transition.

  45. David says:

    But geeze…gives us a date Microsoft will release MDT 2013 U1…we have clients waiting…

  46. rusty says:

    This guy doesn’t care, microsoft doesn’t care, because at the end of the day they still make the money. They dont have RSAT ready, they don’t have MDT ready, Windows 10 wasnt ready.

  47. Johnmclain says:


    Non sense, a completely new deployment product would be amazing and welcomes by everyone who works with MDT. Now with windows 10 upgrade process being so smooth, it would make sense not to make custom wim and just deploy a generic wim to the windows 7/8 desktop
    pc and allow windows 10 upgrade process to do the rest. There is even less need to customise it before hand, all the customizations should come in the form of a much improved windows 10 group policy admx.

    Unforunately windows 10 admx is just as pittiful as windows 7 was and MDT is just as much a mess as it was when it was first released.

  48. RyanR says:


    Agreed the admx is pittiful

  49. Mykel says:

    MDT does a pretty good job at meeting a lot of IT shops needs for OSD. In the simplest forms its easy to get started and with some research a very complex deployment system can be made for large scale environments. I do wish admx and unattend.xml had more control
    over the new ui features in 7 8 and 10 but I don’t think that’s MDTs issue. that’s UI/policy issue.

  50. tony says:

    It is shameful that the new version is going to be called "MDT 2013 Update 1". I mean, Windows 10 is not called Windows 8.1 Update 2, or Windows Vista R2 Update 3, or even Windows 95 R6 Update 4. Sad what Microsoft’s marketing team has done.

    It really should be called 2015. Oh wait, better yet… Call it MDT v6.3 ! Let’s abandon all this stupid year-based version nonsense.

  51. David says:

    Is there ever any end to Microsoft’s version control? Why not MDT 2015? I mean, Mdt 2013 was in 2013 and had no knowledge of Windows 10. I have a feeling the update release version of MDT will have issues…just like Windows 10 does…it was released too
    early. There is not enough solid infrastructure tools to support any Windows 10 corporate update. Most companies will wait at least 6 months…maybe longer. I hope Windows 10 is very successful…but for not, the infrastructure tools do not support it – including
    MDT, Windows 10 GPO, MDOP, RSAT…the list goes on and on…

  52. David says:

    Add to the list Dynamics CRM is not supported on Windows 10…yawn…again – Windows 10 was released too early…

  53. stephan says:

    It can be called "MDT 2013 Update 1" or "MDT 2012 Update 9" or "MDT 1995 NT", I don’t care. It does what it is supposed to do, even the prerelease version is doing fine (except for language packs), so I do not see any issues with that name. Except that
    the RTM version has not been released yet.

  54. Raphael says:

    Any news about the release date ?

  55. Hildegard says:


  56. Ken says:

    @ David There is a workaround for CRM install at

  57. Rafael Vazquez says:

    I think (This is just my opinion) MDT 2013 Update 1 and new RSAT will be announced tomorrow. I could be wrong but I really hope I’m right


  58. Jake M says:

    I’m going to build a new machine for MDT 2013U1 any suggestions on using Windows 10 or 8.1?

  59. So MDOP 2015 is out. MDT? Nowhere to be seen 🙁

  60. Thiago Zanardo says:


    I installed MDT 2013 upgrade 1, a new server, and also the ADK for windows 10.

    I imported the Windows 10 enterprise, and set up a TASK SEQUENCE.

    I upgraded to generate a new boot image, and create a boot pendrive.

    I realized the boot with the pendrive, and configure static IP with subnet mask, gateway and DNS (I have not DHCP), and then the MDT shows the error message below.

    Networking Settings Error

    Network settings have been applied except for the following:

    EnableStatic(IPAddress,SubnetMask) Failure: Unknown Error: -2147467259

    Ok to Continue?

    Has anyone seen this message and can help me?


  61. Rafael Vazquez says:

    @Raphael. It looks like I was. All the right stars were properly aligned; this is how I knew it was going to happen. Now, if my theory is correct, a new version of RSAT will be announced in an hour or two.

  62. Robert says:

    Anyone having any issues with trying to update their deployment shares after the installation? I installed it on both Server 2012 R2 and Windows 7, both times I updated the Deployment Share and it crashed on me with an error 1726. I tested it out Windows
    10 and it works perfectly. Problem is our production MDT server is Server 2012 R2.

  63. Rafael Vazquez says:

    @Robert Update your deployment share running on Windows Server 2012 R2 from your Windows 10 machine. Install ADK 10 and MDT 2013 Update 1 on your Windows 10 machine, open the deployment share running on Windows 2012 R2 and select update. I just did it
    and it worked fine for me.
    I hope this helps.

  64. Jeff25 says:

    I’ve got a Windows 10 reference image ready in Hyper-V that I am unable to capture with MDT 2013 Update 1. It executes sysprep, disconnects the network at some point during sysprep and then errors out with "Can not find script file ScriptsLTICopyScripts.wsf".

  65. Jeff25 says:

    Ok, so I create a new sysprep and capture TS and so far so good, it is currently creating the wim.

  66. RJ says:

    So i did a clean install of Server 2012 R2, MDT 2013 Update 1 and ADK v10. Updating share to create boot images is very hit and miss (mainly miss). DISM reports errors and stops working and now it will not mount winpe.wim and fails to create boot images.
    Everything was happy in MDT 2013 and ADK 8.1. Now I try to install MDT etc on WIndows 10 to see if these errors disappear.

  67. Chris Nicholls says:

    @RJ I had the exact same issue built a brand new server and it worked had to completely uninstall ADK and all Windows Kits reboot and install ADK 10 and MDT 2013U1 for it to work again.

    I have noticed since Upgrading to MDT 2013U1 from 2013 the Estimated Time Remaining from Applying the Image has dissappeared anyone else noticed this issue??

  68. RJ says:

    Everything working as normal when installed on Windows 10. I installed Windows Deployment Services on my DHCP server to get PXE boot back. One thing to be aware of if you edit the unattend.xml in WISM fails the deployment. Only tested this with Windows
    7 so far. Need to investigate what other tools i can use to edit the unattend.xml as i usually do the cheat to get the optimal resolution by setting horizontal and vertical to 1 pixel. Also with my Windows 8 deployments i use the copyprofile feature.

  69. Jeff25 says:

    @Chris, apparently this is due to them now using DISM for applying images in place of ImageX.

  70. PH says:


    I’ve been trying to do something with ICD to evaluate the "Zero Master" strategy with Windows 10.

    It works works very well to change the edition of Windows (Pro -> Enterprise). Adding an user account too.

    But this is the only 2 settings I could test successfully. Everything else is not working :

    – Uninstalling an ICD does not revert back the settings included in it.

    – Setting a proxy seems to do nothing (Edge and IE verified)

    – Installing an .appx, even copying it manually on the target system as recommended doesn’t work

    – Uninstalling an .appx works sometimes but not always

    – Etc.

    Does anyone has tried successfully ICD ?

    I wonder also the meaning and use of some parameters : the GUID, the rank and version. Does it work like in Windows Installer ?

    Are there any logs to watch out for troubleshooting installation of ICDs ?

    I’ve read that ICD only works for now at the runtime. Is it possible to use ICD while deploying and if not, when could we use that ?

    Installation of ICD provisionning profiles is not really "neat" : it does not show to the user exactly if it is still installing or not. A progression bar would have been great, even without exact progression. And the listing of the settings included in a prov.
    profile does not seem to be explicit or even complete (some settings are not shown, some descriptions are not very meaningful…)

  71. Jeff25 says:

    Can anybody else confirm CopyProfile in Windows 10 is broken? Cortana is missing and the desktop folder for all users in Quick access points to the Administrator profile if I set CopyProfile=True in my TS. This is incredibly frustrating and has halted
    any rollout I was planning.

  72. Keith says:

    @Jeff, yes this is what I (and EVERYONE else) is running into. Apparently one of the cumulative updates (latest one?) broke this. The Cortana search bar is broke, the Quick Access points to the inaccessible (Administrator) Desktop, and in fact, my Start
    Menu stopped working and won’t open. Basically Windows 10 is a useless OS for deployment at the moment. (I’ve seen comments that the Quick Access ‘desktop issue’ was reported way back in the tech preview but has never been fixed.)

  73. Baskaran says:


    I have installed MDT 2013 update 1, a new server, and also the ADK for windows 10.

    While import the windows 10 OS .. getting error..

    Performing operation "import" on Target "Operating system".
    Unable to get information for WIM file c:Windows 10 Pro\SourcesInstall.wim.
    System.Exception: Unable to open the specified WIM file. —> System.ComponentModel.Win32Exception: An attempt was made to load a program with an incorrect format
    — End of inner exception stack trace —
    at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
    at Microsoft.BDD.PSSnapIn.ImportOperatingSystem.Import(String sourcePath, String directoryName, Boolean moveDirectory)
    Import processing finished.

    Please help !!!

  74. eagle20060902 says:

    I need to upgrade my present MDT environment to support windows 10 images. When I upgraded to support windows 8.1 images I simply removed ADK and reinstalled teh updated version. I then installed MDT toolkit and did not remove old version and then updated
    my shares. Is the upgrade path for mdt the same now. I am having trouble finding clear documentation. Thanks

  75. Katie says:

    Any word on when Update 2 will be ready?

  76. Rich says:

    Any news on being able to Import Windows 10 1511 (threshold 2) into MDT as an Operating System?

  77. Anand says:

    I tried deploying Windows 10 to a Hyper-V virtual machine using MDT 2013 Update 1 and receiving cannot find script C:LTIBootStrap.vbs file.

    I am not using any sysprep and capture task sequence to capture image.

  78. Nate says:

    Seeing an issue with since upgrade from W8ADK to W10ADK error: Error: 1726

    Processing 1 of 1 – Adding package WinPE-MDAC-Package~31bf3856ad364e35~amd64~~10.0.10240.16384

    Error: 1726

    The remote procedure call failed.
    An error occurred closing a servicing component in the image.
    Wait a few minutes and try running the command again

    This happens EVERY time I update my boot image. If I click Check Online for the solution the window closes and my image is built. If I click close program my boot image finishes too. What gives??

Comments are closed.

Skip to main content