none
WinPE 10 (1607) and dot3svc - Error 126 starting service

    Question

  • I created an instance of WinPE 10 (x86) using the ADK version 1607 but cannot get my environment to work with 802.1x security.  When I launch into WinPE and try to start the dot3svc service, it spits out an error and says module not found.  Error 126.

    I reverted back to Windows ADK 1511 and it works normally. 

     
    Wednesday, August 17, 2016 4:34 PM

Answers

All replies

  • Hi,

    As Microsoft stated, there is no change on Network part in WinPE for Windows 10.

    You may consider to re-add additional package to WinPE, to enable 802.X support:

    WinPE-Dot3Svc

    Adds support for the IEEE 802.X authentication protocol on wired networks. For more info, see WinPE Network Drivers: Initializing and adding drivers.

    We can also feedback this issue onto Feedback Hub, in addition, I will also submit the feedback on my side.


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, August 18, 2016 10:14 AM
    Owner
  • Sorry I didn't mention it in my original post.  Yes, we add the dot3svc component and it's language-specific counterpart during the generation of our WinPE environment.  I'll see if another tech can confirm the issue independently just to rule out my PC. 
    Thursday, August 18, 2016 4:12 PM
  • OK, we went back to basics and made a plain x86 USB PE key with ADK 1607 and reproduced the problem. The only optional components we added were dot3svc cab and the en-us equivalent. We also added the drivers from Dell's WinPE10 driver pack.

    Here is a picture of the error when we tried to start the dot3svc service.

    Thursday, August 18, 2016 5:04 PM
  • I am also experiencing the same issue. Using the scripts that we use to build WinPE images in 1511 with 1607, the dot3svc will not start nor will the associated netsh lan commands work. Is this for a K2000 KBE? 
    Monday, August 22, 2016 2:39 PM
  • Hi,

    Please submit this issue onto Feedback hub and I will also log in our platform.


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 26, 2016 5:34 AM
    Owner
  • Hi,

    Please submit this issue onto Feedback hub and I will also log in our platform.



    Do you mean the Feedback Hub in Windows 10?  Is that the official way to log technical issues with WinPE?
    Monday, August 29, 2016 1:29 PM
  • Hi, 

    Yes, That is the official way. It collects all potential issues in Windows 10 and send the feedback to Microsoft. 


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 29, 2016 3:23 PM
    Owner
  • Hi!

    Did you get the solution for this? We are having the same problem.

    Friday, September 2, 2016 11:39 AM
  • Kate,

    The feedback hub will not let me submit a problem because my organization has group policies configured to limit diagnostic and usage data.  These screenshots show what I mean.

    Saturday, September 3, 2016 12:31 PM
  • Hi,

    I have feedback this issue in our platform.

    Hope it can be fixed in following updates.


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, September 5, 2016 5:19 AM
    Owner
  • Hello!

    Is there any solution or workaround for this?

    We're having the same problem and the Feedback HUB is limited with GPO.

    Tuesday, September 13, 2016 12:57 PM
  • I have opened a Premier Ticket with Microsoft/SCCM team to see if they have any information. If nothing else, I can get it 'officially' noted, instead of the weird, useless hub. We're in the same boat: 1511 ADK worked fine, 1607 ADK fails to start dot3svc.

    Friday, September 16, 2016 12:33 PM
  • I'm seeing the same thing. I really don't want to roll back to 1511 to to test but I may have to if I don't hear anything soon.
    Tuesday, September 20, 2016 12:23 PM
  • I just tried this today with RTM images and everything works. Now I'm having a hard time finding the WINRE.wim image inside the INSTALL.wim for any 1511 ISO. I start all my images with WINRE because it has the WIFI package.
    Wednesday, September 21, 2016 2:06 PM
  • Same thing here.  WinPE from ADK 1607 breaks the 802.1x service.  Sometimes I wonder if any QC happens at MS.
    Thursday, October 13, 2016 5:04 PM
  • Same issue for us.  Had to switch back to 1511 (with hotfixes) because our network has 802.1x protected ports.
    Tuesday, October 18, 2016 10:37 PM
  • Looks like an SCCM blogger stumbled onto this issue.  Hopefully it gains some more traction.

    http://ccmexec.com/2016/09/dot3svc-does-not-load-using-winpeadk-1607/ 

    Monday, October 24, 2016 7:54 PM
  • And now the new version of MDT released in the last week requires 1607... Microsoft has had 4 months to fix this problem and has not.
    • Edited by ToddMiller Wednesday, November 16, 2016 1:00 AM
    Wednesday, November 16, 2016 12:51 AM
  • There is an ADK preview (14965).

    https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewADK

    I downloaded it and tried to make a new WinPE environment and it still gives an error 126 starting the dot3svc service.  It seems like Microsoft doesn't care about some of it's enterprise customers.  I will be speaking to my TAM because clearly these forums are peer to peer support only.

    Tuesday, November 22, 2016 7:03 PM
  • I have created a Feedback Hub item for this

    feedback-hub:?contextid=81&feedbackid=23d99fd3-0600-4ab9-800b-63efe7b2f494&form=1&src=2


    Don [doesn't work for MSFT, and they're probably glad about that ;]





    • Edited by DonPick Wednesday, February 1, 2017 8:16 PM
    Wednesday, November 23, 2016 8:16 PM
  • I had opened a support case. It is a bug and will be solved in the next ADK. The problem is that it will not be available soon. :-(

    dtp1972

    Wednesday, November 30, 2016 6:18 AM

  • i found a workaround. Copy the following files from windows 10 1607 installtion in 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.



    Thursday, January 19, 2017 11:07 AM
  • DBFZ,

    Before I try this, we primarily use 32-bit WinPE environment.  I'm assuming you used the same architecture to get these files as the WinPE environment you are using, correct?

    Thanks!

    Thursday, January 19, 2017 2:00 PM
  • Have any of you with premier support cases open on this subject received positive or negative news on whether this is fixed in Creators? 
    Wednesday, February 1, 2017 2:59 PM
  • I opened a case with Premier support and all they could tell me is that it is a known issue and it will be fixed in the next major release of Windows ADK. They had no ETA.
    Wednesday, February 1, 2017 4:15 PM

  • i found a workaround. Copy the following files from windows 10 1607 installtion in 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.



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

    Edit: yep, HKLM\Software\Microsoft\dot3svc\Interfaces doesn't exist.  Hoping I'm just missing something.  Doesn't get recreated even if I restart the service.

    • Edited by agressiv Thursday, February 2, 2017 4:58 PM
    Thursday, February 2, 2017 4:49 PM
  • Has anyone heard anything more on this? is there a fix in the pipeline? I need to change some things in our custom boot media but if I'm going to do it, I don't want to use PE 10586 because then ill just have to rebuild again sooner.
    Wednesday, March 15, 2017 1:16 PM
  • OP here. I had a ticket opened with Premier Support and they told me this is a known issue and the only fix is to wait for the next version of WinPE and provided a dubious ETA of plus or minus 2 months.  They closed the ticket on December 8, 2016 even though I insisted the problem was not 'solved'.

    Wednesday, March 15, 2017 2:27 PM
  • OK - thanks for the info - I will send this over to my TAM and see if he can help get an answer - I certainly hope this is fixed in the PE build that accompanies Win 10 1703 but according to earlier posts in this thread it looks like the 14965 ADK Preview still has the bug. 
    Friday, March 17, 2017 4:07 PM
  • the service starts, but netsh lan show interface shows no interfaces. Are you guys able to do stuff with netsh?

    Edit: yep, HKLM\Software\Microsoft\dot3svc\Interfaces doesn't exist.  Hoping I'm just missing something.  Doesn't get recreated even if I restart the service.

    I'm wondering about the same issue. Microsoft says to use netsh to import network profiles. I can't import the network profile with netsh if it doesn't see an interface, and without a network profile it won't attempt 802.1x authentication.

    Is there a different way to configure 802.1x authentication in WinPE without netsh?

    Wednesday, April 5, 2017 2:07 PM
  • According to this thread, 802.1x is still broken in ADK 1703. I guess this thread and my premier support ticket weren't enough to convince the development team to fix it.

    https://social.msdn.microsoft.com/Forums/en-US/1fa43cc7-a82d-4dd3-8d28-f76fe2d7593e/hardware-development-kits-for-windows-10-version-1703-april-2017

    Thursday, April 6, 2017 7:09 PM
  • The dot3svc service starts in WinPE 10 1703.  For further issues using 802.1x authentication in winPE, see this thread.

    https://social.technet.microsoft.com/Forums/en-US/289f8703-d0f4-441c-bb7e-63e71ae40b57/winpe-10-1703-and-8021x-problem-with-netsh?forum=win10itprosetup

    Monday, April 10, 2017 7:16 PM
  • Wednesday, July 5, 2017 8:24 PM