Recommended Posts

After quite a lengthy experimentation process I have discovered what the "Tweak Gurus & PC Geeks" don't tell you in their posts on the subject of cleaning the Prefetch folder.

This guide has not been plagiarized. It is totally compiled by me and was once posted by me at the SoftZone Forums.I decided that I did not wan't to be a member of that comunity because they have more rules than posts so I removed this post and others I had made and canceled my membership.So if you have seen it before that is where it came from.

I hope it can be of assistance to some of you that have cleaned your Prefetch folder because you have been told it will speed XP up. But now "like I did" you find that after you have cleaned the prefetch folder your PC now suffers from slow boot up's and general lack of performance. Here is the real deal about the Prefetch Folder

DO NOT REMOVE OR DELETE THE ->(layout.ini)<- FILE WHICH RESIDES IN XP'S PREFETCH FOLDER OR YOU WILL SLOW DOWN YOUR PC AT START UP AND WHEN YOU OPEN WINDOWS PROGRAMS. Once it is gone it can stay gone on some PC'S (like mine) for ever and your Prefetch Folder will never work again no matter what you do in the registry to try to rectify the problem.

If this has happened to your prefetch folder DON'T WORRY because I will now show you in 5 easy steps how you can rebuild the -> (layout.ini) <- file again.

1): make sure that the task scheduler is enabled.If you are un sure go to-> Start/Contrl Panel/Administrative Tools/ Click on Services/ Then in the list of services make sure the Task Sheduler is enabled & restart the service by clicking on Start. Close the Services Folder & go back to desktop.

2): Then go to START/RUN/ and TYPE IN/->cmd<-(without the arrows) CLICK OK. This will bring up the DOS Command screen.

3):You will need to copy and paste this entry in at the flashing cursor

-> rundll32.exe advapi32.dll,ProcessIdleTasks <-(without the arrows) and press ENTER.

4):Now reboot three times and your Prefetch folder will be rebuilt.(It takes 3 reboots for the prefetch folder to work out what it needs)

5):Then go BACK to ->Start/Contrl Panel/Administrative Tools/ / Services/ Once again find TASK SHEDULER in the list and stop the service and then set it to disabled.This will stop any more entries going into your Prefetch folder.

If you need to leave your task sheduler enabled,(No Drama) you will just have to clean out your Prefetch folder manually from time to time.Just remember not to remove the layout.ini file

You should only clean out files ?other than Windows Start up files? in the Prefetch folder.

If you clean out the standard Windows entries you will CRIPPLE & SLOW DOWN the Windows XP Quick starts and also slow down opening windows processes.

No one bothers to tell you the consequence of deleting the (layout.ini file) in all the tips I have seen about cleaning out the Prefetch folder.

Also if you use one of the many programs that are availabe to clean the prefetch folder you will find that they delete the layout.ini file also.

I have now tried about 50 of these so called Prefetch clean programs and they all disable the Prefetch folder completely and for ever which is a crazy thing to do.The Prefetch is one of the best things about XP.

The truth is that only people who don't know what the Prefetch folder is actually for and don't know how it works say that it is useless.

All I can say is that there must be a lot of people with a verry sluggish XP Windows PC's around,,especially at Boot up.

Edited by adamzapple
Link to comment
https://www.neowin.net/forum/topic/331072-repair-xp-prefetch-folder/
Share on other sites

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management \ PrefetchParameters

dword value = EnablePrefetcher

0 = Disable,

1 = App launch prefetch

2 = Boot Prefetch

3 = Both (recommended)

Task Scheduler is needed for Prefetch to work.

Not sure what the rest is needed for...unless I've just never bumped into that particular problem.

I personally do purge my Prefetch folder every so often, including the Layout.ini file.

If you open the Layout.ini file and scroll through it, chances are you're going to see a lot of things that are long gone on your system, including file and folder paths. The Layout.ini file is pointing to those things upon boot.

Ever disable a Service and have DCOM errors spring up all over the place in the Event Viewer? Sometimes, (not always), the errors are coming from the Layout.ini file pointing to that disabled Service.

The Layout.ini file will usually rebuild itself after a couple of reboots and in about 20 minutes of idle time. (Pre SP2, the Layout.ini file would rebilut itself in exactly 13 minutes...a little Pre SP2 trivia...lol )

Thats not 100% correct Iron200,, delete everything in your prefetch folder including the layout.ini file and see what happens. It will not always come back as you say.Once the layout ini file is deleted it has to be rebuilt manually using the comand prompt in DOS.

Bold fortune that Registry tweak you have posted only works when you have still got a working Prefetch folder.If you delete the Layout.ini file and clean out the Prefetch folder that tweak does nothing and it won't just magically rebuild itself once the Prefetch folder has been stripped bare.

Yes you are correct on the fact that you must have the Task Shedular enabled to use bootvis.

Whenever I've gone to clear out the Prefetch folder, I've done a "Ctrl+A", "Shift+Del". Unless the prefetcher is disabled or the Scheduled Tasks service is disabled, the files have always come back on all the computers I'd done this on (several times...).

The Prefetch folder will rebuild itself when it is empty. If it isn't working, then you've got a bigger problem than what's been outlined here. How do you think that the system keeps track of files that it should prefetch? It keeps adding to the list (but not removing...) with the new programs that are run.

If it isn't working, then you've got a bigger problem than what's been outlined here

That is what I have just shown you how to do: REPAIR IT WHEN IT'S NOT WORKING.I wish you people would read the original post.

All I said was if you clean out your prefetch folder not to clean out your Standard Windows Startup files and to leave the layout.ini file in the folder.Do not delete these files or you will slow down your PC especially when windows XP boots up.

If you do delete these files and you find Like I did and hundreds of other XP users that your PC runs slow because the Prefetch folder now doesn't work and that it stays empty no matter how much Registery tweaking you do.I have shown you how to rebuild the layout.ini file and the process involved in repairing the Prefetch folderit so it will work properlyagain OK.Nothing more.

To all the other users that have a PC with an automatic prefetch repair,,Good luck to you and I wish I had one too.

That is what I have just shown you how to do: REPAIR IT WHEN IT'S NOT WORKING.I wish you people would read the original post.

All I said was if you clean out your prefetch folder not to clean out your Standard Windows Startup files and to leave the layout.ini file in the folder.Do not delete these files or you will slow down your PC especially when windows XP  boots up.

If you do delete these files and you find Like I did and hundreds of other XP users  that your PC runs slow because the Prefetch folder now doesn't work and that it stays empty no matter how much Registery tweaking you do.I have shown you how to rebuild the layout.ini file and the process involved in repairing the Prefetch folderit so it will work properlyagain OK.Nothing more.

To all the other users that have a PC with an automatic prefetch repair,,Good luck to you and I wish I had one too.

586061299[/snapback]

No need to get hasty here... we're just trying to put our input here as well.

Your method does work for the situation where something has gone buggered and the Prefetch system isn't working, but if that's the case, then there's most likely an underlying problem. The Prefetcher shouldn't stop working because the folder is empty.

All I'm saying is that I've never run into troubles with the prefetch folder from deleting its entire contents. All the files that are needed, including layout.ini are recreated. Yes, I will say that after you delete the contents of the Prefetch folder, the system will take a bit longer to boot for the next few boots, but that's because (as you yourself said) it takes three full reboots for Windows to track all the files needed on startup.

Thats not 100% correct Iron200,, delete everything in your prefetch folder including the layout.ini file and see what happens. It will not always come back as you say.Once the layout ini file is deleted it has to be rebuilt manually using the comand prompt in DOS.

586052755[/snapback]

actually, i've deleted everything (including the layout.ini file) and they were all re-created.

of course, this is a useful tweak for people with messed up prefetching.

I just found this with a Google Search. (I should have bookmarked where...darnit.)...

After deleting files out of the prefetch directory you should run the command

Rundll32.exe advapi32.dll,ProcessIdleTasks

So, I went ahead and opened my Prefetch folder and deleted its entire contents, including the Layout.ini file.

While leaving the now empty Prefetch folder open for my view, I typed in the above command to my Run Box.

..I'll be buggered...the Layout.ini file was re-created IMMEDIATELY! No need to even reboot the 3 times as prescribed.

Well, I think we all learned something from this thread.

This just keeps getting more interesting. By doing what I did above, it shaved 2 seconds off my complete, round-trip, reboot time.

I compared the new Layout.ini file with my old Layout.ini file from my drive's image. The new one looks sooo clean compared to the old one.

The old Layout.ini file has about a zillion entires and weighs in at 123 KB. The new one is only 5.81 KB...and only lists the basics.

Incidentally, that old Layout.ini file was one re-created after I had manually deleted it and it had re-created itself after 20 minutes of idle time. But, it was never re-created as clean as this new Layout.ini file.

If you clean out the standard Windows entries you will CRIPPLE & SLOW DOWN the Windows XP Quick starts and also slow down opening windows processes.

I cleaned out everything in my prefetch folder, including the .ini file, and disabled it in the registry to no performance detrement at all!

i understand that doing this makes things faster.. but what excatly is prefetch and what am i doing to make things go faster?

586069575[/snapback]

The prefetcher is a feature in Windows that "pre-fetches" parts of programs that you use often. When you start your computer, parts of the programs are loaded into memory so that when you go to run the program itself, it starts up quicker.

It will make your boot time a little bit slower though since there's more work to do here.

The guide is more for people who are having troubles with their Prefetchers. Sometimes - due to viruses and other bad stuff mostly - the prefetcher will stop working altogether.

My recommendation for the prefetcher is based on the amount of RAM that you have:

128MB - Disabled (reg value 0)

256MB - Boot only (reg value 1)

512MB or more - Both (reg value 3)

Hope this helps.

Prefetch Parameters

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters]

"EnablePrefetcher"=dword:00000005

First, I fail to see where any advantage is gained by messing with the prefetch settings. While disabling the prefetch service (or only using setting 1 or 2) can speed boot times it only hurts overall system performance.

Most tweak guides and popular tweaking programs use a setting of ?5?. There is no documentation to suggest that this setting works. MS states that valid values are 0,1,2,3 and that this setting is ?anded?. The default value is ?3?. I tested using a setting of ?5? on 3 occasions and there was no real improvement in boot times and hard drive activity was longer at boot.*

Prefetching is a good thing, leave it alone. In addition well written disk defrag utilities such as Raxco?s Perfect Disk use the layout.ini information for its optimizations.

Source

I always thought the layout.ini file was only actually processed by defrag to determine where best to place files. Therefore, it shouldn't matter if it's MBs in size, since the defrag task is only run when your computer is idle (or you force it with Rundll32.exe advapi32.dll,ProcessIdleTasks).

  • 1 year later...

After quite a lengthy experimentation process I have discovered what the "Tweak Gurus & PC Geeks" don't tell you in their posts on the subject of cleaning the Prefetch folder.

This guide has not been plagiarized. It is totally compiled by me and was once posted by me at the SoftZone Forums.I decided that I did not wan't to be a member of that comunity because they have more rules than posts so I removed this post and others I had made and canceled my membership.So if you have seen it before that is where it came from.

I hope it can be of assistance to some of you that have cleaned your Prefetch folder because you have been told it will speed XP up. But now "like I did" you find that after you have cleaned the prefetch folder your PC now suffers from slow boot up's and general lack of performance. Here is the real deal about the Prefetch Folder

DO NOT REMOVE OR DELETE THE ->(layout.ini)<- FILE WHICH RESIDES IN XP'S PREFETCH FOLDER OR YOU WILL SLOW DOWN YOUR PC AT START UP AND WHEN YOU OPEN WINDOWS PROGRAMS. Once it is gone it can stay gone on some PC'S (like mine) for ever and your Prefetch Folder will never work again no matter what you do in the registry to try to rectify the problem.

If this has happened to your prefetch folder DON'T WORRY because I will now show you in 5 easy steps how you can rebuild the -> (layout.ini) <- file again.

1): make sure that the task scheduler is enabled.If you are un sure go to-> Start/Contrl Panel/Administrative Tools/ Click on Services/ Then in the list of services make sure the Task Sheduler is enabled & restart the service by clicking on Start. Close the Services Folder & go back to desktop.

2): Then go to START/RUN/ and TYPE IN/->cmd<-(without the arrows) CLICK OK. This will bring up the DOS Command screen.

3):You will need to copy and paste this entry in at the flashing cursor

-> rundll32.exe advapi32.dll,ProcessIdleTasks <-(without the arrows) and press ENTER.

4):Now reboot three times and your Prefetch folder will be rebuilt.(It takes 3 reboots for the prefetch folder to work out what it needs)

5):Then go BACK to ->Start/Contrl Panel/Administrative Tools/ / Services/ Once again find TASK SHEDULER in the list and stop the service and then set it to disabled.This will stop any more entries going into your Prefetch folder.

If you need to leave your task sheduler enabled,(No Drama) you will just have to clean out your Prefetch folder manually from time to time.Just remember not to remove the layout.ini file

You should only clean out files ?other than Windows Start up files? in the Prefetch folder.

If you clean out the standard Windows entries you will CRIPPLE & SLOW DOWN the Windows XP Quick starts and also slow down opening windows processes.

No one bothers to tell you the consequence of deleting the (layout.ini file) in all the tips I have seen about cleaning out the Prefetch folder.

Also if you use one of the many programs that are availabe to clean the prefetch folder you will find that they delete the layout.ini file also.

I have now tried about 50 of these so called Prefetch clean programs and they all disable the Prefetch folder completely and for ever which is a crazy thing to do.The Prefetch is one of the best things about XP.

The truth is that only people who don't know what the Prefetch folder is actually for and don't know how it works say that it is useless.

All I can say is that there must be a lot of people with a verry sluggish XP Windows PC's around,,especially at Boot up.

This worked a treat! Thank you!!! I'm forever tinkering with Windows XP, and after a recent purge using System Mechanic, I noticed my Prefetch folder no longer was in use, and thanks to Google and your post, I have rectified the problem and my PC is running nice and fast again!

Thanks a million!

DO NOT REMOVE OR DELETE THE ->(layout.ini)<- FILE WHICH RESIDES IN XP'S PREFETCH FOLDER OR YOU WILL SLOW DOWN YOUR PC AT START UP AND WHEN YOU OPEN WINDOWS PROGRAMS. Once it is gone it can stay gone on some PC'S (like mine) for ever and your Prefetch Folder will never work again no matter what you do in the registry to try to rectify the problem.

First time I heard that..I clear out my prefetch folder weekly :unsure:

the prefetch files are "defragged" every 3 days, so depending on when you clear out your prefetch folder, it could take anywhere from minutes to days for the layout.ini to be recreated.

And yes it's safe to delete the file, it's automatically created when the files are "defragged".

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
    • So how did you solve the problem? Disabling Secure Boot isn’t a solution.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!