Hey Andre what is the exact trace command I should run to have a weird boot issue for you to possibly look at? Cold boots are > 10 min, every warm boot results in a readyboot plan and < 2 min starts with cache hitting yet only one trace ever is kept and following files never flush from this system after rolled into single current trace1.fx:

ecboot.avail

etlboot_1.dqpa

etlboot_1.dqpaf

ecboot.dqpafm

ecboot.dqpafmsg

ReadyBoot.etl.old

Trace1.fx

I can sit and refresh and watch each of the above files fill and grow in first 2 min after boot, the trace1.fx created and then nothing - no flushing of these other files and unlike EVERY other system, NEVER a 2nd trace not matter how many reboots.

For the life of me, I cant get a trace to troubleshoot must not be running right command and need help and cant ever get a cold boot using readyboot plan.

Thanks!

those are internal files of the Prefetcher.

I have no idea how to trace your cold boot issue.

But this is the only WIN7 system I can find that doesn't flush them and create more than 1 trace. As far as the cold boot I guess what i'm asking is what xperf command line is best to grab a capture that maybe you could look at to tell me what's taking the most time and most disk io, etc on a cold boot?

Thanks!

I'm getting the same error, "Gave up waiting for Win7RTM physical prefetcher after 300 seconds. Could not wait for prefetcher" and layout has disapeared after first boot. How do i fix this please.

have you disabled the Superfetch service?

No, set to auto.

is the service running?

upload the complete xbootmgr.log

xbootmgr.zip yes

Edited February 19, 201412 yr by greyeyezz

Install the Enterprise Hotfix Rollup which includes ReadyBoot fixes:

http://support.microsoft.com/kb/2775511/en-us

Alright I got the 2 hotfixes, I am imaging my drive first, God knows what havoc these can wreak.

Ran the hotfixes, now system boots even slower. Tried to run boot trace, same error. Superfetch is running.

I have no other idea.

Alright Andre I tried everything to get that multi boot optimization to run again and nothing worked, so I ran the other trace for the .etl file

I would much appreciate if you took a look, here it is, thank you.

https://onedrive.live.com/redir?resid=2D34C3442773337A%21124

your slow HDD is the cause and busiy for over 70s:

Thanks.