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).



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


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:


New driver:


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.


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


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


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

netsh int tcp set global autotuninglevel=normal


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!)

How to enable the sleep feature on Server 2008 with Hyper-V

The sleep and hibernate features are disabled when Hyper-V is installed on a Server 2008 (R2). This is by design.

Lets start a long journey to find a workaround ..


powercfg.exe /hibernate on


–> Fail.





Disable Hyper-V Service?

I stumbled upon this blog post:

You can have Hyper-V installed but the service not started by the following registry setting:

Windows Registry Editor Version 5.00



When the computer starts, all power management features are available.

If you need a VM (for a demo for example), Hyper-V can be started with the following command:

net start hvboot

Power management will be disabled again, until the next reboot.

As I don’t need Hyper-V most of the time this is the workaround for now! The journey wasn’t that long after all!

All credits to: