Windows 10 - Preparing Windows

[Liam]

Im aware that this has been covered many times before but has anyone actually managed to reduce the time it takes to log a windows 10 machine in.

It seems that computers process the user group policy settings quickly and then hang on 'Preparing Windows'. As you may already know, if you press ctrl alt del and press escape it kills whatever process is running and presents the desktop. Surely there is a way to speed this up? its just not good enough that we cannot control this.

 

Im using LTSB too so all the 'crap' is stripped out already so its not that its preparing the apps etc. Subsequent logins are quick subject to having the profile on the pc but they clear periodically.

 

Is this just what we need to expect now?

 

I think MS assume everyone has their own device, but the reality in education is quite different. Teaching and learning cannot wait as they say and i really need to try and improve things here.

 

I wouldnt mind, but its not that its slow slow. Its just not as quick as the 6 seconds i had it down to in Windows 7.

 

The only plus of Windows 10 is that its pretty reliable and we dont seem to get OS failures etc like we did in WIn 7

[jslate1980]

Have you tried copying a default profile to the net logon folder?

[free780]

On SAC we are now on the 5th Windows 10 release and I can't see this changing. From the MS perspective it's 1:1 devices as that's what an ipad is. You could investigate user profile disks but you'll need a lot of storage. When windows 10 S mode is ready this is supposed to improve logins but you cant run Win32 apps.

[alfatec]

All down to how you make your default profile. See some of my posts in relation to this. we have first login on 1709 education to about 20 secs.

[MrKJLS]

I'd be interested in this as well, sharing is caring

 

Preparing Windows is the slowest part of log in, I'd like to cut that down.

[mdrabble]

Ditto for wanting to cut down login times. Mine are anything from 40sec to 2 mins depending when you pc is turned on!

[sparkeh]

Using the default profile method above and SSDs had a big impact for us

[ful56_uk]

So what’s the correct method for creating the default profile? This is our longest part of our login. Would love to improve this too

[snagrat]

Can the Default Profile be moved between domains etc?

 

If someone has a working one couldn’t they just share with everyone as long as there isn’t too much amendment to it?

[mdrabble]

Can the Default Profile be moved between domains etc?

 

If someone has a working one couldn’t they just share with everyone as long as there isn’t too much amendment to it?

 

+1 for that idea as well :-)

[Liam]

Id be interested in this.. I cant deal with slow logins anymore.

[MrKJLS]

Does anyone know how to do this?

[damien_mason]

Hi Liam,

 

Have you tried asking other people that you work with, say a third party company. Sometimes getting in touch with the managing director can really help! I know a great company if you need, just send me a message

 

Thanks

[gshaw]

Would be interesting if you benchmark LTSB vs the current 1709 Edu build - the version the last LTSB was built on (1607) was horrific for first logins but that's improved a lot in 1703 and 1709

[Liam]

So i have significant reduced this now with a desktopswitchtimeout entry and deleting some stubpath settings

The next thing casuing the delay if folder redirection for start menu's. Its about ten seconds.

 

If i can nail that i think i have it to about 13 seconds on first login.

[jmak]

So i have significant reduced this now with a desktopswitchtimeout entry and deleting some stubpath settings

The next thing casuing the delay if folder redirection for start menu's. Its about ten seconds.

 

If i can nail that i think i have it to about 13 seconds on first login.

What magic are you working? I've stripped all but the essential modern apps out (I have camera, photos, store, calculator and 3d paint, but everything else is gone). The "Happy to see you - please wait while we get things ready" crud takes waaay more than 13 secs for us. SSDs, 4GB RAM and modern processors. It's not awful for standard users, but a pain for shared student devices.

 

Suggestions welcome.

[mdrabble]

I had a play with desktopswitchtimeoutbut that didn't really improve times - just gave me a black screen instead of preparing windows.

 

What subpaths settings did you delete?

[Liam]

I have it to ten seconds now with ssd. the black screen lasts about a second and half and you see the stubpath stuff running. I have found that if i felete too much from stub path it signifitcatly slows this proces down so i am being careful what i delete now.

 

Wifi devices are 25 seconds.

 

Folder redirection is still far too long. If this was quicker it would be so much better

 

- - - Updated - - -

 

I stripped out of the the 'crap' from the wim directly too. This made a difference from doing it any other way

[maark]

I have it to ten seconds now with ssd. the black screen lasts about a second and half and you see the stubpath stuff running. I have found that if i felete too much from stub path it signifitcatly slows this proces down so i am being careful what i delete now.

 

Wifi devices are 25 seconds.

 

Folder redirection is still far too long. If this was quicker it would be so much better

 

- - - Updated - - -

 

I stripped out of the the 'crap' from the wim directly too. This made a difference from doing it any other way

 

I tried desktopswitchtimeout and it seems to work well - black screen just for a second as above.

Have not tried stub path yet. This is with a roaming profile that exists on server but user not logged on local machine before. Am also using uev. I deny access to onedrivesetup.exe in syswow64 - this reduces profile size.

With all these on version 1709 i am getting logon down to 23 seconds - this is on wireless without SSD.

[ollyyllo]

Folder redirection is still far too long. If this was quicker it would be so much better

 

Have you tried changing the "Move the contents of *folder* to the new location" to Disabled for each redirected folder.

 

If you don't have a requirement to copy anything over, it might be worth testing.

 

For example, the time it takes to process the folder redirection policy (i5 PC with SSD)...

 

If I have it set to Enabled for all redirect folders

the very first login from a new user = 50 sec

first login on a different PC = 9 sec

subsequent logins = 0 sec

 

If I have it set to Disable for all redirected folder

very first login from a new user = 2 sec

first login on a different PC = 2 sec

subsequent logins = 0 sec

 

I don't pre-populate the new users folders, that also might make a difference, not tested that yet.

[Liam]

Have you tried changing the "Move the contents of *folder* to the new location" to Disabled for each redirected folder.

 

 

Yes - i always disable that and grant the user excludive rights.

 

I just dont know why it hangs for ten seconds.

 

Im thinking its some sort of permission issue .

[ful56_uk]

Do you do anything with the desktop.ini files?

[Liam]

Do you do anything with the desktop.ini files?

 

No not usually. Although I remember it used to do this with work folders as it was trying to create a file and couldn’t . I can’t remember what it was but I remember it renamed the work folders and I had to create a docs subfolder.

 

I’m convinced it’s a desktop.ini issue though. So kind of permissions I assume

[ful56_uk]

Are you blocking it with file resource manager? We was I turned it off and now letting it do its thing, knocked 20 second off first login

[Liam]

Ah..... I could be you know! I’ll check now.. I used to do that for work folders