January 19, 2017

Winpe 1607 Dot3svc fails to load – Workaround

In WinPE 1607 Dot3svc fails to load as I and many others have noted before. https://ccmexec.com/2016/09/dot3svc-does-not-load-using-winpeadk-1607/ Today on the comment to my post “Robert” posted the following workaround which seems to be working just fine!

Copy the following files from a windows 10 1607 installation 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.mfl

Thanks Robert for sharing this! All credit to your work!

6 Comments

Brad

Worked perfect for my MDT 1607 boot file.
January 20, 2017 Reply
Graham

I see two versions of 1607 in the VLSC; Jul ’16 & Nov ’16, does it matter which one I use? Thanks.
February 1, 2017 Reply
Greg

the service starts, but netsh lan show interface shows no interfaces. Are you guys able to do stuff with netsh?
February 2, 2017 Reply
Dale

Hi Guys,
Just trying to implement 802.1x for a customer and wondering what your steps are to get this happening. I have been able to get the dot3svc started but unsure where to head from here.

Also do you know if machine based certs can be used in this scenario?
Any assistance here would be greatly appreciated.
Cheers,
Dale
February 8, 2017 Reply
Anders Rodland

I have tested this as well with ConfigMgr 1610 and ADK1607, and can confirm this workaround is working.

Thank you !
February 11, 2017 Reply
Christoph Voigt

FYI, information on 802.1x with ADK 1703 is available at https://social.technet.microsoft.com/Forums/en-US/289f8703-d0f4-441c-bb7e-63e71ae40b57/winpe-10-1703-and-8021x-problem-with-netsh?forum=win10itprosetup
April 24, 2017 Reply