Thank you bird!bird wrote:We suspect the problem is some certificate or signature parsing issue caused by some slight change in the output from the microsoft signing tools or CA. However, in order to fix it we need the offending ntdll.dll and are eagerly waiting for the laptop with the insider build setup to feel like update itself so we can get it. With a bit of luck we'll have it fixed soon...
-bird
For your reference, when an Insider build is installed, it takes 12-48 hours of uptime on that build, before the Windows Compatibility Advisor runs and allows a newer build to be installed. I've confirmed with Jason Howard (@NorthFaceHiker on Twitter), one of the main Microsoft Insider devs, that there is no way to manually shortcut this currently. It's one of my key gripes about the Insider program
So ... when you install an Insider build, I'd recommend leaving it run for 48 hours, to be "ready" to be immediately offered the new build when it is available, and then access it via Windows Update, if that's your goal.
Thanks again!
Jacob