Slow initial login times

[m0tyrider]

Is anybody having very slow initial login times for there windows 10 image?

 

Using windows 10 ltsb, no metro apps (as per ltsb).

 

Getting approx 1 min and 30 seconds in my hyper V setup, would be even worse on actual student hardware.

 

 

Is there something I have forgotten to fix in my image?

 

Using local profiles, my default profile is 73mb.

 

Logins after the first one for that account are very quick, easily under 6 seconds.

 

There are no scripts being run yet as I am still testing everything before deployment.

Edited July 6, 2017 by m0tyrider

[ITJS2015]

Windows to has always had this issue with logging in on the first login, just make sure that before syspreping the machine that you turn off first sign in animation. This will help speed it up slightly as it does not show the animation of installing apps on a new profile.

 

Maybe Someone on hear could help you out but its more or less the same speed for everyone else

[m0tyrider]

Bugger, I already have the first sign in animation turned off via GP.

 

Not looking forward to what the end users say...!

[ITJS2015]

A huge hit would be your policies basically, try removing some policies and see what is you biggest policy. When doing this make sure that you do it on a fresh profile as doing it on an existing profile will already be downloaded but wont increase the size that much as it would be quicker then.

 

Try removing icons from startmenu or layout and just have icons on your desktop in a folder.

 

Everyone is still learning this new windows and there is no simple fix for it

[Fazza]

Not looking forward to what the end users say...!

 

I think it's a perception thing as if we had 1 min 30 second logons on all our computers our end users would say "blimey these are fast" - to us 1 min and 30 second log on times are extremely fast and 10 minute log on times are slow.

 

If you consider 1 min 30 secs to be slow what do you consider to be a fast logon?

[m0tyrider]

Fast logon, anything under 30 seconds....I am yet to try my image on any physical hardware yet. So that will be the real test, but 90 seconds on a vm isn't filling me with confidence.

[ifarmery]

I had the most success by following this guidance from - https://social.technet.microsoft.com/Forums/en-US/3e10447a-9976-4d40-9f31-de5e6c13b277/windows-10-first-logon-is-very-slow?forum=win10itprosetup

 

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 once login is complete, but they have no measurable impact on performance while they run.