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

    • A different thing with Russia. When you say is it better, depends on things. It is better that we don't have the E.U making rules and laws that have nothing to do with them. Is the trading part better? No, that is really mucked up, but then we knew that was going to happen and we would have make agreements, like we do with other parts of the world. Freedom of movement is certainly better, but could be improved, we still need more control over our borders. do you live in the U.K?
    • So what am I quoting from them? I never listened to what Farage or his cronies said. I wanted the U.K to leave the E.u years before the referendum and it had nothing to do with Farage and his cronies. So what country do you live in? Did we work much better together? We were always at logger heads with the E.U because we disagreed with them so much. Maggie was always on at them. I would have thought the E.U was glad to get rid of us as we stopped the integration or made it a two tier. Now without us they can integrate more. I would not have voted out if it was just a trading block and we can still work together on somethings.
    • MPC-BE 1.9.0 by Razvan Serea Media Player Classic - BE is a free and open source audio and video player for Windows. Media Player Classic - BE is based on the original "Media Player Classic" project (Gabest) and "Media Player Classic Home Cinema" project (Casimir666), contains additional features and bug fixes. The BE mod (Black Edition Mod) is a skinned version of Media Player Classic Home Cinema, much better looking than the plain old MPC. MPC-BE 1.9.0 changelog: Splitters Fixed crashes in some situations. AudioSplitter Added support for the RF64 format. Fixed reading of channel layout for some WavPack files. Added support for ID3 tags for Wave64 files. Unknown Wave64 chunks are now ignored. AviSplitter Added support for 'y408' video. Improved support for 'HEVC' video. FLVSplitter Added support for VVC video. MP4Splitter Improved handling of corrupted files. MatroskaSplitter Expanded support for V_UNCOMPRESSED video codecs. Fixed support for frame rotation (ProjectionPoseRoll). Improved support for "V_MS/VFW/FOURCC / HEVC". MpcDvdVideoDecoder Fixed conversion to YUY2. Fixed display of menus for some DVD-Videos. RoQVideoDecoder Output in NV12 and YV12 formats is allowed. Full range is used. MPC Video Decoder RGB32 format will be output as a top-down bitmap by default. Added support for the "IID_MediaSideDataDOVIMetadataV2" interface. Removed support for the deprecated "IID_MediaSideDataDOVIMetadata" interface. Fixed retrieving the name of the video adapter when using NVDEC. Fixed crashes in some situations. MPC Video Converter Added support for AYUV video format. MpcAudioRenderer Improved input format validation. Optimized retrieval of supported formats for exclusive mode. Added the "Keep audio device active when paused" setting. Fixed crashes and freezes in various situations. Subtitles Added the ability to open the properties of an external subtitle renderer in the "Subtitles" settings panel. Fixed external subtitle connections for VSFilter. Fixed a crash when rendering PGS/SUP subtitles when using AVX2. YouTube Improved support for yt-dlp. The built-in YouTube parser is no longer used. Player The HTTP read strategy has been changed. If the playlist contains one entry, more key combinations can be used to control the player (jump through chapters, adjust volume). Improved support for reading ASX playlists. The translation of the MediaInfo report for Chinese, Korean and Japanese has been removed. Added blocking of 32-bit filter "PICVideo Lossless JPEG Decompressor" (pvljpg20.dll), because it crashes. Added blocking of the system filter "AVI Decompressor", which will eliminate the crash of VFW codecs. Fixed a rare crash when using the "/slave" key. Fixed a crash when getting a list of fonts for OSD. Added the ability to load an external audio file using hotkeys. Fixed opening a network path starting with \?\UNC. The "Determine duration when adding" playlist setting now works for YouTube video URLs. The "Online media services" settings panel has been redesigned. Added a "Merge files using FFmpeg" option to the file saving dialog. This option is activated when playing multiple streams obtained using yt-dlp. Added loading of local .dpl playlists ("DAUMPLAYLIST"). Fixed a hang when the user closes the player during the URL opening process. Various interface fixes. Installer Updated MPC Video Renderer 0.10.5. Updated MPC Script Source 0.2.17. Added MPC Image Source 0.3.6. Translations Updated Japanese translation (by tsubasanouta). Updated Chinese (Traditional) and Dutch translation (by beter). Updated Romanian translation (by Andrei Miloiu). Updated Hungarian translation (by mickey). Updated Turkish translation (by cmhrky). Updated German translation (by Klaus1189). Updated Chinese (Simplified) translation (by wushantao). Updated Italian translation (by mapi68). Updated Korean translation (by Hackjjang). Updated Chinese (Traditional) (by udfbe). Updated libraries dav1d 1.5.3-6-g04b69f9; ffmpeg n8.2-dev-1857-g4653e68aab; libpng git-v1.6.55-9-g7d52a8087; Little-CMS git-lcms2.18-26-gf739cda; MediaInfo git-v26.05-38-g702c9b7fd; ZenLib git-v0.4.41-91-g073f297; zlib 1.3.2. Download: MPC-BE 64-bit | Portable MPC-BE 64-bit | ~20.0 MB (Open Source) Download: MPC-BE 32-bit | Portable MPC-BE 32-bit Link: Media Player Classic - BE Home Page Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Apple reportedly looks to blacklisted Chinese memory chips as RAM prices climb by Karthik Mudaliar Image via Apple Apple is reportedly trying to get a clearance from the Trump administration to buy memory from ChangXin Memory Technologies (CXMT) to get some relief from soaring DRAM prices. As per a report by the Financial Times, Apple approached the Commerce Department more than a month ago and also spoke to other officials and allies in Washington. For starters, CXMT is a company that's already been placed on the Pentagon's list of Chinese military companies. The Chinese company is the country's top DRAM maker. For Apple, the timing is certainly awkward but not surprising. Tim Cook had recently warned that Apple would have to raise prices because AI companies are buying up large amounts of memory for data centers, and just like that, Apple raised MacBook and iPad prices. Micron also recently revealed that customers have committed billions of dollars to secure memory supply years in advance, which shows us how aggressive securing infrastructure has become. This gives suppliers such as Samsung, SK Hynix, and Micron more leverage, while pushing hardware makers to look for alternatives. CXMT is one of those alternatives, but not the simplest one. Apple has spent many years trying to diversify parts of its supply chain away from China, especially for final assembly, while still depending heavily on Chinese manufacturing and suppliers. Even domestic brands from China are moving towards CXMT and YMTC instead of relying on Samsung, Micron, and SK Hynix. For Apple, though, it would invite more scrutiny than local Chinese companies. For now, this is more like a lobbying effort rather than a confirmed supply deal. There's no official statement from either of the parties. What is clearer, though, is the pressure behind such a request. AI demand has certainly made hardware a bottleneck, and companies are trying everything they can to bring things back to normal, even if that means making politically sensitive choices. Source: Financial Times
    • I did test it a month or so back, but ... the results I expect to be on the first page are not there.
  • 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
      486
    2. 2
      +Edouard
      220
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      Steven P.
      74
    5. 5
      FloatingFatMan
      70
  • Tell a friend

    Love Neowin? Tell a friend!