Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to diagnose the problems I've been having with boot-up on my machine. The system drive is an SSD, so it should be fairly quick. However there is one moment, right after the "Welcome" wheel where I get the mouse and a black screen for a very long time.

Now you can find the boot logs here: (BootCKCL.etl file, opens with windows performance toolkit)

I did several boot-ups and the results are always the same. In this particular one at about the 0:36 sec mark you'll notice this wide gap where nothing happens for about a minute.

It also doesn't seem to be related to any of the processes prior to the gap(tried to disable those). I have no idea what the bottleneck is and don't even know where to start.

P.S. I also tried the suggestion from one of the other threads here. There was a suggestion to run

xperf -start perf!GeneralProfiles.InBuffer && timeout -1 && xperf -stop perf!GeneralProfiles.InBuffer myTrace.etl

But that gave me an error message:

xperf: error: Failed to start profile: Cannot create a file when that file already exists. (0x800700b7).

Which I couldn't figure out how to fix.

share|improve this question
So you gain no performance increase if you disabled ALL startup applications? – Ramhound May 12 '13 at 9:43
I disabled the last three there. There's lots of them. Its unfeasible to try to disable all of those. The problem is how do I narrow it down and how do I find out where the bottleneck is. – martixy May 12 '13 at 11:54
So, does a file with the name of myTrace.etl already exist, as the error message indicates? – Oliver Salzburg May 12 '13 at 13:32
I created a new post you might find helpful… I'm still working on it though – Oliver Salzburg May 12 '13 at 14:22
the errormessage 0x800700b7 shows up if you already run a tool which uses ETW (ProcessExplorer for example). But xperf is the wrong tool. Use xbootmgr. – magicandre1981 May 12 '13 at 15:04
up vote 3 down vote accepted

Your boot is slow because of a long WinLogonInit phase:

enter image description here

When looking into the Generic Events of the WinLogonInit phase I saw that reconnecting the network drives takes most time:

enter image description here

So disable the network drives and reconnect them via

net use <driveletter>: \\Server\Share /persistent:no

on demand when you really need the network drives.

share|improve this answer
WOW... That actually worked brilliantly! Thank you so much. And at the same time somehow I'm not surprised that this exactly is the culprit. – martixy May 14 '13 at 16:01
You're welcome. enjoy your fast booting Win7. – magicandre1981 May 14 '13 at 17:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .