Microsoft is aware of an issue with the Windows ADK for Windows 10 Creators Update (1703) and is currently investigating the cause and a resolution. According to Microsoft…
When installing this version of the Windows ADK on a system with SecureBoot enabled, the Windows Program Compatibility Assistant will display a warning about Windows blocking the installation of a digitally unsigned driver.
There are currently two methods to workaround the issue until a formal fix is available:
- Use the prior version of the Windows ADK, version 1607, for working with Windows 10, version 1703 boot and OS images. This forward compatibility is supported for basic imaging operations (capture/apply). This is our primary recommendation to unblock customers that need to deploy Windows 10, version 1703, via traditional OS deployment methods (imaging). (NOTE: Windows 10 in-place upgrade and Windows 10 servicing do not use any Windows ADK components, thus those scenarios are unaffected by this issue.)
- Disable SecureBoot. While technically an option, it is not recommended in production environments as this increases the potential risk to the server.
Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in San Francisco in 2017!