Whats new in the September 2014 release of Windows ADK 8.1

On September 15, 2014 – Microsoft made the fourth release of Windows ADK 8.1 available. As usual without any explanation on what's been changed 🙂

Windows ADK 8.1 history

First release, September 2013: 2.79 GB in size

Initial release, contained ACT 6.0, WinPE 5.0, and USMT 6.3

Second release, October 2013: 2.85 GB in size, subversion 8.100.26020 (Patches folder)

No new versions, just bug fixes.

Third release, April 2014: 2.97 GB in size, subversion 8.100.26629 (Patches folder)

In this release ACT was updated to 6.1, and a package to update WinPE to 5.1 was made available. The other updates was basically bug fixes.

Fourth release, September 2014: 2.97 GB in size, subversion 8.100.26866 (Patches folder)

Bug fix for dism and updates to the documentation (EULAs). Still ACT 6.1 and WinPE 5.0 with WinPE 5.1 update option.

In addition to dism to following deployment components had new versions, but I have not yet learned if its just artifacts of the build process, or if they contain any updates.

Imagex.exe: updated to 6.3.9600.17095

wdsmcast.exe: updated to 6.3.9600.17237

USMT: (all tools) are updated to 6.3.9600.17237

image
The updated Patches folder.

 

Download the fourth release

For an offline download, simply download the adksetup.exe file to a temporary location, and run adksetup.exe /layout C:tmpofflineADK81.

image
The Windows ADK 8.1 folder once all bits are downloaded.

 

Upgrading to the September 2014 release of Windows ADK 8.1

To upgrade to the latest version, run adksetup, and run through the setup wizard.

image
Upgrading to the latest version of Windows ADK 8.1.

 

/ Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
5 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Hendrik
Hendrik
7 years ago

No worries, thanks for coming back on this.

Regards,

Hendrik

Admin
Admin
7 years ago

Sorry, don't know more than that.

/ Johan

Hendrik
Hendrik
7 years ago

Thanks would you know which issue it addresses on the splitted WIM files. To be honest, when creating an automated usb-deployment (static image) which supports UEFI I'm actually using splitted wim-files. As a UEFI boot sticks needs to be fat32, but wanted to be able to use just one USB key rather than two. It's for specific customer imaging requirements on i.e. tablets where there's just one USB slot.

Admin
Admin
7 years ago

It was a fix when using splitted WIM files, which almost nobody is 🙂

/ Johan

Hendrik
Hendrik
7 years ago

Thanks for pointing out the update points. You mention a bugfix to dism. What bugfix is this about, do you perhaps know?

Thanks…


>