[MagicAndre1981]

ATTENTION: The guide only works if you use HDD (NOT a SSD!).

To get started you need the Windows Performance Tools Kit. Read here how to install it:

http://www.msfn.org/...howtopic=146919

If you are a Windows 7 User:
Make sure that EnablePrefetcher and EnableSuperfetch registry settings are set to 3 and that the Superfetch service (sysmain) is running and set to start automatically.

Also install those Windows 7 hotfixes:
http://www.msfn.org/...howtopic=152622

If you are a Windows Vista User:
Make sure that EnablePrefetcher and EnableSuperfetch registry settings are set to 3 and the ReadyBoost service and that the Superfetch service (sysmain) are both running and set to start automatically.

Now open a command prompt with admin rights ( http://windows.micro...or-access-token ) and run the following command:

xbootmgr -trace boot -prepSystem -verboseReadyBoot

Now your PC will be restarted 6 times. After the second reboot the MS defragmentation program is running and is placing the files into an optimized layout, so that Windows will boot up faster (for the description read what ReadyBoot is). The last Reboots are training of readyBoot. After the training is finished, you'll notice a huge improvement in startup.

Note! DON'T USE OTHER DEFRAGMENTATION PROGRAMS AFTER THE OPTIMIZATION, USE ONLY THE INCLUDED MS TOOL, BECAUSE EVERY TOOL PLACES THE FILES AT A DIFFERENT OFFSET ON YOUR HDD, BECAUSE ALL TOOL THINK THEY KNOW IT BETTER!

Background:

With Windows XP, MS implemented a prefetcher which loads data into the RAM, when the CPU was busy, starting services, drivers, so that they are already loaded when they are needed in later stages of the boot process.

With Vista, MS improved this prefetcher and named it ReadyBoot:

Quote

Windows Vista uses the same boot-time prefetching as Windows XP did if the system has less than 512MB of memory, but if the system has 700MB or more of RAM, it uses an in-RAM cache to optimize the boot process. The size of the cache depends on the total RAM available, but is large enough to create a reasonable cache and yet allow the system the memory it needs to boot smoothly.
After every boot, the ReadyBoost service (the same service that implements the ReadyBoost feature just described) uses idle CPU time to calculate a boot-time caching plan for the next boot. It analyzes file trace information from the five previous boots and identifies which files were accessed and where they are located on disk. It stores the processed traces in %SystemRoot%\Prefetch\Readyboot as .fx files and saves the caching plan under HKLM\System\CurrentControlSet\Services\Ecache\Parameters in REG_BINARY values named for internal disk volumes they refer to.
The cache is implemented by the same device driver that implements ReadyBoost caching (Ecache.sys), but the cache's population is guided by the ReadyBoost service as the system boots. While the boot cache is compressed like the ReadyBoost cache, another difference between ReadyBoost and ReadyBoot cache management is that while in ReadyBoot mode, other than the ReadyBoost service's updates, the cache doesn't change to reflect data that's read or written during the boot. The ReadyBoost service deletes the cache 90 seconds after the start of the boot, or if other memory demands warrant it, and records the cache's statistics in HKLM\System\CurrentControlSet\Services\Ecache\Parameters\ReadyBootStats, as shown in Figure 2. Microsoft performance tests show that ReadyBoot provides performance improvements of about 20 percent over the legacy Windows XP prefetcher.

Source:
http://technet.microsoft.com/en-us/magazin...el.aspx?pr=blog


If you remember XP days, their was a tool called BootVis. The optimization is similar to this here, but the difference is, that is only starts the integrated MS defragmentation program for a better HDD layout, because XP doesn't have ReadyBoot.

To see the improvement in time, run those 2 commands:

xperf -i bootPrep_BASE+CSWITCH_1.etl -o 01_summary_start.xml -a boot
xperf -i boot_BASE+CSWITCH_1.etl -o 02_summary_end.xml -a boot

To determine the boot time, open the XML files and look at the value bootDoneViaPostBoot. This value (-10000 = 10seconds) shows you the time, which Windows needs to boot completely.

In the file 02_summary_end.xml it should be much lower.


I hope this small tutorial helps you to make your Windows start faster.

This post has been edited by MagicAndre1981: 25 July 2011 - 10:07 AM

[Felipe]

Quote

After the training is finished, you'll notice a huge improvement in startup.

How much of an improvement are we looking at ?

[MagicAndre1981]

for me it improves the startup from 60s to 35s. And this is a lot.

[Felipe]

It is. Worth a shot, thanks !

[MagicAndre1981]

ok, please post your results.

[Felipe]

For those who'd like to try it as well, I've put them here : http://www.filedropp...formancetoolkit for easy access.

[Felipe]

Startup went from 42s to 30s. Until now, that seems to be the fastest it can go.

It did crash however when it ran an additional step after the 6. Something about the user, I haven't taken the time to look at it, wierd, because I'm an admin on my pc.

I'll give it another run when I have more spare time.

[MagicAndre1981]

42s to 30 is also ok. You could make a trace and look for drivers or services which cause a slow start.

[cloferba]

any way to do only one or 2 reboots?

not 6 :s

i want to slipstream this function to my unattended windows 7

[MagicAndre1981]

no, more reboots are better. After the optimal placement of the files on your HDD, the prefetcher must learn to load them in optimal order. This takes several reboots.

[tbusters]

I gave i a try but found a strange error:

xbootmgr is an unknown format /file or assignment

and how do i know if my ready boost is running ( windows 7 ) enableprefetch was (3) so is running i gues

[MagicAndre1981]

which CPU architecture does your Windows have? Did you install the correct msi?

[tbusters]

x64

I got the msi from x64 not the 32 and not the special for the processor i dont have

[MagicAndre1981]

Could you please post a screenshot of the error message?

[tbusters]

ok now i get a different error (strange)

The message is btw in dutch
und ich glaube das sie das nicht lesen konnen (bad german)

it now says >"-boot"is unrecognised <

try some other commands

ps is there a way to post pics on this forum without uploading them to a strange server?

[MagicAndre1981]

upload the pictures in the attachment and insert them into the post.

remove the "-" before boot.

[tbusters]

ok this is really stupid

in total i have gotten 2 different error messages

the third time was the lucky time it just worked and i havent changed the code or anything els

so people it does work and i appreciate the help i got from U

thank you very much.

still one question stand: why is this not normaly integrated in windows and why hasnt anyone made a easy tool for it so every body can use it?

[MagicAndre1981]

normally Windows should learn it on every Reboot. But with this method you can speed up the "learning" of ReadyBoot.

Which error message do you get? You are the first person, who is unable to run it.

This post has been edited by MagicAndre1981: 29 December 2009 - 04:02 AM

[PC_LOAD_LETTER]

i just got around to running this on a machine.

i tried my laptop since its the machine i reboot the most.
Windows 7 Ent Dell d830 c2d@2G 2Gb ram

i tried 3 test boots before installing the sdk (timed as a cold start from power button to C+A+D to login)

1 min 45 seconds
3 min 10 seconds
1 min 55 seconds

after the 6 reboots (and 6 logins and answering 6 UAC prompts between boots) i get:

1 min 21 seconds
1 min 20 seconds
1 min 25 seconds
1 min 21 seconds
1 min 22 seconds

not a major increase but if nothing else its more consistent (wish i woulda taken a few more "before" times)

[MagicAndre1981]

30s improvement is ok. If you can upload the latest etl (compressed as 7z or RAR) I can take a look at it and tell you what may causes delays and what can be improved.