Windows 10: Disable Prefetch & Superfetch

Howdy,
I've written a code in a batch file to disable Superfetch service and some other things.
But the Superfetch part does not work?
Code: SC Config Superfetch Start= Disabled SC Stop Superfetch[/quote] Output >> The specified service does not exist as an installed service.
Please advise *Sad

:)

 

Cannot delete .mkd file in prefetch

The PfPre_******.mkd files are system files used by prefetch/SuperFetch.

While SuperFetch and prefetch can be stopped/disabled, this is only recommended in some cases when a solid state drive is used.

The best general recommendation is just to leave these files and the entire prefetch folder alone.

 

Windows 10 - Memory usage problem

Since I have been diasabling Superfetch System has used under 10 MB.

How to Disable Superfetch

 

Have you tried running it as administrator?

 

Hi there.

I'm not sure why you would ever want to disable pre-fetch in an OS.

Pre-fetch can considerably improve performance even with SSD's. What the pre-fetch does is use a complex algorithm built on your usage of the OS -- so even when stuff isn't loaded into storage (RAM) it will have an idea of what commands / applications you are likely to use and will when the OS isn't busy load those into RAM ready for you when you run the application.

When you first install the OS it takes a while to build up the database -- that's often why a system "performs better" after a few boots and hours / days of use.

SuperFetch is another thing entirely -- you could disable that if it relies on using a USB stick / other alternate storage to "boost RAM" and I'm not even sure if it exists in W10 any more.

Cheers
jimbo

 

I'm not a newbie, of course I have reason to disable that!
I have SanDisk Extreme Pro SSD and it's recommended to disable those 2 features in systems with SSD.
Somewhere pointed that Windows automatically turn it off if you're using SSD, but mine didn't.
So, I asked why my code returns an error, didn't ask about the function of those features!
Thanks though!

 

You used the wrong name, you should use the service name, not display name. Like this:

sc config SysMain start= disabled

Additionally you can use (just to be sure):

reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters" /v "EnablePrefetcher" /t REG_DWORD /d 0 /f
reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters" /v "EnableSuperfetch" /t REG_DWORD /d 0 /f

 

Most services have 2 names, a "Service Name" which is the official name of the service and a more descriptive "Display Name". The Service Name of the service that controls prefetch and superfetch is "SysMain" while it's display name is "Superfetch". Service manager shows the Display Name and you can see the Service Name in the services properties. The sc command expects the Service Name.

Having 2 names for a service sometimes causes confusion.

 

Hi there
Pre-fetch loads into RAM so I don't see why an SSD would have ANY problem with it -- note again I'm talking about PRE-FETCH not SUPER-FETCH which as I pointed out before is another issue entirely.

So as PRE-FETCH is essentially an HDD / or an SSD READ operation what's the problem with it. !!!

BTW some of the technical stuff you see on manufacturers sites isn't always accurate when it comes to describing the inner workings of an OS.


Cheers
jimbo

 

Thanks all, useful info indeed *Smile

 

Superfetch and Prefetch need to stay enabled. Disabling them, does not improve performance, same as you are asking how to disable System Restore in your other thread.

Leave those items alone. You will actually cause more problems.

 

+1
On Win10 it needs those services on to function correctly. If your system disk is an SSD they will work accordingly. But for things like OneDrive or a 2nd non SSD drive it's still useful, also some software looks for and use them. Just let Windows take care of Windows, it was created with SSDs in mind.

 

There's no reason to "baby" modern SSDs. Most of those recommendations are from few years ago when they were vulnerable to many writes and cell life was short, also were very expensive.

 

Especially that Windows 10 handles Memory and drive management a whole lot better than previous editions.

 

Yes, that too, ever since Windows became SSD aware, methinks it's from W7 Sp1. With XP, it used to be recommended and default virtual memory 2 1/2 times physical RAM !!!