Solved! Go to Solution.
Although I'm not running Office 365, some versions may have the ability to stop Outlook from disabling add-ins it considers 'slow':
Note: If the plugin has already been temporarily re-enabled, clicking Disable this add-in and then clicking Always enable this add-in will permanently enable it.
Hi Syed,
What can happen with Outlook sometimes is, it believes that certain plugins slow down performance and disables these automatically.
Microsoft reference: https://support.microsoft.com/en-us/help/2758876/add-ins-are-user-re-enabled-after-being-disabled-by...
Programs in Office 2013 and later versions provide add-in resiliency in that the apps will disable an add-in if it performs slowly. However, you can re-enable the add-in and select the "Always enable this add-in" option to prevent the add-in from being auto-disabled by the Office program. For example, the following figure shows an add-in that was disabled because it caused Outlook to shutdown slowly. The option to "Always enable this add-in" is shown as well.
Here's one other referenced User solution if that should fail: https://www.slipstick.com/outlook/always-load-an-outlook-addin/
Although I'm not running Office 365, some versions may have the ability to stop Outlook from disabling add-ins it considers 'slow':
Note: If the plugin has already been temporarily re-enabled, clicking Disable this add-in and then clicking Always enable this add-in will permanently enable it.
Meet now is missing from the calendar meeting view ribbon. I've attached two screenshots. I also uninstalled and reinstalled all GoToMeeting related applications and tried a reboot. ,
@ahauer Let us know if the MS Outlook fix directed here does not work in your situation.
Hello, thank you for your prompt reply. It does not fix the issue.
If you've already tried reinstalling the Outlook plugin, with no error messages shown, then you might try this CLI installer we developed: Outlook CLI Installer Tool
I have the same problem as ahauer. The CLI installer runs the same install as setup.exe did, but I don't see the add in no matter how hard I look.