Windows ADK for Windows 10 v1703: Known issues, Workaround Fix

There were roughly issues reported of late regarding the installation of novel Windows ADK on Windows 10  v 1703 as well as Windows Server 2016 past times users running Secure Boot. While the principal movement of the employment remained unidentified, it was flora that the primary argue for the appearance of it was an improperly signed WIMMOUNT driver included inwards the ADK. This was perceived via 2 noticeable symptoms,

1. A popup from the Program Compatibility Assistant during the ADK installation.
2. A failure to mountain whatsoever WIMs later ADK 1703 is installed. That manifests itself inwards MDT similar this:

So, when you lot travail to install this version of the Windows ADK on a arrangement amongst SecureBoot enabled, the Windows Program Compatibility Assistant displays the next warning:

Windows ADK for Windows 10 v1703 issues & its workarounds

Fortunately, Microsoft has come upwardly up amongst a solution. It has published an updated driver that is signed. If you lot are non aware, several files included amongst the Deployment Tools characteristic of the Windows Assessment as well as Deployment Kit, including wimount.sys, are digitally signed amongst an older certificate. As such, these files are considered every bit skillful every bit “unsigned” past times latest operating systems, as well as thence blocked or stopped completely when SecureBoot is enabled. It is for this reason, Microsoft advises to run ‘Secure Boot’ as well as non plough it off.

Second, the wimount.sys driver is used past times DISM for mountain operations which is used on the Configuration Manager site server for creating as well as servicing kicking images, inwards addition, to perform offline servicing operations on OS Image as well as OS Upgrade Packages.

A postal service on Microsoft Technet weblog suggests, customers using Configuration Manager electrical current branch version 1702 as well as deploying Windows 10, version 1703 should essay the next workarounds.

The primary recommendation from Microsoft to unblock customers who are interested inwards deploying Windows 10, version 1703, via traditional OS deployment methods is to role the prior version of the Windows ADK, version 1607, for working amongst Windows 10, version 1703 kicking as well as OS images. This frontward compatibility is supported for basic imaging operations (capture/apply).

It is peculiarly noteworthy to yell hither that Windows 10 in-place upgrade as well as Windows 10 servicing produce non role whatsoever Windows ADK components. As a result, these scenarios stay unaffected past times the issue.

As an alternative to the above, Windows users tin ship away select to disable SecureBoot. While technically an option, Microsoft urges non to role it inwards production environments every bit it enhances the potential conduct chances to the server.

Microsoft has every bit good released a fix for this issue. For to a greater extent than data on this topic, watch TechNet blog.

Source: https://www.thewindowsclub.com/

Share This :