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

    • Dupe of "Microsoft further improving Windows 11 Taskbar with latest builds", published <20 minutes apart
    • Dupe of "Windows 11 is getting redesigned taskbar settings in new build", published <20 minutes apart
    • Ooooh! Two editorial from Paul Hill on the same day! Is it my birthday or something? 😉 Okay, let's see if I get it right. SearXNG develops a meta-search engine app. Individuals install it on their relays. Users connect to these relays to have their own identity-stripping meta-search engine instead of relying on DuckDuckGo. And some of these volunteers have listed their SearXNG instances on SearX.space. That was a lot of wrap my head around. I hope I haven't missed anything.
    • You sound like some Ukrainians in Crimea before 2014: "I didn't vote for USSR disbanding - I want Ukraine to be part of Russia again" 🤣
    • Uninstalr 3.1 by Razvan Serea Introducing Uninstalr: Easy to use and very accurate software uninstaller for Windows. It can uninstall multiple apps at the same time and we think it’s pretty cool. Developed with expertise by Macecraft Software - the minds behind jv16 PowerTools. Key Features Batch uninstall many apps at the same time. Supports unattended uninstallation of apps. Supports monitoring of new software installations. Also detects portable apps and previously uninstalled software leftovers. Shows all the data added to your system by installed software on a file by file basis. Shows all the data it will remove before starting the uninstallation. Filter and search the list of installed software. According to our benchmark, Uninstalr is the most accurate software uninstaller by leaving the least amount of leftovers when uninstalling apps. Supports detection and uninstallation of Microsoft Store, Steam, Big Fish Game System, Chocolatey, NuGet and Ninite installed software. Supports Windows Dark Mode. Supports Windows 11, 10, 8 and 7. Comes with these translations builtin: Chinese Simplified, Chinese Traditional, Czech, Danish, English, Filipino, Finnish, French, German, Greek, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Romanian, Slovak, Spanish, Swedish, Thai, Turkish, Ukrainian and Vietnamese. Has a single executable file portable version and a normal setup version. Uninstalr is freeware, lightweight and easy to use. No bells and whistles, no nonsense. Uninstalr’s custom uninstallation engine has a dedicated support for the detection and uninstallation of 15 types of apps: Normal Windows apps Microsoft Store apps Portable apps Chocolatey apps Ninite apps PortableApps.com apps Steam games EA App games Epic Games Store games Riot platform games GOG Galaxy games WarGaming.net games Battle.net games itch.io games Big Fish platform games Uninstalr 3.1 changelog: Key Changes Uninstalr now starts and shows the list of installed apps faster after the initial scan has been completed, and with much smaller memory usage. Uninstalr now detects and highlights apps that automatically start with Windows. Greatly improved the detection of portable apps. Improvements New feature: Uninstalr now detects and highlights apps that automatically start with Windows. New feature: Uninstalr now highlights possible leftovers and apps from Russia and China. This can be disabled from the Settings. New feature: A new filter that allows you to show only software that is installed to other than the system drive. New feature: Users can now select to always do the deepest and the most accurate scan for installed apps, at the cost of the analysis taking a longer time. Greatly improved the detection of portable apps, such as added dedicated support for MiTeC, EZ Tools and SysInternals tools. Improved support for portable apps installed via Windows System Control Center (WSCC). NirSoft portable apps are now listed with "NirSoft" prefix for easier identification. Improved the speed of uninstalling apps. The main installed software listing search will now find "Xbox GameBar" if you search for "Game bar" and vice versa. The tooltip now displays more detailed information of the installed apps, such as its registry key and uninstaller path. The links in the About section now look more like clickable links. The main menu is now more clearly indicated in the main user interface. Microsoft Teams Meeting Add-in for Microsoft Office ships with some Windows 11 installations and is now considered a builtin Windows app and only listed if builtin Windows apps filter is enabled. Added a Help button to the main user interface that opens the help section of the website. Added an option not to close Uninstalr after uninstallation. If you open the Uninstalr website from the app, the website now receives the version number of your current Uninstalr version and warns you if you are using anything but the latest version. Improved the accuracy of the New Software Monitor. Improved confirmation messages for Steam and other platform related uninstalls. Improved the uninstallation performance of Steam games. Fixes: Known bug fixed: Some installed app names are capitalized incorrectly, such as "CCleaner Portable" is listed as "ccleaner portable". Known bug fixed: Some apps can be listed twice, for example, Smart Defrag can be listed once as Smart Defrag and then Smart Defrag Home. Known bug fixed: On the pre-uninstallation screen, the Scripts checkbox can be checked by default on Dark Mode but not on the normal mode. Known bug fixed: Perform Deep Analysis can be started only by clicking the button, not via the Right Click menu, main menu or F4 keyboard shortcut. Muse Hub could be incorrectly listed as Adobe Muse. SyncTrayzor was incorrectly detected as two unrelated software, SyncTrayzor and Syncthing. Smart Defrag was incorrectly listed twice as Smart Defrag 11 and Smart Defrag Home. It was possible to enter non-printable characters to the search input boxes of the main screen, and the path listing screen, which caused the UI to look funny. Changing the translation from Settings, especially many times in a row, caused the UI to distort. If you had multiple instances of portable apps on your system, such as the 64b and 32b versions of the same portable app, typically only one of them was detected, not both. In some very rare cases, Uninstalr UI could start with random characters in its search input boxes, which could make the UI look rather confusing. This was a rare issue, only reported by two users. The pre-uninstallation screen could display non-existing paths for example as the software's installation directory or main exe file. This was a cosmetic issue. New Software Monitor cannot detect the installation of Claude. Selecting all the found software made the UI look funny with the top panel covering everything else (because the names of all the selected software were listed there). Sometimes a Steam game could be listed a normal app instead of a Steam game. If the system restart after an uninstallation is delayed, e.g. because of Windows Updates being installed, this additional delay is incorrectly added to the time how long the uninstallation process took. This cosmetic bug could cause the program incorrectly report an uninstallation time longer than the actual uninstallation time. Uninstalling Minecraft could simply fail. The Only scan the system drive for installed apps setting does not fully work. If some apps are installed to a non system drive and this setting is enabled, the app could still be detected and listed on the main user interface. Changing any settings could also incorrectly alter the Only Scan The System Drive For Installed Apps setting. Microsoft OneDrive and Copilot are not always detected. If you enter something to the search filter field, then select the text and press the Delete key, this triggers the Uninstall button click even if your intent was to delete the text input. If you press the F5 key to refresh the screen during the uninstallation loading screen, the program will crash. If you enabled some setting, such as "Do not analyze installed app installation sizes", it could automatically be unchecked later. Uninstalr doesn't warn you if you try to remove Fortec antivirus. There should be a warning if user attempts to remove any antivirus or antimalware type program. Such programs should not be uninstalled using a third party uninstaller, as they are typically protected against automated uninstallation, for security reasons. With "Do not analyze installed app installation sizes" option checked from the Settings, Uninstalr could still display some installation size related elements in the UI which was confusing. The "Only scan the system drive" option moved under Improve Scan Speed from the General settings. If two software have the exact same name and version number, selecting both of them for uninstallation fails because only one is actually selected. Sorting the installed apps by size sometimes fails and the order is incorrect. The "Don't show which paths are currently analyzed" did not work correctly - some parts of the UI still show the currently analyzed path with this setting checked. The "Don't list software less than 10 MB" filter did not work correctly - some apps smaller than 10 MB could still be listed. Uninstalr could start very quickly and display an empty list of detected apps. Restarting the app usually fixed the issue and the list of installed apps was properly displayed. If you placed portable Uninstalr to a same folder with other portable apps, those were not detected because Uninstalr automatically added its installation folder to the ignore list. When trying to uninstall some specific software, Uninstalr could get stuck on the Searching for more data relating to the app phase. Uninstalr could sometimes do a silent uninstallation even if user had unchecked the Perform a silent uninstallation option. Known issues: Uninstalr can fail to run with an Out Of Memory error in systems that have a lot of installed apps. Using the New Software Monitor tool multiple times during one session can cause the program to get stuck on the Scanning stage. The "uninstallation completed" message box sometimes closes when the user moves the mouse cursor over the button before user clicks it. There is no feedback for the user after Fix Information feature has been used. The Right Click menu's Select by publisher option can display the number of apps per each publisher without correct vertical alignment. The default user interface might not display all of the found installed apps if you have over 600 installed apps. If you do, using the Screen Reader Compatible Interface solves the issue. Leftover apptype filter checkbox is shown in red font only in Dark Mode. Clicking the app's icon from the Windows Taskbar doesn't minimize/restore the app like other apps. The warning about an app that user wishes to uninstall being related to some other app user did not select can sometimes be inaccurate. If app's language is changed without restarting Uninstalr, the list of installed software might not automatically refresh. When software is being uninstalled, the UI can say it is processing paths unrelating to the uninstalled app. This is purely cosmetic and does not mean these paths are removed. Uninstalr might not properly detect and/or uninstall Steam games if they are installed to a drive different than Steam's default location in C:\. You might see "This action is only valid for products that are currently installed" error message from Windows Installer during uninstallation. This is a cosmetic issue. Download: Uninstalr 3.1 | 7.1 MB (Free, paid version available) Download: Uninstalr Setup 3.1 View: Uninstalr Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      153
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!