locked
Settings to make Windows 10 Login Faster for first time use in a computer lab-Where are they? RRS feed

  • Question

  • Hi, can someone tell me what settings/Policies I need to apply to expidite the first time login for each user in a computer lab? It just takes for ever for the "Hi we are setting things up for you screen"  I know you can turn that portion off with a GPO but it still takes forever to do an initial setup.

    Thanks

    Wednesday, November 11, 2015 9:35 PM

Answers

  • Hi,

    Yes, just as Jack said, there is no way to disable "prepare Windows" screen so far.


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

    Friday, November 27, 2015 2:38 AM

All replies

  • Either you need to customise the image or use GP's.. Here's the policy that disables it : 

    Computer Configuration, Administrative Templates, System, Logon, Show first sign-in animation, Disable. 


    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, November 11, 2015 10:31 PM
  • Hi,

    Besides that, you also could use the registry to disable it:

    1. Open the Registry Editor.

    2. Located to

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

    3. Add the DWORD value named EnableFirstLogonAnimation

    4. Set its value as below:

    0 = Disable first sign-in animation
    1 = Enable first sign-in animation


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

    • Proposed as answer by Karen Hu Wednesday, December 2, 2015 1:57 AM
    Thursday, November 12, 2015 7:44 AM
  • Yea, I did that initially, but instead of the Tile welcome screen it all does it on the login screen.  I am just trying to speed this process up. 
    Thursday, November 12, 2015 1:31 PM
  • Hi,

    What's the meaning of "Tile welcome screen it all does it on the login screen"?

    Based on my test, after I disable first sign-in animation, I would sign in the new user account directly. It's very fast.


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

    Monday, November 16, 2015 9:10 AM
  • Whenever I set the "Computer Configuration, Administrative Templates, System, Logon, Show first sign-in animation" to Disable and a new user login,  they dont get the default windows setup "Slide show" but it sits on the login screen displaying "Preparing Windows."  It still takes the same amount of time to login.

    Tuesday, November 24, 2015 8:13 PM
  • Yes, this is correct, the time is taken setting up Windows for that user, not to display the welcome, there is nothing you can do except remove some applications during your imaging process so fewer setup during logon. This is a question I've asked several times, including to Microsoft reps directly, there is no answer or FAQ or official stance. IMO, Microsoft could allow this to be done in the imaging process but wants to control this so bad they are even willing to hear this complaint from enterprises, Windows 8 was no better...

    Jack

    Tuesday, November 24, 2015 8:22 PM
  • Hi,

    Yes, just as Jack said, there is no way to disable "prepare Windows" screen so far.


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

    Friday, November 27, 2015 2:38 AM
  • This has been driving me mad for the last month.  First time logon was around 2 minutes 40 seconds.  I've now got it down to around 22 seconds.  Here's what I've done so far.  Please bear in mind that much of this is totally unsupported; I've just been doing it in a test environment to try and get a grip on what's going on, and find where the delays are.  I probably wouldn't recommend doing this (especially step 3) in a live environment.

    1. Use Powershell to remove unwanted Provisioned AppX Packages (which get configured for each new user at logon).  You'll need to open Powershell as an admin. List them all with the command...
    Get-ProvisionedAppXPackage -online | select packagename

    Choose which ones you want, then remove the rest with the command...

    Remove-ProvisionedAppXPackage -online -PackageName Microsoft.ZuneVideo_2019.6.15731.0_neutral_~_8wekyb3d8bbwe

    This example removes Zune Video. I've set up a Powershell script that runs in my SCCM build capture task sequence and uninstalls a list of all the ones I don't want, so these apps are removed from our image.

    2. Remove as much as you can from ActiveSetup registry keys, which you can find at...

    • HKLM\Software\Microsoft\Active Setup\Installed Components
    • HKLM\Software\WOW6432Node\Microsoft\Active Setup\Installed Components

    Many of the sub-keys within Installed Components will have a value called 'StubPath', which generally contains an executable that is run to configure that component for the new user.  Examples include Windows Media Player, Adobe Reader, Google Chrome, Internet Explorer etc.  Copy the contents of the StubPath value, and add it to the following group policy...

    User Configuration > Administrative Templates > System > Logon > Run these programs at user logon

    Then configure a group policy preference to delete that Installed Component from ActiveSetup.  The result is that the executable will run immediately after login, when the user's desktop is already available.  I have removed absolutely everything that has a StubPath, with the exception of the Themes Setup component.  (Without this, I just get a black background without our corporate branding etc). You can see the processes running in Task Manager, but they have no measurable impact on performance while they run.

    3. Lastly, there are some apps you can't uninstall using the Powershell method described above because they are classed as 'System Apps'.  Examples are Windows Feedback, Contact Support, Edge, Cortana etc.  Although you can't uninstall them, you can break them.  You can find them in C:\Windows\SystemApps.  For example, I run the following command in a cmd file during our SCCM build...

    rename "C:\Windows\SystemApps\ContactSupport_cw5n1h2txyewy" DISABLED_ContactSupport_cw5n1h2txyewy

    Again, choose which ones you want, disable the rest.  (I don't think you can disable Cortana this way, as the service is always running so you can't rename the folder).  There are apparently some that will break your system if you disable them.  I'd leave ShellExperienceHost_cw5n1h2txyewy well alone.

    So that's what I've tried, and like I say, our first login is now around 22 seconds.  One annoying exception to this is that the first user to login after a reboot takes longer, maybe around 56 seconds.  If anyone has any other tips (especially ones that are actually supported and don't involve sabotaging system apps), I'd love to hear them!

    Thursday, December 17, 2015 9:47 PM
  • thanks for this information!
    this has been so frustrating. We have lab computers that are shared among dozens/hundreds of students who sit down randomly at a machine. So we essentially get the "new user experience" every day for every person....sigh
    Monday, March 21, 2016 11:19 PM
  • Or use Windows 10 LTSB which doesn't have apps.

    Tuesday, March 22, 2016 2:46 PM
  • Removing apps as he is doing was initially suggested by several but removing Run Once and/or Active Setup registry keys will affect the application for each user, as that is the mechanism to populate HKCU or AppData registry/files. This is unsupported because it's a hack, and by hack I mean both "manually changed" as well as "at risk or breaking something"...

    Jack

    Tuesday, March 22, 2016 3:12 PM
  • I'm pretty sure I made it clear in my post that it was unsupported and I wouldn't recommend doing it in a production environment. I was looking for suggestions that were a.) not hacky and b.) supported. Do you have any?

    As an aside, I'm not entirely removing the ActiveSetup stuff, I'm just moving it so it happens after the user is logged on.  So HKCU and AppData get populated, it just happens slightly later than normal

    Tuesday, March 22, 2016 3:53 PM
  • No, you are doing it as safe as you can and you made it clear, but Windows always has had a second user logon faster than the first. Companies with products to optimize systems (AppSense for example) with VDI systems, will have their product logon once with a service, then logoff to have the VDI session run faster for the first user to be assigned the machine. I would be a little worried about the logon time being so long after a reboot, wondering if Windows senses something isn't right? My fear is something breaking in a future upgrade/feature change, not enough to stop me if for personal reasons but certainly enough to stop me in the Corporate image...

    Jack

    Tuesday, March 22, 2016 5:44 PM
  • The problem is that on our student PCs, where the profile is deleted after logoff, and we do not use roaming profiles, every logon is effectively a first logon.  In the past mandatory profiles have helped us get around this, but they do not seem to work in Windows 10 (and from what I've read, the problem actually dates back to Windows 8).  They result in a non-functioning Start menu.  I'm using local profiles, that are deleted by a scheduled task shortly after logoff, so the profile has to be completely rebuilt at every logon.  I have found a couple of other things that have helped with my logon times:

    I had left IPv6 enabled, even though our environment is IPv4 only.  Disabling this shaved a few more seconds off logon time.  I'm guessing Windows tries to use IPv6 first, then fails over to IPv4.

    We are still using App-V 4.6 for some applications.  This was set to do a full sync of available applications at logon.  I've turned this off, and run the sync using a command line after the desktop is available.  Again, this saved several seconds.

    Overall, first logon is now down to less than 20 seconds, which I'm pretty happy with.  (On an SSD it's even better).  First logon after a reboot is still slightly longer, at around 25 seconds, which I can live with.  I'd love to know why that's the case though!

    Thursday, March 24, 2016 10:28 AM
  • Ron, under 20 seconds is fantastic! I'm working with Windows 10 LTSB, also in a student lab environment, and have used a local default profile modification tool called DefProf in the past with good results in Windows 7. I'm still around 2 minutes for a new user login. I forgot about the ActiveSetup stuff I used to remove from Win 7 so I'll be trying that again.

    How exactly do you get profiles to delete by scheduled task?

    Thanks for your informative post here!

    cheers,

    David Levine


    Tech Specialist

    Monday, May 23, 2016 8:06 PM
  • Just to let you know, there are no advantages to setting 'Fast Logon Optimization' for new users to sign in.

    By doing so, you disadvantage Group Policies from applying immediately at next logon, especially those group policies with need to load 'BEFORE' the user logs in.

    I work at a college and this feature has killed our roll-out for several group policies, and we have had to back-track on what went wrong.  Finally found that a technician had built an image of Windows 10 with this feature enabled.

    From Microsoft - https://technet.microsoft.com/en-us/library/jj573586(v=ws.11).aspx 

    Fast Logon Optimization and Group Policy processing


    By default in Windows 8.1, Windows 8, Windows 7, Windows Vista, and Windows XP, the Fast Logon Optimization feature is set for domain and workgroup members. Policy settings apply asynchronously when the computer starts and when the user signs in. As a result, these operating systems do not wait for the network to be fully initialized at startup and sign-in. Existing users are signed in by using cached credentials. This results in shorter sign-in times. Group Policy is applied after the network becomes available.

    Fast Logon Optimization is always off during sign-in when a user:

    • First signs in to a computer.

    • Has a roaming user profile or a home directory for sign-in purposes.

    • Has synchronous sign-in scripts.

    System_CAPS_noteNote

    Under the preceding conditions, computer startup can still be asynchronous. However, because sign-in is synchronous under these conditions, sign-in does not exhibit optimization.

    --- Furthermore --- from a description of Fast Logon Optimization feature
    https://support.microsoft.com/en-us/help/305293/description-of-the-windows-fast-logon-optimization-feature

    Be aware that, because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logons to apply changes. Additionally, changes that are made to the user object, such as adding a roaming profile path, root directory, or user object logon script, may take two logons to be detected.

    Wednesday, July 19, 2017 4:23 PM
  • windows 10 1809 has a quick first sign in option that goes along with shared pc mode.

    Tuesday, April 30, 2019 6:14 PM
  • windows 10 1809 has a quick first sign in option that goes along with shared pc mode.

    Can you share where this option is or how to get to it?
    Wednesday, November 6, 2019 7:52 PM