ADK

OS Deployment – Installing ADK 1703 on Windows Server 2016 could fail

Update:It does not happens on all WS2016 machines, it happens only on computer where Secure Boot is enabled. This also means that this will happen on every machine that is using Secure Boot, regardless of OS version. It is a confirmed bug.

Yesterday Microsoft released Windows 10 1703 and also ADK 1703. But it fails to install correctly, the ADK actually installs, but it is the WIM mount driver that fails, du to this absurd message.

Install ADK 1703 on windows server 2016 - 2

A digitally signed driver is required

The message indicates that the driver Windows Overlay Filter is not signed.

The Solution:

According to this https://social.msdn.microsoft.com/Forums/en-US/1fa43cc7-a82d-4dd3-8d28-f76fe2d7593e/hardware-development-kits-for-windows-10-version-1703-april-2017?forum=wdk , the solution is to disable Secure Boot, really???

image

/mike

Categories: ADK, OS Deployment, OSD

Tagged as: , ,

2 replies »

  1. Yes, can confirm this is OS independent, this happened to me too when installing ADK 1703 on both Win10 7103 and Windows Server 2012 R2. Both devices Hyper-V VM and Workstation had Secureboot Enabled.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.