Winlogon Init delay for about 40 seconds

[softshape]

Hi all,

I did bootprep as described on and found that the boot time didn't change much. Xperf result shows that Winlogon Init becomes (almost) idle for about 40-45 seconds -

http://www.irk.fm/files/tmp/bootprep-6.png (screenshot)

http://www.irk.fm/files/tmp/bootPrep_BASE+CSWITCH_6.zip (raw result, 12 Mb)

But looking at xperf report I cannot understand the reason of this idle interval. How to find it ?

Windows version is 7 64-bit.

Thanks,

Jury.

[cluberti]

XPerf isn't necessarily meant to give you the ultimate answer, it's meant to show you where to further troubleshoot (unless the problem is so obvious that it makes sense from the xperf data alone). In this case, 40 second delays in winlogon init usually means policy issues - enable winlogon logging to see what it is (or isn't) doing during that time, because that is a long time:

Fixing Group Policy problems by using log files

How to enable user environment debug logging in retail builds of Windows

How to read a userenv log part 1

How to read a userenv log part 2

Interpreting Userenv log files

[softshape]

I've enabled logging, the result is on http://www.irk.fm/files/tmp/gpsvc.log - I see the gap in it, but there are no clear error messages or warnings. I mean, error message is here but not really clear -

GPSVC(2e8.a24) 19:56:07:309 CGPNotify::UnregisterNotification: Entering with event 0x298

GPSVC(2e8.a24) 19:56:07:309 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(2e8.a24) 19:56:07:309 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0

GPSVC(3b4.194) 19:56:07:340 CGPNotify::UnregisterNotification: Entering with event 0x204

GPSVC(3b4.194) 19:56:07:340 CGPNotify::AbortAsyncRegistration: No asyn registration is pending

GPSVC(3b4.194) 19:56:07:340 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0

GPSVC(2e8.2f8) 19:56:40:741 CGPNotify::RegisterForNotification: Entering with target Machine and event 0x29c

GPSVC(2e8.2f8) 19:56:40:788 Client_InitialRegisterForNotification: User = machine, changenumber = 0

GPSVC(2e8.2f8) 19:56:40:788 Client_RegisterForNotification: CheckRegisterForNotification returned error 0x6ba

GPSVC(2e8.2f8) 19:56:40:788 CGPNotify::RegisterForNotification: Service not RUNNING. waiting

GPSVC(2e8.2f8) 19:56:40:788 CGPNotify::RegisterForNotification: Trying to recover from error 1722

- it's 33 seconds delay. Any ideas about "error 1722" are really appreciated.

[cluberti]

Error 1722 is "RPC_S_SERVER_UNAVAILABLE", so it's unable to make an RPC connection - however, it's probably a local RPC (LRPC) call given it's trying to run "RegisterForNotification" in winlogon itself. I wonder if your network card driver is at fault here, or if something 3rd party on the machine that would normally be running in winlogon is failing to register itself with callback events properly.

Does running the following 2 commands (and rebooting) change this at all?

netsh int tcp set global rss=disabled
netsh int tcp set global autotuning=disabled

If that doesn't help, your next best bet is autoruns, disable anything not absolutely critical for boot (including stuff in the winlogon tab) and see if that changes the behavior any.

[softshape]

I've installed autoruns and disabled all the things which looked unnecessary. I've also disabled bluethooth in the BIOS and applied netsh commands you suggested. Boot time remained the same. But after that I've applied bootprep again and, oh my God, it started to boot two times faster! So, thank you for your help!

[cluberti]