Remove add-in from blacklist

This guide explains how to re-enable the FacilityNet Outlook Add-in if it has been blacklisted by Outlook.

Alternatives

If you haven't already, try this guide first to re-enable the add-in. Note that if the add-in has disappeared because Outlook has blacklisted it, that guide will not be sufficient. Proceed with this guide.

If you want to protect your entire organization from Outlook disabling the add-in, you can set up a group policy by following this guide.

Outlook Blacklists

Outlook maintains 2 blacklists in the registry, and for Outlook 2016 (32-bit), they are located under this key:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency

One is in the "CrashingAddinList" key, and the other is in "DisabledItems". They both have the same structure:

• One value for each blacklisted add-in of type REG_BINARY.
• Names consisting of random characters.
• The path to the add-in as data, but in a format that can be somewhat challenging to decipher.

Here is an example of a blacklist with 2 add-ins:

If you open the first one, you can see that it is TeamViewer's add-in that has been blacklisted:

Removing FacilityNet Add-in from the Blacklist in Outlook 2016 (32-bit)

1. Open the Registry Editor.
2. Navigate to the key "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList".
3. If a value in the data contains the word "CateringPortal" or "FacilityNet", delete the value.
4. Repeat for the key "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems".

Removing FacilityNet Add-in from the Blacklist in Other Outlook Versions

64-bit

For 64-bit versions of Outlook, the procedure is the same, but instead of "Software\Microsoft", the key is located in "Software\Wow6432Node\Microsoft\Office". So for Outlook 2016 64-bit, the full path would be:

HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\16.0\Outlook\Resiliency

Other Releases

For other versions of Outlook, the procedure is the same, but the "16.0" in the key path needs to be changed to the appropriate version:

``` I've translated the provided text to English while keeping the formatting intact.