I had an installer which worked fine on one machine. Testing on a second machine it failed to install files in the APPDATA area.
I found that the difference was that the on the first machine the user was admin, so it did a per machine install. On the second machine, the user wasn't admin so it did a per user install and failed to write the APPDATA.
The problem seems to be that the installer was putting the executable in Program Files, which isn't a per user location and therefore isn't allowed. But this seems very odd, the Per User install manages to install the exe in a non-per user area, but failed to install the other data in an area it was allowed to.
Is that expected behaviour, because I want to be sure I have really fixed the problem.
I seem to have fixed things by turning on Per User for all users, which automatically warned me about the exe file and moved the Application Folder to a per user location.
If this is really the case, I think it would be helpful if AI detected this situation and warned about it, because it had me scratching my head for a while!
FOLLOW US
Get the latest news in Application Packaging