I have deployed our 2014 products; IDSP and BDSP and all went well. I have a user that was complining about performance. I checked all our settings etc and cant find any system variable that might cause sluggih behavior.
I noticed that everytime the user starts up, the secondary installer runs. It seems like a registry problem? Is there anything I can cut from the registry?
I did a repair and no change. I'll try a reinstall now.
Solved! Go to Solution.
Solved by dgorsman. Go to Solution.
There's two things which come to mind: the HKEY_CURRENT_USER registry and the C:\Users\... path. Both are modified by the secondary installer, so if the user doesn't have sufficient rights the changes won't stick and the programs will think they haven't been run previously.
Found this thread while searching for a solution for this same issue of the secondary launcher kicking in unexpectedly and wanted to share our solution.
We utilize a database called Made2Manage, and whenever we performed a search, the secondary launcher would kick in for all the installed Suite products even though they are already registered and activated.
The solution is an order of installation, if M2M is installed prior to an Autodesk suite, then uninstall M2M and re-install after you've activiated all your suite products. Alternatively, don't install M2M until after you've completed your Autodesk installations.
Order of installation may also work with other applications that may be yielding similar undesired secondary launches.
@llorden4 wrote:
Found this thread while searching for a solution for this same issue of the secondary launcher kicking in unexpectedly and wanted to share our solution.
We utilize a database called Made2Manage, and whenever we performed a search, the secondary launcher would kick in for all the installed Suite products even though they are already registered and activated.
The solution is an order of installation, if M2M is installed prior to an Autodesk suite, then uninstall M2M and re-install after you've activiated all your suite products. Alternatively, don't install M2M until after you've completed your Autodesk installations.
Order of installation may also work with other applications that may be yielding similar undesired secondary launches.
This +1
I recently uninstalled older versions of my Autodesk products (INV 2014, ACAD 2014,etc...) and after that Made2Manage kept firing the Autocad 2016 installer on every browse/search on every screen I did in M2M..
Uninstall M2M and reinstall fixed it