I use AI's Users and Groups feature to add a special user. Later that user is used by the app in the creation of registry entries, etc, including setting permissions for the special user.
Upon Upgrade, even though the properties of the user will not change, installation removes the original version of the user, and later adds the user back.
Problem is, with Windows, even though the user name is the same, the underlying SID (security ID) will be different after such an upgrade, and therefore permissions established before upgrade are broken. That is, logging as the named user will not invoke the seemingly corresponding permissions. This is a show-stopper for me, and I'd assume for many scenarios. Setting object permissions for a user is common.
Is there a way to avoid removing an AI-installed user upon upgrade?