none
windows 10 stuck on just a moment RRS feed

  • Question

  • I have inherited Windows 10 1703 task sequence. I am having an issue after the OS is installed it just sits on " just a moment" screen. I do not see anything in BDD or SMSts log files.

    Installing on VM so i dont think drivers is an issue.

    What can i do to find an issue? 

    Thank you.

    Thursday, July 20, 2017 3:38 PM

All replies

  • Thanks for the quick reply. The unattend.xml file did not change from 1607?

    Thank you.

    Thursday, July 20, 2017 3:51 PM
  • Best is to generate a new Unatttend XML for a new Build. But you can try the old one.
    Thursday, July 20, 2017 4:07 PM
  • I am reading the link for updating the wim file.

    1. DISM updates.

    2. Boot the image to complete the update process, and then clean up the image

    I dont understand this part? If i DISM in updates then why do i need to boot/cleanup/ and recapture?

    3. Use Sysprep to generalize and shut down the PC

    4. Recapture the Windows image

    When i DISM in updates and commint to changes arent they already included? why do i need to recapture?

    Thanks for the help.

    Thursday, July 20, 2017 5:54 PM
  • No you can do it offline.

    For example on Powershell:

    Mount-Image

    Add-WindowsPackage

    Dismount-WindowsImage

    Thursday, July 20, 2017 5:57 PM
  • Thats what i though.

    Installing ADK and will try it. Do i need to do anythign to boot.wim?

    Thursday, July 20, 2017 6:03 PM
  • No

    Thursday, July 20, 2017 6:22 PM
  • I have added the msu using DISM and still the same issue. 

    Just sits @ "Just a moment" screen.

    I cant open cmd at this point. Is there anythign i can do to find out what is the problem?

    Friday, July 21, 2017 6:04 PM
  • Hi,

        Have you also the way adding an Unattended file (as a package) into the step "Apply Operating System"? Seem that this works in most scenarios.

    Regards,

    Jimmy 


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





    Sunday, July 23, 2017 7:44 AM
    Moderator
  • Hi,

    I also came across the same issue. That's correct it seems to be a bug, Microsoft might be working on it. In the meantime, you can change the below settings in unattended.xml. It worked for us.


    Thanks,







    • Proposed as answer by RakeshSahoo Friday, August 18, 2017 3:21 PM
    • Edited by RakeshSahoo Friday, August 18, 2017 3:24 PM
    Friday, August 18, 2017 3:17 PM
  • Hello,

    So I have an unattend.xml file in my task sequence :

    And I have two versions I have tried; And neither stop the JUST A MOMENT:

    Version One:

    <OOBE>
            </UserAccounts> <OOBE>
     <SkipMachineOOBE>true</SkipMachineOOBE>
     <SkipUserOOBE>true</SkipUserOOBE>
     <HideEULAPage>true</HideEULAPage>
     <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
     <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
     <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
     <HideLocalAccountScreen>true</HideLocalAccountScreen>
     <ProtectYourPC>1</ProtectYourPC>
            <NetworkLocation>Work</NetworkLocation>     
            </OOBE>
           <RegisteredOrganization>DAS BEST</RegisteredOrganization>
           <RegisteredOwner>Windows User</RegisteredOwner>
           <TimeZone>Eastern Standard Time</TimeZone>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <InputLocale>0409:00000409</InputLocale>
          <SystemLocale>en-US</SystemLocale>
          <UILanguage>en-US</UILanguage>
          <UserLocale>en-US</UserLocale>
        </component>
      </settings>
      <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <OOBE>
     <SkipMachineOOBE>true</SkipMachineOOBE>
     <SkipUserOOBE>true</SkipUserOOBE>
     <HideEULAPage>true</HideEULAPage>
     <HideLocalAccountScreen>true</HideLocalAccountScreen>
     <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
     <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
     <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    <DriverPaths>
            <PathAndCredentials wcm:keyValue="1" wcm:action="add">
              <Path>\Drivers</Path>
            </PathAndCredentials>
          </DriverPaths>
        </component>
      </settings>
    </unattend>

    Version Two:

    <OOBE>
            </UserAccounts> <OOBE>
     <SkipMachineOOBE>true</SkipMachineOOBE>
     <SkipUserOOBE>true</SkipUserOOBE>
     <HideEULAPage>true</HideEULAPage>
            <NetworkLocation>Work</NetworkLocation>
            <ProtectYourPC>1</ProtectYourPC>
            <HideLocalAccountScreen>true</HideLocalAccountScreen>
            <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
            <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
          </OOBE>
          <RegisteredOrganization>
          </RegisteredOrganization>
          <RegisteredOwner>
          </RegisteredOwner>
          <TimeZone>
          </TimeZone>
          <CopyProfile>true</CopyProfile>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <InputLocale>0409:00000409</InputLocale>
          <SystemLocale>en-US</SystemLocale>
          <UILanguage>en-US</UILanguage>
          <UserLocale>en-US</UserLocale>
        </component>

    Can someone tell me what I am missing.....

    Tuesday, August 29, 2017 11:51 AM
  • Hi Jess,

        Could you please post your question in a new thread instead of appending it here? Thank you.

    Regards,

    Jimmy


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

    Wednesday, August 30, 2017 2:11 AM
    Moderator
  • This will cause the OOBE process to be skipped, which is not recommended. 

    I had this same issue - Win10 Pro, build 1803, stuck at "just a moment" forever, during the OOBE process, after a sysprep. 

    The reason was the SetupComplete.cmd script, mentioned here in the Microsoft documentation for manufacturers: docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup

    I had included a pause for debugging purpose, which chocked the entire OOBE process. 

    I found the answer in the logfile located here: C:\Windows\Panther\setupact.log - that logfile stated clearly that it found a user script and ran the script in the background with no UI. Great... :-)

    AT


    Saturday, June 9, 2018 8:43 PM
  • @Allan Thisgaard,

    That is exactly what happened with mine! I set a pause at the end of SetupComplete.cmd and forgot about it after testing.

    I couldn't figure it out until I came across this and it jogged my memory that I had done that.  Thank you for sharing!  Saved me a lot of grief as I was about to redo the image again from scratch to resolve the issue!  You rock sir!

    -Q


    • Edited by QzMicro Thursday, August 16, 2018 11:39 PM
    Thursday, August 16, 2018 11:36 PM