I,ve been portabilizing an app here in our office that we usually use and i was able to and it had been a success, yet, i found out that our app was still leaving a trace at C:\windows\prefetch
our app save's it's settings at the registry at
HKCU\Software\Author\AppName
And i was able to portabilize that. But what else should i do so that our could run without leaving an AppName1234.pf file at C:\windows\prefetch?
You are here
PAL, how to handle that prefetcher?
March 27, 2011 - 5:18am
#1
PAL, how to handle that prefetcher?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
There's nothing you can do about it reliably, and it's core Windows stuff, so we don't try to touch it.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
I think there's something there at the registry about this at HKLM....\Prefetcher.
But does HKLM really 100% in need of admin rights?
-:O =
Prefetch is files in %WINDIR%\Prefetch, not registry data in HKLM. Both, however, require admin to deal with it. You don't need to (and shouldn't) touch prefetch.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Both the HKLM keys related and the prefetch folder itself within the Windows directory require admin rights. And they are generated by Windows itself when you run programs under accounts without admin rights. Meaning that most of the time they are created automatically and you have no rights to remove them. This is the way Windows is designed with this feature.
Sometimes, the impossible can become possible, if you're awesome!
so there's really no way aorund it. But may i know what does .pf files? I mean do info's it have about the app?
-:O =