Secondary installer comes up with every launch after user profile deleted
IssueEvery time a user logs on and runs the program, an installer dialog box is displayed. When the installer is finished, the program starts up with default user interface settings.
Typically this issue is related to an ActiveDirectory setting associated with roaming profiles called Delete Cached Profiles on Logout. While many Autodesk products support roaming profiles, they do not support many of the additional customizations that can be associated with them. This is because some of the support content installed into the user profile is not designed to be roamable. Therefore, when the cached local profile is deleted and a new copy of the profile is copied down from the server, it does not contain all the files the program needs. This forces the program to fire the secondary installer and replace those files; in the process, all default support content is replaced.
To resolve this issue, you need to disable the deletion of locally cached profiles for users who will be running the application.
Note: The ActiveDirectory setting is only the most common cause of this issue. Similar settings in other user management software (for example, Novell) have been known to cause this issue as well.