Stateless VDI - Windows 10 1903 EventID 6005

Hey guys,

we are using stateless vdi machines and currently Windows 10 1803. We are using VMware Dynamic Environment Manager for user profiles and uses the vmware optimization tool for the gold image. We are using the "Windows 10 LoginVSI.com VDILIKEAPRO" template in 7.1 version. Everythink is working fine! Now we are trying to switch to Windows 10 1903 and we have sporadically a very very long login time. It tooks around 8-10mins on the "welcome" screen before it will switch to "windows will be prepared".

The VMware Logon Monitor show us a very long time for the user policy part:

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] ****************** Session Summary (User: DTS-SYSTEME\dtstest, Session: 1) *****************

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Logon Time: 238.54 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Logon Start To Hive Loaded Time: 0.56 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Logon Start To Classes Hive Loaded Time: 0.75 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Profile Sync Time: 0.00 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Windows Folder Redirection Apply Time: 0.00 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Shell Load Time: 8.69 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Total Logon Script Time: 2.93 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] User Policy Apply Time: 228 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Machine Policy Apply Time: 0 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Group Policy Software Install Time: 2.13 seconds

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] Free Disk Space Available To User: 45 GB

2020-01-03T10:49:39.237 INFO (0cd4-0e74) [LogonMonitor::LogSummary] ********************************************************************************************

But we dont apply any user policies from active directory. Every user setting is coming from DEM.

In the eventlog you can see EventID 6005: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event

Can someone help?



0 Kudos
3 Replies

I have reverted back to 1803. My management asked me sarcastically are we going to back to start using physical desktops again.

I edited my response, I meant the same thread refer by @andiwe79

With Great Regards,
0 Kudos

What ESXi Version and VMFS do you use?

Maybe you run into this issue with Win10 1809 and above on VMFS6: Re: windows 10 1809 slow

Best regards


0 Kudos
Hot Shot
Hot Shot

Are you using instant clones? I assume you have DEM logging enabled. Check your logs there and see what’s hanging. Misconfigured logon scripts will show similar symptoms to what you’re reporting.

Did you in-place upgrade your image to 1903, or start from scratch? If IPU, it’s best practice to reinstall your agents in correct order.