Now this is a very basic question , but bugs most of the packagers and i bet, most dont know the exact reason.

It is well know fact, when we mark user specific file as a keypath and suppose an application makes use of this file, on first launch in user it will repair. now when in admin , if we launch the shortcut, it will repair(the file was already present in admin, but still it repaired). now again go to user and launch the shortcut again, and the application heals(remember the file was already present in user after first launch in user). Here i m presuming , the location of the file gets hardcoded somewhere in registry , mostly machine specific location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders\<Path of file>. Can somebody please elaborate why is this so.....what exactly happens during this whole process.
I would really appreciate if somebody doesnt ask me to mark registry keypath for user specific file. I m really tired with those answers 

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



Now after doing a little research i found a particular registry location where this file location gets harcoded

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\<Reverse GUID of component>

Answered 05/07/2013 by: talonsprem87
Tenth Degree Black Belt

  • I want to reply with something meaningful, but I dont quite get your question. Where is this file that you have made a keypath?
    • Well the file that i m talking about resides under AppData Folder
  • Just to clarify.
    You have a file that is keypath in the AppData folder. You start the app via the advertised shortcut, the file is already in the AppData folder, but it still repairs that file in the AppData folder?

    If the file is a keypath in the user profile, it should only repair once. If it keeps repairing, something is broken, you need to look in the event log to see what is triggering the repair. Are you sure that something else is not triggering the repair?
    • yes i m dead sure about it....there is just one component i.e. the file under appdata folder.
Please log in to comment