Enabling SuperFetch
When you are using Windows Server 2008 as a workstation SuperFetch will give your operating system a little bit more responsive while working on it.
Use Registry Tweak in stead of the first 4 steps
1. To enable the SuperFetch service you will first have to make a little change in the registry. Open the Registry Editor by clicking Run in the Start menu. Next type regedit and click OK. In the Registry Editor browse to the location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters.
2. Right click in the right part of the window and choose DWORD (32bit) Value in the menu New. Type as Name: EnablePrefetcher
3. Edit the value of value EnablePrefetcher by doubleclicking on it. Change the Value data field into ‘3‘ (without quotes)
4. Next create a second DWORD (32bit) Value, name it EnableSuperfetch and also give it as Value data ‘3‘ (without quotes)
5. Close the Registry Editor, then click Run in the menu Start. Type services.msc and click OK. In the Services window, scroll down to the service with name SuperFetch.
6. Right click on the SuperFetch service and choose Properties in the context menu.
7. Next choose in the Startup type dropdown Automatic. Click Apply in the lower right of the Superfetch Properties window. The Start button will now be enabled. Press the Start button to enable SuperFetch for your current session.
8. Final screen. Because we have set the Startup type to Automatic, next time you start Windows Server 2008, the SuperFetch service will run to optimize your systems performance!
Tags Server 2008 Workstation
March 15th, 2008 at 8:39
do you need to add d-word 64bit value instead of 32bit value for x64 systems?
March 18th, 2008 at 23:09
For server 2008 x64 I also used the 32bit value, dont know whats the effect if you use the qword…
Admin: 32bit DWORD should be used in both architectures. In Vista SP1 x64 these are all 32bit values too.
March 27th, 2008 at 1:11
As reghack:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters]
“EnablePrefetcher”=dword:00000003
“EnableSuperfetch”=dword:00000003
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysMain]
“Start”=dword:00000002
May 9th, 2008 at 18:54
What’s the difference between EnableSuperFetch being set to 3 rather than 1?
Admin: See the following options:
1 = Enable SuperFetch for boot files only;
2 = Enable SuperFetch for programs only;
3 = Enable SuperFetch for both boot files and programs.
July 16th, 2008 at 13:02
Many people disable superfetch or in the case of server 08, leave it off.
This is for a number of reasons and everyone should do their own research and come to their own conclusion depending on their particular usage pattern (if they have one).
I wont explain why because there are countless sites and forum threads you can find with a quick google.
The idea of prefetching apps that you’re about to use is great. The problem is the OS predicting which apps they are!
July 16th, 2008 at 19:00
That’s why I prefer option 1
August 14th, 2008 at 19:04
http://www.howtogeek.com/howto/windows-vista/change-superfetch-to-only-cache-system-boot-files-in-vista/
Says that 1 = programs only, 2 = boot files only. I’m inclined to believe him over Kevin, as I’ve had it set for a week or two to 1, and it still superfetches programs (as indicated by watching files accessed in reliability and performance monitor).
August 14th, 2008 at 19:35
Well, exactly the same thing happened with it set to 2. So I’m not sure what to make of it (or if that registry value does anything at all).
October 8th, 2008 at 19:39
Hey Guys how to us Windows ReadyBoost
:! :!