viewtopic.php?t=20441
Essentially, not having the |vstolocal parameter appended to the Manifest registry value invokes the VSTO installer and causes two instances of the add-in to show up... adding the parameter back, however, causes the locally installed add-in to stop functioning and throw a runtime error when I attempt to enable it.

If I remove the |vstolocal parameter again, when restarting Outlook, I again have two instances of the add-in loading and functioning correctly. The first time I ran through this I double-checked the .AIP but then I decided to rebuild it via the wizard and not touch anything besides loading up my files that need to be dropped into Files and Folders. That being said, if the way I built out the .AIP or the compiled MSI had an issue, the add-in would not load even after removing the |vstolocal parameter but it does. Something about that |vstolocal parameter is creating an issue with the add-in loading correctly.
I am building this to run on Windows 10 1703 in both Outlook 2013 and 2016; I have done two separate builds targeted to both flavors and the issue occurs on both. I would really like this to be installed under the LOCAL MACHINE context for All Users because this is an add-in that our organization would like all users to have when they receive their device... I had planned on adding this to our task sequence so this just gets dropped in during OSD but I can't do that if it has to be installed in the Current User context.
This was one of the features we were excited about this product for, any assistance on this is highly appreciated! Thanks!
FOLLOW US
Get the latest news in Application Packaging