The fact that the add-in seemed to be only failing on institutional devices led me in the wrong direction for this problem. I've been able to disable all VBA addins in the group policy editor - and this is consistent with not seeing VBA addins marked as being disabled in the Trust Center Settings, however, setting this policy also disables per-user addins - which I am not seeing.
Addins are NOT disabled in Trust Center Settings -> AddinsĮarlier theory - ruled out - group policy setting. Using an alternative installer - created with inno setup script, which installs for the current user only, modifies HKCU entries and puts the addin in "C:\Users\username\AppData\Roaming\Microsoft\AddIns" results in the addin loading without problem when PowerPoint opens. The add-in appears in the program files directory. 
The installer runs and the installation appears in the apps and features list and can be uninstalled. is replaced with the current version, for example "16.0" (This comes from "PowerPoint.Application\CurVer" in HKCR appended with ".0") - with autoload set to 1 and path set to the path of the ppam addin file in the Program Files directory.īoth the addin and the installer are signed with an EV code signing certificate. The addin is enabled in the registry in the HKLM hive: "SOFTWARE\Microsoft\Office\PowerPoint\AddIns\NameOfAddin". The addin goes into its own folder in "C:\Program Files (x86)". The MSI installer is run (requiring administrator privileges). Unfortunately, some users - on machines within organisations such as schools - do not get these buttons in the ribbon and the addin appears not to be loaded although the MSI installer runs without complaint. 
Following installation, a user gets some additional buttons in the PowerPoint ribbon to run the addin functions.
I have a PowerPoint VBA addin (ppam file) which is packaged in an MSI installer for installation for all users of a machine.
0 kommentar(er)
