Winlogon Notification Subscriber taking foever!

[Chuckster]

I get 2 errors.

 

First one is Event ID 6005

The winlogon notification subscriber is taking long time to handle the notification event (CreateSession).

 

Followed an hour or so later with the Event ID 6006

The winlogon notification subscriber took xxx second(s) to handle the notification event (CreateSession).

 

 

The screen is stuck at Applying Computer Settings and the quickest it's been for me to get to the login screen was 8004 seconds!!!!!!!!!!!!!

 

 

I've applied the following hotfixes which claim to fix the problem(s) but to no avail:

You encounter a long logon time after you enable the "Do not automatically make redirected folders available offline" Group Policy setting in Windows 7 or in Windows Server 2008 R2

Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7

 

 

I've disabled IPv6 on the LAN and WLAN. Also the same on both DCs

I've disabled Autotuning with the command: netsh interface tcp set global autotuninglevel=disabled

I've installed all the latest drivers

Disabled Card Reader

Added the registry key of GpNetworkStartTimeoutPolicyValue with the value of 1 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

I moved the computer object to a unmanaged OU (without policies applied), ran gpupdate /force and rebooted but the problem still exists.

 

I am now pulling my hair out over this! I've been at it since last week and haven't managed to reduce the time to within 60 mins.

 

Has anyone experienced this and, if so, what was your solution?

Edited May 9, 2012 by Chuckster

[Chuckster]

After 2 days of disabling everything in my single GPO of Comp Config, and re-enbaling everything one bit at a time, I discovered just now that disabling "Run logon scripts synchronously” cured my problem!

 

No more Event IDs 6005 and 6006! Hurrah!

 

This is found under Computer Configuration\Policies\Administrative Templates\System\Scripts

[SimonWindisch]

In my case it was a Multipoint Server 2011

 

I had an extra 10 network cards defined. I disabled all of these, turned off IPv6 and the problem went away.

[Yesdude]

the answers here are correct, but more information might prove helpful, so here it is...

 

When you get these Event ID's in Event Viewer Application Log:

6000: The winlogon notification subscriber was unavailable to handle a notification event.

6001: The winlogon notification subscriber failed a notification event.

6005: The winlogon notification subscriber is taking long time to handle the notification event (CreateSession).

6005: The winlogon notification subscriber is taking long time to handle the notification event (Logoff).

6006: The winlogon notification subscriber took xxxx second(s) to handle the notification event (CreateSession).

6006: The winlogon notification subscriber took xxxx second(s) to handle the notification event (Logoff).

 

Open Group Policy Editor

Start\Run\gpedit.msc

 

Computer Configuration\Administrative Templates\System\Scripts

Set the following:Specify maximum wait time for Group Policy scripts: Enabled (Options: Seconds, 60)

Run logon scripts synchronously: Disabled

 

Note: Max wait time set to 60 seconds or whatever you are comfortable.

Edited June 14, 2018 by Yesdude