I'm packaging an app that by default installs to “C:\Users\local-user-name\AppData\Roaming\VendorName\AppName”. Since I need a Per Machine install, I sent an email to the vendor asking if a per machine install was possible. Meanwhile I re-engineered the app in Installshield to install to “C:\Users\Public\AppData\Roaming\VendorName\AppName”. It works fine so far. I then received a response from the vendor suggesting moving the install folder to “C:\Users\Default\AppData\Roaming\VendorName\AppName”.

My question is - Is there really any difference between installing to “C:\Users\Public" or “C:\Users\Default"? I'm kinda looking for a best practice.

Answer Summary:
See the answers given below
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



Is it MSI or Legacy EXE?

Answered 04/03/2013 by: jagadeish
Red Belt

  • Legacy .exe
  • Is this application has any shortcut? any registries?
  • Shortcuts and several registry keys. Only one key needed editing to correct the new file path. As I said, I've already got it working. I'just just wondering if I'm using a valid and correct file path.
  • Why don't you move them to C:\Program Files\VendorName\AppName folder.. Instead of keeping them in Roaming...
  • That may or may not break the whole thing. The path I have now has no spaces in it.
  • You will have to test the functionality of the applcation once you redirect the path.. if you are worried like this then no application can be packaged..
Please log in to comment


"In public normal users cannot delete the icons if they do not want them if placed in default they can.  On existing machines when placed in public all user get that icon even if they have an existing profile.  On an existing machine when placed in default only new users will get that icon."

Answered 04/03/2013 by: SnowLyric
Second Degree Brown Belt

  • This is the answer I was looking for. Thanks. @jagadeish - I was able to get the application to work in C:\Program Files.
  • Great..
Please log in to comment