Server 2008 R2 Slow startup while applying computer settings

I’ve had some trouble with slow logon on Windows Server 2008 R2. The “Applying Computer Settings”-part takes about two minutes!

The eventlog shows two records about this issue:

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

image

And:

The winlogon notification subscriber <GPClient> took xxx seconds to handle the notification event (CreateSession).

image

I stumbled upon some possible solutions. The first was updating the NIC driver. As I’m using the wireless network card, I’m only updating this one.

Updating NIC driver

Old driver:

image

New driver:

image

Drivers are updated but the logon time wasn’t reduced by a single second. Crying face

Disable Computer GPO’s

Second try was moving the computer object to a unmanaged OU (without policies applied), run gpupdate /force and rebooted some times .. but the problem still exists.

GpNetworkStartTimeoutPolicyValue

Third try: adding GpNetworkStartTimeoutPolicyValue with value 1 to the registry:

image

Maybe it’s a service or application on the computer itself .. ? I disabled some 3rd party (non Microsoft) services, but the problem remains.

Disable IPv6?

–> no luck

Disable CardReader?

–> no effect

Disable Autotuning?

netsh int tcp set global autotuninglevel=disabled

image

Didn’t solved it either, so I enabled Autotuning again:

netsh int tcp set global autotuninglevel=normal

Patches/Hotfixes?

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

KB2525332: 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

–> This hotfix fixes the slow logon issue for me! (I’m using redirected folders!)

4 thoughts on “Server 2008 R2 Slow startup while applying computer settings

  1. Wesley

    If this works, you are the man. I haven’t had a chance to try it yet but your documentation supports that you know what your doing! Thanks for helping out a fellow IT member.

  2. Tim

    Thank you so much for the information. My problem was the KB2617858. I searched forever to find a solution and that was it!

Comments are closed.