<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Disable SuperFetch on Windows Vista</title>
	<atom:link href="http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/</link>
	<description>Computer Help from your Friendly How-To Geek</description>
	<lastBuildDate>Sun, 08 Nov 2009 07:56:33 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Timovone</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-77750</link>
		<dc:creator>Timovone</dc:creator>
		<pubDate>Mon, 12 Oct 2009 20:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-77750</guid>
		<description>DISABLE! YES FINALLY!, THIS THING WAS REALLY ANNOYING. now everything is smooth and quite.</description>
		<content:encoded><![CDATA[<p>DISABLE! YES FINALLY!, THIS THING WAS REALLY ANNOYING. now everything is smooth and quite.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-77233</link>
		<dc:creator>Geoff</dc:creator>
		<pubDate>Tue, 29 Sep 2009 16:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-77233</guid>
		<description>WOW! great tip. Photoshop CS4 was lagging sooo bad for the longest time , and i disabled super-fetch and OMG, what a difference!1 Thanks a lot! :)</description>
		<content:encoded><![CDATA[<p>WOW! great tip. Photoshop CS4 was lagging sooo bad for the longest time , and i disabled super-fetch and OMG, what a difference!1 Thanks a lot! <img src='http://www.howtogeek.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarevok</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-76590</link>
		<dc:creator>Sarevok</dc:creator>
		<pubDate>Sun, 13 Sep 2009 07:03:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-76590</guid>
		<description>how I physically destroyed HDD:
I bought new mainstream PC 8400,4GB,4850,500GB WD HDD. Installed WV x64 Ultimate. I noticed extreme HDD activity next day, thinking it is normal for new vista to create everything needed... after next 10 days of endless 100% disk activity I started to figure out whats wrong. In reliability and performance monitor I found Localsystemnetworkrestricted is reading 100MB/s my ISO image of one DVD I had on HDD. OMG, it was reading it all the time. It could copy it for 1000000 times for that time. Next day Vista failed to boot. When trying to reinstal, failed to di it. Disk went back to store. They did not change, just did low level format and returned it to me. After installation superfetch was doing the same with iso image, I found on internet it is superfetch and disable it, but it was too late for HDD which failed that day totally. I bought another hard drive and again it is doing the same. This time i disabled superfetch right when it start to read iso image for 20 minutes... I think Microsoft should be charged for these things...</description>
		<content:encoded><![CDATA[<p>how I physically destroyed HDD:<br />
I bought new mainstream PC 8400,4GB,4850,500GB WD HDD. Installed WV x64 Ultimate. I noticed extreme HDD activity next day, thinking it is normal for new vista to create everything needed&#8230; after next 10 days of endless 100% disk activity I started to figure out whats wrong. In reliability and performance monitor I found Localsystemnetworkrestricted is reading 100MB/s my ISO image of one DVD I had on HDD. OMG, it was reading it all the time. It could copy it for 1000000 times for that time. Next day Vista failed to boot. When trying to reinstal, failed to di it. Disk went back to store. They did not change, just did low level format and returned it to me. After installation superfetch was doing the same with iso image, I found on internet it is superfetch and disable it, but it was too late for HDD which failed that day totally. I bought another hard drive and again it is doing the same. This time i disabled superfetch right when it start to read iso image for 20 minutes&#8230; I think Microsoft should be charged for these things&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sad_Tale</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-75900</link>
		<dc:creator>Sad_Tale</dc:creator>
		<pubDate>Fri, 28 Aug 2009 02:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-75900</guid>
		<description>My problems started about 1.5 years after I purchased a Fujitsu N6460 laptop that came with Vista Home and 2gig of RAM. I purchased the full retail version of Vista Ultimate (not an upgrade version) that was pre-SP1. Ultimate did an &quot;upgrade&quot; install without any issues, and an upgrade to SP1 without any issues. I then upgraded to 4gig of RAM. The hardware detected the 4gig of RAM, but 32bit Ultimate could only &quot;see&quot; about 3.5gig of it (because 32 bits can not address a 4gig address) so I used the last .5gig of the 4gig RAM as a Ramdrive mapped as Drive D. The mapping for the Ramdrive is performed BEFORE Ultimate starts booting, so all that is physically available to Ultimate as normal RAM is just 3.5gig, which it can use in total. Additionally, Ultimate &quot;sees&quot; the .5gig Ramdrive as Drive D and can use it without error.

One day I discovered that attempts to actually perform a System Restore from a previously and successfully saved Restore Point would not work from within a normal boot of Ultimate. Worse, attempting to boot into safe mode to perform the restore would blue screen with a 0x0000000A error related somehow to a Fujitsu specific driver. The same thing would happen if I tried to restore using the Ultimate CD to boot from! At this point I had been experiencing a lot of HD &quot;thrashing&quot; for several months, but system performance had not seemed to be affected. Due to inability to restore without getting blue screen, I contacted Microsoft and had to pay them for a fix. They took my money but did not provide a fix. This for MS software that I had purchased less than 2 years before writing this forum comment! After they took my money I discovered that the reason for the blue screen, and inability to do a restore by any means whatsoever, was because I had 4gigs of RAM instead of 3gigs. Downgrading to 3gigs made the blue screens go away.

But before I discovered that fact, MS had me uninstall SP1. I was able to boot in normal mode but still could not restore, and I didn&#039;t yet know that trying to boot in Safe Mode or from the CD would cause a blue screen. So then MS had me start a &quot;repair&quot; reinstall, with SP1 having been removed (as my CD did not come with SP1). It didn&#039;t work and I experienced the 1st blue screen of type mentioned above (because the Ramdrive wasn&#039;t reducing the 4gigs to 3.5gigs). I used MSConfig to remove the attempts at boot to continue the failed &quot;repair&quot; reinstall of Ultimate, and was able to then boot normally to the desktop.

The first boot was fast and the MS tech decide the case was closed (!) and I got charged but now had a system that still would not restore and I then discovered that doing just about anything would cause the HD to start going into continuous activity, and trying to launch anything at all would take several minutes! The error logs were filling up with messages about random programs degrading system performance. Turns out they were not the cause.

I discovered the cause for the blue screens in Safe Mode (via Google!) and reduced my memory to 3gigs, the blue screens went away and I restored via CD to a time when all was ok (about a week ago), as I still could not successfully restore from within a normal boot. This did not fix the HD thrashing and immediate near total system freeze when the thrashing would begin!

But the articles here about Superfetch fixed the issue! No more disk thrashing, no more system freezing! Boot time back to about 4 minutes with HD sitting inactive, way down from the near 1/2 hour it was taking previously! I did use the registry settings of &quot;1&quot; for both Superfetch and Prefetch as mentioned earlier in this forum, as a setting of &quot;2&quot; would boot in an acceptable time but it would boot a little faster when both were set to &quot;1&quot;, and I didn&#039;t see that programs were launching faster with the &quot;2&quot; setting.

I&#039;ve turned back on Windows Search, since it&#039;s smart enough to pause itself if the system is not idle (Superfetch seems to lack that at any setting, slowing the system way down when it is busy). Windows Search was NOT the cause of having an unusable desktop and lots of performance error messages in Event Viewer. Superfetch was the cause, nothing else.

Upgrading to Ultimate SP2 did not fix the Superfetch issue, so I have it on but with the mentioned registry settings of &quot;1&quot;. The system runs fast and nice, and World of Warcraft performance is also noticeably improved. If Superfetch worked properly then I&#039;d agree that it should be used. But like MS charging me to unsuccessfully fix a Vista Ultimate *system* related issue, they have it wrong when it comes to their default configuration of Superfetch. Maybe it&#039;s a way for them to get money on service calls? I am, of course, angry that I was charged for something I had to fix after they closed my case SRX1109606110ID. I think I&#039;ll stick with Vista Ultimate and XP Pro, and never buy another product from MS again. I&#039;ve had Win3.1, 95, 98, 98SE, ME, 2K, XP, and Vista. I&#039;m tired of the problems when each was supposed to be so much better than the previous, and I&#039;ll never be forgiving that I was charged for a faulty design issue caused by software that goes bonkers with a system motherboard that itself can recognize 4gigs of memory. That&#039;s just poor design, and I&#039;m tired of that history! I&#039;ll keep what I have, but no Win7 etc. with the continuing issues with security and system performance that 8 different versions have exhibited and now they want to charge for when the operating system malfunctions. No, no more money from me. MS did *not* help nor resolve my issue for the money, they made it worse but Google and this forum supplied the needed technical knowledge to resolve the issues. Thanks to all in this forum, you&#039;re an experienced and honorable group of people!</description>
		<content:encoded><![CDATA[<p>My problems started about 1.5 years after I purchased a Fujitsu N6460 laptop that came with Vista Home and 2gig of RAM. I purchased the full retail version of Vista Ultimate (not an upgrade version) that was pre-SP1. Ultimate did an &#8220;upgrade&#8221; install without any issues, and an upgrade to SP1 without any issues. I then upgraded to 4gig of RAM. The hardware detected the 4gig of RAM, but 32bit Ultimate could only &#8220;see&#8221; about 3.5gig of it (because 32 bits can not address a 4gig address) so I used the last .5gig of the 4gig RAM as a Ramdrive mapped as Drive D. The mapping for the Ramdrive is performed BEFORE Ultimate starts booting, so all that is physically available to Ultimate as normal RAM is just 3.5gig, which it can use in total. Additionally, Ultimate &#8220;sees&#8221; the .5gig Ramdrive as Drive D and can use it without error.</p>
<p>One day I discovered that attempts to actually perform a System Restore from a previously and successfully saved Restore Point would not work from within a normal boot of Ultimate. Worse, attempting to boot into safe mode to perform the restore would blue screen with a 0&#215;0000000A error related somehow to a Fujitsu specific driver. The same thing would happen if I tried to restore using the Ultimate CD to boot from! At this point I had been experiencing a lot of HD &#8220;thrashing&#8221; for several months, but system performance had not seemed to be affected. Due to inability to restore without getting blue screen, I contacted Microsoft and had to pay them for a fix. They took my money but did not provide a fix. This for MS software that I had purchased less than 2 years before writing this forum comment! After they took my money I discovered that the reason for the blue screen, and inability to do a restore by any means whatsoever, was because I had 4gigs of RAM instead of 3gigs. Downgrading to 3gigs made the blue screens go away.</p>
<p>But before I discovered that fact, MS had me uninstall SP1. I was able to boot in normal mode but still could not restore, and I didn&#8217;t yet know that trying to boot in Safe Mode or from the CD would cause a blue screen. So then MS had me start a &#8220;repair&#8221; reinstall, with SP1 having been removed (as my CD did not come with SP1). It didn&#8217;t work and I experienced the 1st blue screen of type mentioned above (because the Ramdrive wasn&#8217;t reducing the 4gigs to 3.5gigs). I used MSConfig to remove the attempts at boot to continue the failed &#8220;repair&#8221; reinstall of Ultimate, and was able to then boot normally to the desktop.</p>
<p>The first boot was fast and the MS tech decide the case was closed (!) and I got charged but now had a system that still would not restore and I then discovered that doing just about anything would cause the HD to start going into continuous activity, and trying to launch anything at all would take several minutes! The error logs were filling up with messages about random programs degrading system performance. Turns out they were not the cause.</p>
<p>I discovered the cause for the blue screens in Safe Mode (via Google!) and reduced my memory to 3gigs, the blue screens went away and I restored via CD to a time when all was ok (about a week ago), as I still could not successfully restore from within a normal boot. This did not fix the HD thrashing and immediate near total system freeze when the thrashing would begin!</p>
<p>But the articles here about Superfetch fixed the issue! No more disk thrashing, no more system freezing! Boot time back to about 4 minutes with HD sitting inactive, way down from the near 1/2 hour it was taking previously! I did use the registry settings of &#8220;1&#8243; for both Superfetch and Prefetch as mentioned earlier in this forum, as a setting of &#8220;2&#8243; would boot in an acceptable time but it would boot a little faster when both were set to &#8220;1&#8243;, and I didn&#8217;t see that programs were launching faster with the &#8220;2&#8243; setting.</p>
<p>I&#8217;ve turned back on Windows Search, since it&#8217;s smart enough to pause itself if the system is not idle (Superfetch seems to lack that at any setting, slowing the system way down when it is busy). Windows Search was NOT the cause of having an unusable desktop and lots of performance error messages in Event Viewer. Superfetch was the cause, nothing else.</p>
<p>Upgrading to Ultimate SP2 did not fix the Superfetch issue, so I have it on but with the mentioned registry settings of &#8220;1&#8243;. The system runs fast and nice, and World of Warcraft performance is also noticeably improved. If Superfetch worked properly then I&#8217;d agree that it should be used. But like MS charging me to unsuccessfully fix a Vista Ultimate *system* related issue, they have it wrong when it comes to their default configuration of Superfetch. Maybe it&#8217;s a way for them to get money on service calls? I am, of course, angry that I was charged for something I had to fix after they closed my case SRX1109606110ID. I think I&#8217;ll stick with Vista Ultimate and XP Pro, and never buy another product from MS again. I&#8217;ve had Win3.1, 95, 98, 98SE, ME, 2K, XP, and Vista. I&#8217;m tired of the problems when each was supposed to be so much better than the previous, and I&#8217;ll never be forgiving that I was charged for a faulty design issue caused by software that goes bonkers with a system motherboard that itself can recognize 4gigs of memory. That&#8217;s just poor design, and I&#8217;m tired of that history! I&#8217;ll keep what I have, but no Win7 etc. with the continuing issues with security and system performance that 8 different versions have exhibited and now they want to charge for when the operating system malfunctions. No, no more money from me. MS did *not* help nor resolve my issue for the money, they made it worse but Google and this forum supplied the needed technical knowledge to resolve the issues. Thanks to all in this forum, you&#8217;re an experienced and honorable group of people!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spackie</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-75466</link>
		<dc:creator>Spackie</dc:creator>
		<pubDate>Tue, 18 Aug 2009 01:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-75466</guid>
		<description>According to the &quot;experts&quot; over at http://www.sevenforums.com/  if you disable SF you are a troll, an idiot, are spreading FUD because modern Operating Systems operate on a &quot;unused RAM is wasted RAM&quot;. One fellow even stated &quot;I want every bit of my RAM full so its gets used&quot;. Well thats great buddy, but my foreground application are alway so slow due to execessive memory contention between apps in the cache apps in the foreground.</description>
		<content:encoded><![CDATA[<p>According to the &#8220;experts&#8221; over at <a href="http://www.sevenforums.com/" rel="nofollow">http://www.sevenforums.com/</a>  if you disable SF you are a troll, an idiot, are spreading FUD because modern Operating Systems operate on a &#8220;unused RAM is wasted RAM&#8221;. One fellow even stated &#8220;I want every bit of my RAM full so its gets used&#8221;. Well thats great buddy, but my foreground application are alway so slow due to execessive memory contention between apps in the cache apps in the foreground.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-75271</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Thu, 13 Aug 2009 01:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-75271</guid>
		<description>This may be why my friend thinks he has to have 8 gigs of ram on his system to play games.  He knows almost nothing about computers and when he started with 4 gigs of RAM on his desktop it was always filling up before he even started his games.  He went out and spent TONS of money on a desktop with a huge CPU and 8 gigs of ram.  Even then His ram seemed to fill up almost full upon boot-up.  One simple tweak and he&#039;ll probably trip over his own jaw.  Thanks for answering my question!</description>
		<content:encoded><![CDATA[<p>This may be why my friend thinks he has to have 8 gigs of ram on his system to play games.  He knows almost nothing about computers and when he started with 4 gigs of RAM on his desktop it was always filling up before he even started his games.  He went out and spent TONS of money on a desktop with a huge CPU and 8 gigs of ram.  Even then His ram seemed to fill up almost full upon boot-up.  One simple tweak and he&#8217;ll probably trip over his own jaw.  Thanks for answering my question!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HPMC</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-75213</link>
		<dc:creator>HPMC</dc:creator>
		<pubDate>Tue, 11 Aug 2009 14:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-75213</guid>
		<description>Fantastic! Superfetch is an absolute aberration. After using Vista for a few months, I sincerely believe that SF was causing it to run more slowly. I was ready to put a piece of tape over the HD LED.

Disabled Superfetch. Quiet hard drive, faster PC, SHORTER load times, better performance. Thanks to you all for the original post, as well as your comments.</description>
		<content:encoded><![CDATA[<p>Fantastic! Superfetch is an absolute aberration. After using Vista for a few months, I sincerely believe that SF was causing it to run more slowly. I was ready to put a piece of tape over the HD LED.</p>
<p>Disabled Superfetch. Quiet hard drive, faster PC, SHORTER load times, better performance. Thanks to you all for the original post, as well as your comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-75024</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Thu, 06 Aug 2009 18:48:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-75024</guid>
		<description>I only have a dual core 3 gig sony with 2 gigs max ram and vista has been a slow freezing beast with long load ups and shut down and such. I was reading about windows 7 new release and saw info on the superfetch. Well quick google got me here and I turned it off and what I notice right away is the laggy freezes and slow to open tabs are all gone its like a different machine quick responses no freezes and a silent drive not to menton much better game play. great find here</description>
		<content:encoded><![CDATA[<p>I only have a dual core 3 gig sony with 2 gigs max ram and vista has been a slow freezing beast with long load ups and shut down and such. I was reading about windows 7 new release and saw info on the superfetch. Well quick google got me here and I turned it off and what I notice right away is the laggy freezes and slow to open tabs are all gone its like a different machine quick responses no freezes and a silent drive not to menton much better game play. great find here</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rookal</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-74815</link>
		<dc:creator>rookal</dc:creator>
		<pubDate>Thu, 30 Jul 2009 23:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-74815</guid>
		<description>I forgot to mention once you make a changes to superfetch through the registry, you need to clean out your Windows/prefetch folder in order to complete the changes.

Once you reboot your machine it will rebuild the superfetch/prefetch folder. THis will make your hard work more than usual on the first reboot but subsequent boots will work with your new setting.</description>
		<content:encoded><![CDATA[<p>I forgot to mention once you make a changes to superfetch through the registry, you need to clean out your Windows/prefetch folder in order to complete the changes.</p>
<p>Once you reboot your machine it will rebuild the superfetch/prefetch folder. THis will make your hard work more than usual on the first reboot but subsequent boots will work with your new setting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rookal</title>
		<link>http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/comment-page-2/#comment-74813</link>
		<dc:creator>rookal</dc:creator>
		<pubDate>Thu, 30 Jul 2009 22:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.howtogeek.com/howto/windows-vista/how-to-disable-superfetch-on-windows-vista/#comment-74813</guid>
		<description>I see mostly everyone here either trashing or loving superfetch, and most are recommending disabling it.

But I can recommend a perfect fix that wiil be good for everyone to use.

Superfetch has options. And the default vista install option is not a very good setting as it can thrash many hard drives, taking up valuable resources and give your poor hard drive a run for it&#039;s money.

But as most are not aware superfetch run in cunjuction with prefetch and disabling it disable the other.

My best suggestion would be to limit Superfetch and remove that annoying Hard drive thrash and free up valuable system resources, without forgoing prefetch which can be a good thing for gamers.

Super fetch and prefetch have 3 settings 

a value of 1: Caches Boot files only.
a value of 2: Caches Boot files and Programfiles 
a value of 3: Caches all files (Default setting when vista is installed, takes maximum resources) 


These settings can be found in the system registry under

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management\PrefetchParameters

there are two keys called enable superfetch and enable prefetch, both having the default values of 3.


Therefore I would suggest:

a setting of 2 for common and advanced users, as this setting will still take a moment to load up on first startup, but will stop thrashing the hard drive after a few moments and give you faster access to the software you use more often. For people with highier end systems there is not hard drive thrashing with this setting.

a setting of 1 for power users and hard core gamers, this setting will allow system resources to be minimully affected, and what this does is it cashes many of the system files in Ram, theoretically increasing performance (and this is the setting that I use with a 4 gig ram system latest cpu...).

a setting of 3 is for people running large databases, presentations and so forth and only if your running your machine for days at a time. if you reboot daily use a setting of 2.


People who need to disable superfetch are those that are running vista with older systems and low ram (under a gig) - if you have an older system and have more than a gig use a setting of 1 and over 2 gigs you might consider using a setting of 2.


I hope this information helps. And clarifies a few things for most about superfetch.

Good Luck everyone</description>
		<content:encoded><![CDATA[<p>I see mostly everyone here either trashing or loving superfetch, and most are recommending disabling it.</p>
<p>But I can recommend a perfect fix that wiil be good for everyone to use.</p>
<p>Superfetch has options. And the default vista install option is not a very good setting as it can thrash many hard drives, taking up valuable resources and give your poor hard drive a run for it&#8217;s money.</p>
<p>But as most are not aware superfetch run in cunjuction with prefetch and disabling it disable the other.</p>
<p>My best suggestion would be to limit Superfetch and remove that annoying Hard drive thrash and free up valuable system resources, without forgoing prefetch which can be a good thing for gamers.</p>
<p>Super fetch and prefetch have 3 settings </p>
<p>a value of 1: Caches Boot files only.<br />
a value of 2: Caches Boot files and Programfiles<br />
a value of 3: Caches all files (Default setting when vista is installed, takes maximum resources) </p>
<p>These settings can be found in the system registry under</p>
<p>HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management\PrefetchParameters</p>
<p>there are two keys called enable superfetch and enable prefetch, both having the default values of 3.</p>
<p>Therefore I would suggest:</p>
<p>a setting of 2 for common and advanced users, as this setting will still take a moment to load up on first startup, but will stop thrashing the hard drive after a few moments and give you faster access to the software you use more often. For people with highier end systems there is not hard drive thrashing with this setting.</p>
<p>a setting of 1 for power users and hard core gamers, this setting will allow system resources to be minimully affected, and what this does is it cashes many of the system files in Ram, theoretically increasing performance (and this is the setting that I use with a 4 gig ram system latest cpu&#8230;).</p>
<p>a setting of 3 is for people running large databases, presentations and so forth and only if your running your machine for days at a time. if you reboot daily use a setting of 2.</p>
<p>People who need to disable superfetch are those that are running vista with older systems and low ram (under a gig) &#8211; if you have an older system and have more than a gig use a setting of 1 and over 2 gigs you might consider using a setting of 2.</p>
<p>I hope this information helps. And clarifies a few things for most about superfetch.</p>
<p>Good Luck everyone</p>
]]></content:encoded>
	</item>
</channel>
</rss>
