Why Does Outlook Keep Disabling My NetDocuments Add-Ins?

Understanding Outlook Resiliency Keys and LoadBehavior

If you’ve ever come into the office, opened Outlook, and found that your NetDocuments add-ins have mysteriously disappeared from the ribbon, you’re not alone. This is one of the most common support issues we see across NetDocuments implementations, and the culprit is a built-in Microsoft feature called Outlook Add-in Resiliency.

The good news? There’s a straightforward registry fix that prevents this from happening.

What Is Outlook Add-in Resiliency?

Microsoft Outlook includes a performance monitoring feature that tracks how long each add-in takes to load at startup. If an add-in exceeds a load time threshold — or causes Outlook to crash — the resiliency manager automatically disables it on the next restart.

From Microsoft’s perspective, this is protective. From a NetDocuments user’s perspective, it’s a frustrating disruption. Users lose access to the NetDocuments ribbon, email filing, and ndMail functionality without any obvious explanation. Often the only indication is a small notification bar at the top of Outlook that’s easy to miss.

Why NetDocuments Add-Ins Get Flagged

NetDocuments relies on three Outlook add-ins:

• Client.OutlookAddIn — The core integration providing the ribbon toolbar, document access, and Save & File functionality.
• ndMail.OutlookAddIn — Powers email filing, predictive filing suggestions, and the filing panel.
• MailSync — Handles folder-based email synchronization between Outlook and NetDocuments workspaces.

All three need to be initialized, authenticated, and connected to the NetDocuments cloud at startup. On slower machines, over VPN, or during high network latency, this can exceed Outlook’s load time threshold, causing Outlook to disable the add-in on the next restart.

The Fix: Two Sets of Registry Keys

A reliable NetDocuments workstation setup requires two complementary sets of registry keys working together:

• DoNotDisableAddinList keys (HKCU) — prevent Outlook’s resiliency manager from automatically disabling the add-ins.
• LoadBehavior keys (HKLM) — ensure the add-ins are configured to load every time Outlook starts.

Think of it this way: LoadBehavior is the instruction to load the add-in, and the resiliency key is the protection that keeps Outlook from changing that instruction on its own. Without both, you’re leaving the door open for add-ins to silently disappear.

Part 1: DoNotDisableAddinList (Resiliency Keys)

These keys are located at:

HKCU\Software\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList

The three values you need to create:

Setting each to 1 tells Outlook to keep these add-ins loaded regardless of performance behavior.

Part 2: LoadBehavior Keys

The LoadBehavior registry value controls how and when Outlook loads each add-in. It’s stored under each add-in’s registration path in HKLM, meaning it applies machine-wide to all users on that workstation.

The three paths and values you need to set:

HKLM\Software\Microsoft\Office\Outlook\Addins\NetDocuments.Client.OutlookAddIn

HKLM\Software\Microsoft\Office\Outlook\Addins\NetDocuments.ndMail.OutlookAddIn

HKLM\Software\Microsoft\Office\Outlook\Addins\MailSync

Setting each to 3 means “load automatically at startup.” This is the standard setting that the NetDocuments installer configures, but it can get changed if a user manually disables an add-in through Outlook’s COM Add-ins dialog, or if Outlook’s resiliency manager intervenes and resets the value.

Why the HKCU Keys Often Get Missed

When we go live with a NetDocuments implementation, we provide the firm’s IT team with a batch file that should automatically configure all of these registry keys. The HKLM keys — including the LoadBehavior values — typically deploy without issue because they run once under administrator privileges and apply machine-wide.

The HKCU keys are a different story. Because HKCU is user-specific, these keys must be created under each user’s registry hive. In practice, we see this go wrong frequently. The batch file may run before the user has logged in, or IT may deploy it in a system context that doesn’t map to the user’s HKCU. The result is that the resiliency keys never actually land where they need to be, and users start losing their add-ins within a few days or weeks of going live.

If your users are reporting that NetDocuments add-ins are disappearing after a recent go-live, the HKCU resiliency keys are the first thing to check.

What About the NetDocuments M365 Outlook Add-In?

This is a common point of confusion. NetDocuments offers a separate M365 Outlook add-in that is deployed through the Microsoft 365 admin center or the Office Add-ins store — not through registry keys or a local installer. This is a web-based add-in built on Microsoft’s modern Office Add-in platform, and it works across Outlook desktop, Outlook on the web, Outlook for Mac, and mobile devices.

None of the registry keys discussed in this article has anything to do with the M365 Outlook add-in. The resiliency keys and LoadBehavior values apply exclusively to the traditional COM/VSTO desktop add-ins (ndMail, the NetDocuments Client, and MailSync) that are installed locally on Windows workstations.

This is a misconception we encounter regularly — people assume that because both involve NetDocuments and Outlook, they must be related. They are not. The M365 add-in and the COM/VSTO add-ins are entirely separate integrations, deployed and managed differently, and affected by different issues. If you’re troubleshooting disappearing add-ins in Outlook desktop on Windows, you’re dealing with the COM/VSTO add-ins, and the registry keys in this article are your fix.

A Note on the Registry Path

The 16.0 in the resiliency key path corresponds to Microsoft Office 2016, 2019, and Microsoft 365 — they all share the same registry version number. Virtually all firms running NetDocuments today are on Microsoft 365, so 16.0 is the correct path for most deployments. For Office 2013, use 15.0 instead.

Summary

Outlook’s add-in resiliency feature is well-intentioned but frequently causes problems for NetDocuments users. By deploying both sets of registry keys — LoadBehavior to ensure add-ins load at startup, and DoNotDisableAddinList to prevent Outlook from overriding that setting — you can keep the NetDocuments Client, ndMail, and MailSync add-ins active and available.

No more missing ribbons, no more lost filing panels, and no more confused users wondering where their NetDocuments tools went.