none
"now we have some important setup to do" with SCCM 1810 and Win 10 1809 RRS feed

  • Question

  • Hi all,

               Similar issue to previous versions where Windows 10 the extremely annoying "Now we have some important setup to do" after first logon.

    Please don't point me to the links which show how to disable cortana voice - that is not the issue.

    The issue is that the machine finishes building, the user logs on, the "Now we have some important setup to do" stuff happens, it then logs the user back out... and they need to logon again.

    Im not interested in getting rid of the voice part of this, im interested in getting rid of all of it - there is no need for this complete rubbish in an enterprise deployment and its odd that this isn't disabled by default in all education and enterprise versions.... anyway, i digress.

    i have added the following to the unattend.xml within the OobeSystem pass - with no effect

          <OOBE>
            <HideEULAPage>true</HideEULAPage>
            <NetworkLocation>Work</NetworkLocation>
            <ProtectYourPC>1</ProtectYourPC>
            <HideLocalAccountScreen>true</HideLocalAccountScreen>
            <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
            <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    <SkipMachineOOBE>true</SkipMachineOOBE>
    <SkipUserOOBE>true</SkipUserOOBE>
          </OOBE>

    i realise that <SkipMachineOOBE> is deprecated - but i just want the thing gone - so gave it a crack.

    Monday, January 7, 2019 10:17 PM

All replies

  • Hi Ben_22,

    I see a similar discussion here.
    Https://community.spiceworks.com/topic/2062129-skip-cortana-in-sccm-task-sequence
    He uses the same code as you provided and is also invalid.

    But there are more attempts from him below.

    https://qtechbabble.wordpress.com/2018/02/02/fix-windows-10-image-stuck-on-just-a-moment-screen/

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
         <settings pass="oobeSystem">
              <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
                   <OOBE>
                        <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                        <NetworkLocation>Work</NetworkLocation>
                        <SkipMachineOOBE>true</SkipMachineOOBE>
                        <SkipUserOOBE>true</SkipUserOOBE>
                   </OOBE>
              </component>
         </settings>
    </unattend>

    Or the complete code should take effect.
    https://pastebin.com/RAMrhiXQ

    We could try it again. If you copy it, please note that the punctuation format and spaces.

    I hope it will succeed.

    Best regards,
    Yuxiang

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

    • Edited by Yuxiang Shi Tuesday, January 8, 2019 7:45 AM
    Tuesday, January 8, 2019 7:18 AM
  • Same issues being experienced here.

    Attempted to disable the cortana voice with a registry edit through the sysprep unattend file however the voice still says "Now we've got some important setup to do..."

    Microsoft support, what can be added to the unattend.xml to disable the cortana voice over during OOBE?

    Friday, January 11, 2019 12:00 AM
  • reg add HKLM\Software\Microsoft\Windows\CurrentVersion\OOBE /v DisableVoice /t REG_DWORD /d 1 /f

    adding as a step in the TS worked for me. the unattend.xml wasnt possible to get working.

    • Edited by T__16 Wednesday, January 16, 2019 8:33 PM
    • Proposed as answer by User36987 Sunday, January 20, 2019 11:13 PM
    Wednesday, January 16, 2019 8:33 PM
  • Thankyou. This has resolved the issue.

    Added a run command line TS step just after the "Apply Operating System" step with the following:

    reg.exe add "HKLM\Software\Microsoft\Windows\CurrentVersion\OOBE" /v DisableVoice /t REG_DWORD /d 1 /f

    Sunday, January 20, 2019 11:15 PM
  • I'm glad I'm not the only one having this issue. Ok for Cortana voice but what about the second part of the problem?

    * The issue is that the machine finishes building, the user logs on, the "Now we have some important setup to do" stuff happens, it then logs the user back out... and they need to logon again. *

    Is that also related to the Cortana voice issue?

    Thursday, February 28, 2019 5:46 AM
  • No - suppressing the voice and suppressing it all together are two totally different things - but as you can see from above - the goal here appears to be to mark the question as answered, not to actually answer the question.
    Thursday, February 28, 2019 3:25 PM
  • I encountered this at my latest client site and had no idea why i was getting this on first login but found the issue.

    1. Check if you have UAC GPO's applying to the OU that you are building your machine into. To solve this, i joined the computer into a staging OU and then moved the computer at the end of the task sequence via powershell script.

    Now machines build and apply the unattend.xml file correctly with no "Now we have some important setup to do" message with cortana on login.

    Here is the link for the PS script i used for those who need it.

    https://ccmexec.com/2018/03/move-the-computer-to-the-correct-ou-during-osd-ps-version/

    Sunday, March 17, 2019 2:40 PM
  • Even this wasn't enough…

    <OOBE>
      <HideEULAPage>true</HideEULAPage>
      <HideLocalAccountScreen>true</HideLocalAccountScreen>
      <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
      <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
      <SkipMachineOOBE>true</SkipMachineOOBE>
      <SkipUserOOBE>true</SkipUserOOBE>
    </OOBE>


    MCSE Mobility 2018. Expert on SCCM, Windows 10 and MBAM.


    • Edited by yannara Thursday, April 4, 2019 6:22 AM
    Tuesday, April 2, 2019 8:17 AM
  • Ben

    did you find an answer for this - its annoying the hell out of me at the moment !!


    bigmike

    Wednesday, April 3, 2019 1:10 PM
  • Hi, I too am suffering with this issue.

    I have found that when using a raw install.wim from iso, the issues is not present. However, if I use an image I have capture using a Build and Capture TS I suffer with the "We have some important setting up to do" before it dumps the user back at the logon screen.

    Obviously this is not something we can put out to our users, we are heavily invested in the Hybrid Image we have designed, however, as a test I have removed all of the applications and updates from the Build and Capture and seeing the same issue. 

    Has anyone had any further progress with this issue or suggestions?

    Friday, May 10, 2019 9:15 AM
  • We never had this issue with Win101703, 1709, 1803 or 1809 but it has come back with a vengeance in Win10 1903. 

    For those that want to know, this worked for us for Win10 1809 (and prior):

            <component name="Microsoft-Windows-Shell-Setup" 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">
                <Display>
                    <ColorDepth>32</ColorDepth>
                </Display>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    		<SkipMachineOOBE>true</SkipMachineOOBE>
    		<SkipUserOOBE>true</SkipUserOOBE>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                </OOBE>
                <ShowWindowsLive>false</ShowWindowsLive>
            </component>

    Now, with 1903 these are the primary issues:

    The OOBE Network is the only OOBE window that appears. If you have either SkipMachine or SkipUser the OSD will fail as it will state the answer file is invalid. To be fair, I can just about live with the Network one. It has no input, it just shows, which is a bit annoying. 

    I then can't help but think this is the cause of my next issue with Win10 1903 (and BTW, SCCM 1902)

    The login prompt appears straight after OOBE. If you log in, the machine has not performed a machine GPO update and therefore you are then presented with the First Sign In Animation for the user, even though we have a Machine GPO to stop that from appearing. It's almost like I need to add another reboot to the end of the TS, wait, or, more importantly, see if I can get rid of the Network OOBE.

    I'm tempted to split out the SkipOOBE sections and try either machine or user individually, but there are only so many hours in the day :)

    Current 1903 OOBE if anyone wants to collaborate:

                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                </OOBE>



    • Edited by Lapierre79 Wednesday, May 22, 2019 6:18 PM
    Wednesday, May 22, 2019 6:05 PM
  • I had the same problem a couple of years ago with 1709. I can't post a URL, so Google "A user is logged off at the “Now we can go look for any updates” message" or "microsoft 4049012" to get to the MS article about the issue.  

    I ran into a problem with this in 1809 though. I started having the OSD get stuck at "just a moment" while in the middle of an SCCM TS. Adding the "SkipMachineOOBE" and "SkipUserOOBE" resolved that but the original user logoff issue returned.

    Thursday, June 13, 2019 11:12 PM
  • I have simliar issue with 1809 but something is blocking "now we have important setup to do".  The build goes through the task sequence and just hangs on "Just A Moment" and then goes blank.  Cold reboot does eventually gets the "now we have important setup to do".  The depreciated settings skip OOBE for machine and user does bypass that but however when you attempt to login you get the same issue of Just A Moment and then the screen goes blank.

    I'm in the process of speaking to our network team to see if it is (google Windows 10 1803 - black screen during OOBE ITNinja article) .  something firewall related possible.

    Anyone experience this issue?

    Wednesday, June 19, 2019 10:13 AM
  •             <OOBE>
                   
    <HideEULAPage>true</HideEULAPage>
                   
    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    <SkipMachineOOBE>true</SkipMachineOOBE>
    <SkipUserOOBE>true</SkipUserOOBE>
                   
    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                   
    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                   
    <NetworkLocation>Work</NetworkLocation>
                   
    <ProtectYourPC>1</ProtectYourPC>
               
    </OOBE>
          

    Jesus, 1803 custom wim, even with these options in unattend.xml, I Still see the final screen :(


    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Monday, June 24, 2019 7:48 AM
  • Maybe this would help? https://keithga.wordpress.com/2017/12/11/silence-is-golden-during-setup/

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Monday, June 24, 2019 10:50 AM
  • Cortana cannot be disabled with PowerShell (Microsoft design). Still seeing this window appearing.

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.


    • Edited by yannara Wednesday, August 14, 2019 11:22 AM
    • Proposed as answer by yannara Friday, September 13, 2019 11:15 AM
    Wednesday, August 14, 2019 11:21 AM
  • I've had an 1809 TS working fine for a month or 2, all of a sudden having the same issue. WIM or XML not been changed so not sure why all of a sudden...

    the only think that's changed is AD OU of machines and GPOs

    Friday, September 13, 2019 10:45 AM
  • This works for me in 1903 (and previous versions).

    <OOBE>
    	<HideEULAPage>true</HideEULAPage>
    	<ProtectYourPC>3</ProtectYourPC>
    	<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    	<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
    	<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
    	<HideLocalAccountScreen>true</HideLocalAccountScreen>
    	<SkipMachineOOBE>true</SkipMachineOOBE>
    	<SkipUserOOBE>true</SkipUserOOBE>
    </OOBE>


    • Proposed as answer by rga6 Friday, September 13, 2019 8:33 PM
    Friday, September 13, 2019 8:33 PM
  • Can you post your entire unattend.xml file? I can't get this to work in my lab...
    Friday, September 13, 2019 10:28 PM
  • Removed some personally data, but here it is.  Side note that I vaguely remember reading somewhere that users may have issues if they don't use en-US language (see the bottom of my file). If you're not using that... try using that.

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="specialize">
            <component name="Microsoft-Windows-UnattendedJoin" 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">
                <Identification>
                    <Credentials>
                        <Domain></Domain>
                        <Password></Password>
                        <Username></Username>
                    </Credentials>
                    <JoinDomain></JoinDomain>
                </Identification>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" 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">
                <RegisteredOrganization></RegisteredOrganization>
                <RegisteredOwner></RegisteredOwner>
                <TimeZone>Pacific Standard Time</TimeZone>
                <ComputerName>%MACHINENAME%</ComputerName>
            </component>
            <component name="Microsoft-Windows-TerminalServices-RDP-WinStationExtensions" 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">
                <UserAuthentication>2</UserAuthentication>
            </component>
            <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" 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">
                <fDenyTSConnections>false</fDenyTSConnections>
            </component>
            <component name="Microsoft-Windows-Deployment" 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">
                <RunSynchronous>
                    <RunSynchronousCommand wcm:action="add">
                        <Description>Disjoint Namespace Fix</Description>
                        <Order>1</Order>
                        <Path>reg add HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /v SyncDomainWithMembership /T REG_DWORD /d 0 /f</Path>
                    </RunSynchronousCommand>
                </RunSynchronous>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" 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>
                    <HideEULAPage>true</HideEULAPage>
                    <ProtectYourPC>3</ProtectYourPC>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <SkipMachineOOBE>true</SkipMachineOOBE>
                    <SkipUserOOBE>true</SkipUserOOBE>
                </OOBE>
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value></Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Description></Description>
                            <DisplayName></DisplayName>
                            <Group></Group>
                            <Name></Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <RegisteredOrganization></RegisteredOrganization>
                <RegisteredOwner></RegisteredOwner>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="wow64" 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>en-US</InputLocale>
                <SystemLocale>en-US</SystemLocale>
                <UILanguage>en-US</UILanguage>
                <UserLocale>en-US</UserLocale>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim:e:/media/sw_dvd5_win_ent_10_1703_64bit_english_mlf_x21-36478/sources/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>


    • Edited by rga6 Saturday, September 14, 2019 12:40 AM
    Saturday, September 14, 2019 12:38 AM
  • I think it has something to do with an update released within the psat three months. When I did a quarterly Build and Capture is when this started for me. Before that the following had worked for a few versions and captures:

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
         <settings pass="oobeSystem">
              <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
                   <OOBE>
                        <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                        <NetworkLocation>Work</NetworkLocation>
                        <SkipMachineOOBE>true</SkipMachineOOBE>
                        <SkipUserOOBE>true</SkipUserOOBE>
                   </OOBE>
              </component>
         </settings>
    </unattend>

    Sunday, November 17, 2019 1:38 AM