none
Sysprep Windows 2016 LTSB failed with setupdigetclassdevs & rearm error

    Question

  • I read on the net that the setupdigetclassdevs when syprep is quite common and yet to resolve. But I'm also getting a SLReArmWindows error. I have tried changing the skip rearm registry settings to 1 or 0, still same error. Image installed straight from ISO with some windows apps, latest windows updates applied, no universal apps loaded as it's a LTSB.

    2017-04-13 13:02:38, Error                 SYSPRP setupdigetclassdevs failed with error 0
    2017-04-13 13:02:39, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SLReArmWindows' from C:\Windows\System32\slc.dll; dwRet = 0xc004fe00
    2017-04-13 13:02:39, Error                 SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0xc004fe00
    2017-04-13 13:02:39, Error                 SYSPRP ActionPlatform::ExecuteActionList: Error in execute actions; dwRet = 0xc004fe00
    2017-04-13 13:02:39, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0xc004fe00
    2017-04-13 13:02:39, Error                 SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0xc004fe00
    2017-04-13 13:02:39, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0xc004fe00
    2017-04-13 13:02:39, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0xc004fe00
    2017-04-13 14:14:34, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2017-04-13 14:14:34, Error                 SYSPRP WinMain:Hit failure while processing sysprep re-specialize internal providers; hr = 0x8007001f

    Appreciated any suggestions/comments.

    Sunday, April 16, 2017 1:59 PM

Answers

  • Thanks, I was able to sysprep after activated windows. I shall try reloading image and see how it goes. I never thought I need to activate windows before sysprep, at least not for the Windows 7 and Windows 10 LTSB v1511.

    Really appreciated your help.

    • Marked as answer by N-T-S-L Wednesday, April 19, 2017 4:25 PM
    Wednesday, April 19, 2017 4:25 PM

All replies

  • Hi N-T-S-L,

    It seems that there is something wrong with the activation. Please open an administrator command line and run "slmgr /dlv" to check the activation information.
    Run "slmgr /rearm" to reset the activation information and run "slmgr /ato" to perform an automatic activation again.
    If there is any third party antivirus software installed, please turn it off temporarily or uninstall it.

    Best regards

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

    Tuesday, April 18, 2017 2:18 AM
    Moderator
  • Thanks for your tips.

    However, it still didn't work with the commands you suggested.

    DLV indicated the remaining windows rearm count is 1001.

    Rearm indicated error 0xC004FE00 on a computer running Microsoft Windows non-core edition, run slui.exe to display the error text.

    SLUI.exe Windows activation, an error has occurred

    ATO Activating Windows(R), EnterpriseS edition, Error: 0xC004F074 The software licensing service reported that the computer could not be activated. No key management service (KMS) could be contacted.

    BTW, we do not want to activate this windows installation as we are syspreping it for SCCM deployment.

    Tuesday, April 18, 2017 4:07 PM
  • Hi N-T-S-L,

    According to my test, it is not available to sysprep a machine that is not activated. So you'd better to activate it then sysprep it. Don't worry about the activation information, it will be removed automatically during the sysprep  process.


    Best regards


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

    Wednesday, April 19, 2017 8:51 AM
    Moderator
  • Thanks, I was able to sysprep after activated windows. I shall try reloading image and see how it goes. I never thought I need to activate windows before sysprep, at least not for the Windows 7 and Windows 10 LTSB v1511.

    Really appreciated your help.

    • Marked as answer by N-T-S-L Wednesday, April 19, 2017 4:25 PM
    Wednesday, April 19, 2017 4:25 PM
  • Somehow, the windows is still activated after I loaded the image. This is a big concern as we do not want to have any windows activation issues after the machines are deployed.

    FYI, I never received the error you posted above in related to validate the windows installation.

    When I run slmgr /rearm before sysprep, below error showed. It almost looks like it's using KMS channel for activation. In fact, we shall be using MAK license thru' SCCM to activate our 2016 LTSB deployment. Could this be the reason why the sysprep SLReArm failed??

    Thursday, April 20, 2017 2:59 PM