Every time I’m starting a new Windows 10 deployment project, I need to know which Windows 10 ADK is installed on a server to use with MDT or SCCM. The Windows 10 ADK (Assessment and Deployment Kit) has the tools you need to customize Windows images for large-scale deployment, and to test the quality and performance of the system, the added components, and the applications running on the system.
How to find your Windows 10 ADK Version
In Program and Features, all Windows 10 ADK are referred as Windows Assessment and Deployment Kits – Windows 10. The only element that defers is the build version at the right.
Each time, I end up googling the version number but the information was not easily findable. Those days are over since I will be documenting Windows 10 ADK Version History in a beautiful table until Microsoft decide to include the build number in the name of the product… which could be never…
Windows 10 ADK Version History
| Name | Version | Released | Direct Download Link |
|---|---|---|---|
| Windows ADK for Windows 10 v1709 | 10.1.16299 | October, 2017 | Download link |
| Windows ADK for Windows 10 v1703 | 10.1.15063 | March. 2017 | Download Link |
| Windows ADK for Windows 10 v1607 | 10.1.14393.0 | Sept. 2016 | Download Link |
| Windows ADK for Windows 10 v1511 | 10.1.10586.0 | Oct. 2015 | Download Link |
| Windows ADK for Windows 10 RTM | 10.0.26624.0 | July. 2015 | Download Link |
| Windows ADK for Windows 10 | 10.0.10240.0 | July. 2015 | Download Link |
See our post on how to upgrade your Windows 10 ADK version, if you already have an ADK version installed on your server.
11 Comments on “Windows 10 ADK Version History”
so what if the environment have a multiple windows 10 build numbers, and the current adk installed with SCCM is 1709 so the only version of windows 10 should be use is 1709 or ADK 1709 will support older version of windwos 10 such as 1703-1607 and so on.
I would assume that previous Windows OS (client) versions continue to be supported when you are running the latest “server components” (SCCM and ADK). With that said, my concern is staying compliant with the Microsoft matrix documented below:
Support for Windows 10 for System Center Configuration Manager
https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10#windows-10-adk
In parallel with that, keep an eye in the “What’s New/Change” session in every ADK release to know the resources that are “new, deprecated, removed, etc.”.
Hi,
yeah Microsoft doesn’t provide a lot of flexibility here… The overall idea is to stay up to date.
I do understand that is easier said then done, but that how Microsoft want it. :S
Jonathan
Hi Benoit,
I got the ADK 1709 release note from Michael Niehaus on Twitter just an hour ago. I came here to let you know about that update, but you were faster than me! lol
Thanks a lot for keeping this reference updated. It is very handy and I enjoyed this information last week while upgrading to CM 1706.
Cheers!
Julio
Currently working with MDT for kaby lake laptop on a Windows 7 you just saved me hours of researches ! Thanks
You should definitely add something about backing up any customized XML files used by USMT before uninstalling any version of the ADK from your server.
Oops – I meant to put this comment on a different post.
Hi Cristopher,
We are reworking a part of the How To update Windows ADK post.
We’ll add a note about USMT XML files
thanks
Jonathan
Great list!
The SecureBoot driver-bug is now fixed for 1703 ADK, and the patch is available at: https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/
Thanks that’s good to know. I will probably still wait to the fall ADK. I usually skip a release.
Is the 1703 ADK deemed bug free? I know 1511 was a disaster but 1607 went by fine. I really hope they add a way to SCCM to update the boot image once you install a new ADK.