Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Outlook disabled an add-in because it was slow (Event ID 59): how to keep it enabled

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Outlook, like the other Office programs from Office 2013 onward, disables an add-in that performs slowly and shows a notification the next time it starts. Microsoft's page says you can re-enable the add-in and choose Always enable this add-in so the program does not disable it again. The cost is that the slowness Outlook reacted to can come back.

Read Event ID 59 first, because it states which add-in was disabled and why. Record the registry key that the Always enable choice writes to before you use it.

What the error means

Microsoft's page on add-ins that users re-enable says: "Programs in Office 2013 and later versions provide add-in resiliency in that the apps will disable an add-in if it performs slowly." The page gives an example of an add-in disabled because it caused Outlook to shut down slowly, with the option Always enable this add-in shown on the notification.

Two events matter, both in the Application event log:

  • Event ID 45 records an add-in's load time in Outlook.
  • Event ID 59 is added when an add-in causes a performance problem. The page's example, source Outlook, level Warning, reads "Outlook disabled the following add-ins" and lists the ProgID, the GUID, the name, the Load Behavior, a Threshold Time in milliseconds, the Time Taken in milliseconds and a Disable Reason. In the example the Disable Reason is "This add-in caused Outlook to close slowly." with a threshold of 500 milliseconds and a time taken of 719 milliseconds.

On the next start Outlook shows a notification. Selecting View Disabled Add-ins opens the Disabled Add-ins dialog box, where Always enable this add-in keeps the add-in enabled even if it performs slowly.

Microsoft's page warns: "If you re-enable an add-in that caused a performance problem at one time, you may experience performance problems in the future in the Office program under which the add-in is loaded."

Likely causes

Cause What you see How to confirm
Add-in slow when it loads Event ID 59 for an add-in that loads slowly; Microsoft's table of values names the reasons boot load and demand load Event 59 text and the Time Taken against the Threshold Time
Add-in slow at shutdown Event ID 59, "This add-in caused Outlook to close slowly." The Disable Reason in the event
Add-in slow when the user changes folders or opens an item Event ID 59 naming a folder switch or item open reason The reasons listed on Microsoft's table of values, such as Handling FolderSwitch event or Item Open
Add-in crashed Outlook or cannot be loaded Add-in disabled again after you re-enable it Microsoft says Outlook cannot be prevented from disabling an add-in in these two cases

The reasons in the third row come from Microsoft's table of values for the DoNotDisableAddinList entry. They record why the add-in was originally disabled: boot load, demand load, crash, handling FolderSwitch event, handling BeforeFolderSwitch event, item open, iteration count, shutdown, and two crash cases where the add-in was not disabled.

Prove the cause before changing anything

All of these read only.

  1. Open Event Viewer, go to the Application log and find the Event ID 59 entry from source Outlook. Note the ProgID, the Name, the Time Taken, the Threshold Time and the Disable Reason.
  2. In Outlook, check which add-ins are listed as slow or disabled. Microsoft's page names Slow and Disabled COM Add-ins on the File tab in Outlook 2016, and Slow and Disabled Add-ins in Outlook 2013.
  3. Record what is already stored under the Resiliency key, which holds the DoNotDisableAddinList entries for add-ins that were re-enabled. For Outlook 2016, 2019 and Microsoft 365 the key is under 16.0; for Outlook 2013 it is under 15.0:
reg query "HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency" /s

The reg query page documents the syntax reg query <keyname>, the /s option that queries all subkeys and value names recursively, and says a key name containing a space must be in quotes. If the command reports an error, the Resiliency key may not exist yet; in that case skip the export in the Fix section.

  1. Read the Event 45 entries for the same ProgID. Microsoft's page says they record the add-in's load time.

Example (illustrative): at contoso.com.au a user on rds01 runs a quote-lookup add-in with ProgID QuoteLink.Connect. Event ID 59 says Time Taken (milliseconds): 719 against Threshold Time (milliseconds): 500, with Disable Reason: This add-in caused Outlook to close slowly. The overrun is 719 minus 500, which is 219 milliseconds. The add-in is slow by a small margin. Microsoft's page warns that performance problems may return, so the event log is worth watching afterwards.

Fix

The fix has three parts: fix the add-in, re-enable it for one user, or manage it for many users.

Improve the add-in itself

Microsoft's support page lists suggestions for add-in owners: prefer native COM add-ins over managed add-ins, because managed add-ins load the .NET Framework at Outlook start-up; move long-running tasks, such as an expensive database connection, to after start-up; cache data locally instead of making network calls during the FolderSwitch and BeforeFolderSwitch events or item Open events; avoid long-running Outlook object model calls, which run on Outlook's main foreground thread; and prefer events to polling. Pass these on to the add-in's vendor with the Event 59 text.

Re-enable it for one user

Save first. Export the Resiliency key to a new file so you have a record of what exists. If the earlier reg query of that same key reported an error, skip this block and note that in your records:

reg export "HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency" C:\Temp\resiliency-before.reg

The reg export page says the file must have a .reg extension and that the /y option overwrites an existing file without asking, so leave /y off and use a new file name each time. Create C:\Temp first if it does not exist.

Risk: The next step keeps a slow add-in enabled. Microsoft's page says the registry is updated to exempt the add-in from automatic disabling, and warns that performance problems may return in the program under which the add-in is loaded. The change applies to the signed-in user.

  1. In Outlook, select View Disabled Add-ins in the notification, or open the Disabled Add-ins dialog box.
  2. Select the add-in and choose Always enable this add-in.

Microsoft's page says Outlook then writes the add-in to HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\<application>\Resiliency\DoNotDisableAddinList as a DWORD named for the ProgID, with a value from 1 to A that records why the add-in was first disabled. The x.0 stands for the Office version, 16.0 for Office 2016, and 15.0 for Office 2013.

To undo it: on the File tab, select Slow and Disabled COM Add-ins in Outlook 2016 (Slow and Disabled Add-ins in Outlook 2013), select Disable this add-in below the add-in, select Close, then exit and restart Outlook. Microsoft's page does not say whether this also removes the DoNotDisableAddinList entry, so the entry may remain. Run the reg query command above again to see. If the entry for your add-in is still there, delete only that value, using the ProgID you noted from Event ID 59 (this works whether or not the key existed before your change; the reg delete page documents /v <valuename>, and without /f it asks for confirmation):

reg delete "HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList" /v <ProgID>

The exported file C:\Temp\resiliency-before.reg, if you made one, is a record to compare with, and the delete above never touches it.

Manage it for many users

Microsoft's page says group policy can control add-ins from Office 2013 onward and that group policy always overrides user settings. The setting is "List of Managed Add-ins", stored as a string named for the add-in's ProgID in HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\AddinList for Outlook 2016, 2019 and Microsoft 365 (15.0 for Outlook 2013). Its values are 0 for always disabled (blocked), 1 for always enabled and 2 for configurable by the user. Microsoft's pages give no step-by-step path through the Group Policy editor.

What Microsoft says cannot be fixed this way

Microsoft's support page says you cannot prevent Outlook from disabling an add-in that crashes Outlook or that cannot be loaded, and that the cause of the crash or load failure needs to be fixed together with the add-in owner.

Confirm the fix

  • Restart Outlook. The notification about the add-in no longer appears.
  • The add-in is listed as active in the Add-ins section of Outlook Options.
  • Event ID 59 for the same ProgID does not appear after the restart.

What to watch afterwards

  • Event ID 45 entries for the add-in. Microsoft's page says they record the load time, so compare the figures with the old Time Taken.
  • Start-up and shutdown speed for the user. Microsoft says to consider disabling the add-in manually "if you continue to experience slow performance or instability issues in Outlook".
  • Any add-in that returns to the disabled list after the next update, which suggests the problem is one that Always enable cannot hold off.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's pages describe Office 2013, 2016 and later, give the registry paths for 15.0 and 16.0 only, and do not give a threshold that applies to every add-in: the 500 millisecond figure is the value in Microsoft's example event. Microsoft's pages say nothing about importing an exported Resiliency key back, so the exported file is a record to compare against, not a restore step. Always enable this add-in is a per-user setting stored in the registry; a Group Policy list overrides it.

Sources