0

My i5 desktop Windows 10 Pro is taking over 5 minutes to boot--with a SSD. I have run the xBootMgr profile and it shows winlogon.exe starts immediately and for 2.50 min of the 5.83 min boot time, there is nothing--other process or disk activity going on during this period. Any suggestions has to how to determine what winlogon is waiting for?

xBootMgr Summary

0

Lookig in the generic Events table for Events from the Microsoft-Windows-Winlogon provider I can see that the CreatePrimaryTerminal task takes over 200s to finish.

enter image description here

3 years ago I saw this, too, and here font files caused such a long delay. Look if this also applies to you.

But it must have someting to do with fonts. Looking at the callstack shows, that the CreatePrimaryTerminal function loads fonts:

Line #, Process, Stack Tag, Stack, Thread ID, Count, Weight (in view) (ms), TimeStamp (s), % Weight
9, , ,   winlogon.exe!WinMain, , 107, 106,712051, , 0,01
10, , ,   winlogon.exe!CSession::CreatePrimaryTerminal, , 107, 106,712051, , 0,01
11, , ,   winlogon.exe!CreatePrimaryTerminal, , 107, 106,712051, , 0,01
12, , ,   |- user32.dll!CreateWindowStationW, , 106, 105,712051, , 0,01
13, , ,   |    user32.dll!CommonCreateWindowStation, , 106, 105,712051, , 0,01
14, , ,   |    user32.dll!NtUserCreateWindowStation, , 106, 105,712051, , 0,01
15, , ,   |    ntoskrnl.exe!KiSystemServiceCopyEnd, , 106, 105,712051, , 0,01
16, , ,   |    win32kfull.sys!NtUserCreateWindowStation, , 106, 105,712051, , 0,01
17, , ,   |    win32kfull.sys!xxxCreateWindowStation, , 106, 105,712051, , 0,01
18, , ,   |    |- win32kfull.sys!xxxInitTerminal, , 102, 101,694054, , 0,01
19, , ,   |    |    win32kfull.sys!xxxLW_LoadFonts, , 102, 101,694054, , 0,01
20, , ,   |    |    win32kfull.sys!xxxbEnumerateRegistryFonts, , 102, 101,694054, , 0,01
21, , ,   |    |    win32kfull.sys!xxxbEnumerateRegistryFontsInternal, , 102, 101,694054, , 0,01
22, , ,   |    |    |- win32kfull.sys!xxxAddFontResourceW, , 96, 95,668687, , 0,01
23, , ,   |    |    |    win32kfull.sys!xxxClientAddFontResourceW, , 96, 95,668687, , 0,01

The latest trace shows that you still have other fonts installed (Marketing Script Inline, Marketing Script, Microsoft JhengHei, CordiaUC, Teamviewer, Rage Italic, La Bambda, Quixley, Pump Demi).

So remove really all 3rd party fonts.

// Edit 2016-08-24

The second trace shows a long delay in Boot-SessionInit/SMSSInit-Phase:

enter image description here

The SMSSInit subphase begins when the kernel passes control to the session manager process (Smss.exe). During this subphase, the system initializes the registry, loads and starts the devices and drivers that are not marked BOOT_START, and starts the subsystem processes. SMSSInit ends when control is passed to Winlogon.exe.

I looked at the delay and see that the Init/enum of Serial devices (COM port connected devices) is slow:

enter image description here

If you don't need COM port, disable the COM port in BIOS/UEFI.

  • I checked my fonts and while there were many (635) there were no encrypted fonts. I selected all of them and did a delete (i have a backup) and all except 86 uninstalled. I rebooted and basically same boot time. – Andywt Jul 20 '16 at 16:44
  • An interesting anecdote. I ran msconfig and chose diagnostic startup. Boot was the same if not a bit longer. – Andywt Jul 21 '16 at 4:20
  • create a new boot trace: xbootmgr -trace boot -traceFlags BASE+LATENCY+DISPATCHER -stackwalk profile+CSwitch+ReadyThread -resultPath C:\TEMP this captures delay/wait info. Maybe I see why the boot is hanging creating the terminal – magicandre1981 Jul 21 '16 at 5:12
  • The link to the new etl file is dropbox.com/s/51zzf22odmhg4wu/… – Andywt Jul 21 '16 at 20:43
  • update the logitech camera driver and disable malwarebytes. In the trace I see that you use a Seagate Baracuda and no SSD. – magicandre1981 Jul 22 '16 at 15:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.