Quick workaround for ADK 1703 issue
If you read about the issue with the ADK 1703 release that Aaron blogged about here, you know that there’s an issue installing the new ADK on Windows 10 and Windows Server 2016 if you are running Secure Boot (which you should be running and shouldn’t turn off). This is due to an improperly signed WIMMOUNT driver included in the ADK; we’re working on finding a way to publish an updated driver that is signed. There are two symptoms:
A popup from the Program Compatibility Assistant during the ADK installation.
A failure to mount any WIMs after ADK 1703 is installed. That manifests itself in MDT like this:
The interesting part of this: The driver included in the OS itself would work fine; it’s already properly signed. So just use that one instead of the one in the ADK. There’s probably several ways to go about this, but I’ll stick with simple: Use REGEDIT.EXE, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WIMMount, and edit the ImagePath value. It starts off like this:
Change the ImagePath to instead be:
And presto, now you can mount WIMs again: