6-12 seconds Logon delay between "End Session: Logon" and "Begin Session: StartShell"

Roger Eklund 11 Reputation points
2020-12-11T10:37:47.627+00:00

I have seen this when i find other users logs aswell, its the same type of delay in all of them. What happens during this time? This is the one thing taking time during our logon process.

This is from the logs:

[11:11:16.129][tid:000014cc.00004434][INFO]           ===== End Session:  LoadProfile: d7dp
[11:11:16.129][tid:000014cc.00004434][INFO]           ===== End Session: Logon
[11:11:28.848][tid:000014cc.00004434][INFO]           ===== Begin Session: StartShell
[11:11:28.848][tid:000014cc.00004434][INFO]            User: S-1-5-21-613775786-3661600701-2283250920-403041 (d7dp)
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,225 questions
FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
463 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Jeremy Hurren 11 Reputation points
    2021-01-19T17:23:43.527+00:00

    This time (between End Session Logon and Begin Session Start Shell) is when FSLogix isn't actually doing any direct work. This is the time when Windows is loading the profile, and other services involved in the logon notification are doing their work. So this could be large profiles that take a lot of time. A new profile that has to be created from scratch will take extra time here. It could also be something like applying group policy.

    2 people found this answer helpful.
    0 comments No comments