There seems to be a bug in the Windows 10 1607 ADK when trying to load the components needed to for instance deploy a machine when using 802.1x in your network. The service fails to load with System Error 126 as shown in the screenshot below.
There are some comments about it on forums and as comments on blog posts as well.
For now the workaround would be to use WinPE from the Windows 10 1511 ADK.
Hi!
We had a case for Microsoft to look at this issue and we got the following answer today:
“This is, in fact, a BUG on the Product!
I am still trying to engage the team to provide a workaround, but the fastest reply I get is to use WinPE v1511 as there may not even be a fix for the v1607 version, because; although not having any specific timeline, the most probable fix can be included on the RS2 ADK, and back-port (the correction of the bug on previous version) may not even be feasible.”
Hello Erik, do you have find a workaround for this problem?
i found a workaround. Copy the following files from windows 10 1607 installtion to winpe:
%windir%\l2schemas\OneX_v1.xsd %winpewindir%\l2schemas\OneX_v1.xsd
%windir%\system32\l2gpstore.dll %winpewindir%\system32\l2gpstore.dll
%windir%\system32\onex.dll %winpewindir%\system32\onex.dll
%windir%\system32\en-US\onex.dll.mui %winpewindir%\system32\en-US\onex.dll.mui
%windir%\system32\wbem\en-US\l2gpstore.mfl %winpewindir%\system32\wbem\en-US\l2gpstore.mflI hope, that Micorosft fix this error fast.
Thanks for posting it here! seems to work just fine! Wrote a quick post about it as well, let me know if you want me to include your full name, blogs, twitter ..
https://ccmexec.com/2017/01/winpe-1607-dot3svc-fails-to-load-workaround/
Regards,
Jörgen
I’ve found and tried the same solution as Robert a couple of weeks ago. The files can be identified by comparing the .Cab files for the optional components for WinPE. There you’ll see there are more in the WinPE boot.wim files of ADK10 1511 then ADK10 1607. Copying the missing files from an existing Win10 1607 machine indeed allows you to start the service in WinPE 1607, but I wasn’t able to configure any interfaces because they wouldn’t show as they did with ADK 1511. If anyone could tell me how I could get these back so I can use Network Authentication, I would really appreciate it!
Hello.
Thanks for sharing this workaround, it got me one step further, but I am facing another problem. Using netsh commands works, I am able to enable and disable the adapter so the command works with interface name Ethernet. But when I run the command netsh lan add profile interface=”Ethernet” filename=”X:\8021x\EAPTLS_USER.XML” or netsh lan set eapuserdata filename=”x:\8021x\userid.xml” allusers=yes interface=”Ethernet” I receive the error : “There is no such interface on the system” I have tried the command in a lot of ways with not luck. I suspect that there are more files missing in the boot image. I am running sccm 1610 with the latest supported windows ADK. Earlier bootimages used the same commands and everything worked as it should. Anyone else facing this problem?
Regards
Thomas.
I guess it is testing time, this might be good news..
Windows ADK for Windows 10, version 1703 was released yesterday.
https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit
Regards
Thomas.