Custom Word add-in installs but fails to run properly on Windows

Question

Hi guys, I’ve built a custom add-in for Microsoft Word and tried deploying it on a Windows machine, but I’m running into issues getting it to actually run after installation. I published the add-in and installed it like I normally would, but once I open Word and try to use it, I get an error message popping up. This is kinda stressing me out since I’m preparing to roll this out internally at work before selling it externally, and right now it just doesnt behave properly at all. Am I missing some step in the install or config process to make the add-in work correctly?

Answer 1

Hi Manish Rahul,

The CLSID {000209FF-0000-0000-C000-000000000046} specifically belongs to Word.Application. The 0x80080005 (Server execution failed) error means Windows COM tried to launch or connect to Word but was aggressively blocked. In custom Add-in development, this almost always boils down to one of two things:

1. The "Privilege Mismatch" (Most Common) COM architecture strictly forbids communication across different integrity levels.

If your Add-in (or the application/installer calling it) is running "As Administrator", but Word is launching as a Standard User (or vice versa), COM will completely block the connection and throw this exact error.

The Fix: Ensure both Word and your Add-in/development environment are running at the exact same privilege level. Typically, you want to run both normally (not as Admin) during daily use.

2. Ghost WINWORD.EXE Processes If an earlier debug session crashed or closed improperly, you might have an invisible Word process hanging in the background holding the COM factory hostage.

The Fix: Open Task Manager -> go to the Details tab -> look for any instances of WINWORD.EXE and forcefully End Task on all of them. Then try opening Word to trigger your Add-in again.

Try killing any background Word processes first, and double-check your admin privileges. If this gets your add-in communicating with Word correctly again and saves your rollout, please consider clicking "Accept Answer". It hugely helps other developers save their sanity when they hit this exact COM block!

Tracy.

Answer 2

The add-in is installing correctly but Word is failing to start/host it reliably on that machine. Use these steps to isolate whether the problem is Word/Office itself, a conflicting add-in, or the deployment of the custom add-in.

1. Check whether Word itself is stable (Safe Mode)
   Start Word in Safe Mode to see if it can run without any COM/VSTO add-ins:
   • Press Windows + R → type winword /safe → Enter.
   • Confirm the title bar shows (Safe Mode).
   • If Word does not start in Safe Mode, the issue is with Office or the device, not the add-in. In that case, run an Office repair (step 4).
2. If Word starts in Safe Mode, disable other add-ins
   A conflicting add-in can prevent the custom add-in from loading correctly.
   • With Word still in Safe Mode, go to File > Options > Add‑Ins.
   • In Manage, choose COM Add-ins (or Word Add-ins) → Go.
   • Clear all checkboxes to disable third‑party add-ins → OK.
   • Close Word, start it normally, and then enable only the custom add-in and test.
   • Re‑enable other add-ins one by one to identify any conflict.
3. Check the Normal template and compatibility mode (for Word add-ins)
   If the add-in interacts with shapes or document content and the document is in Compatibility Mode, APIs may fail:
   • Create a new document from the default template and check that Compatibility Mode does not appear in the title bar.
   • If it does, update the default template by renaming Normal.dotm so Word creates a fresh one, then test again.
4. Repair Office on the affected machine
   The COM error and “run into an error” behavior often indicate a damaged Office installation.
   • Close all Office apps.
   • In Windows Settings > Apps > Installed apps, select the Office product.
   • Choose Modify → run an Online Repair (more thorough than Quick Repair).
   • After repair completes, reboot and test the add-in again.
5. If this is a web add-in, validate manifest and runtime environment
   For Office Web Add-ins:
   • Confirm the manifest is valid and deployed correctly (SharePoint catalog, network share, or Centralized Deployment).
   • If users see “This add-in is no longer available”, ensure the manifest file still exists at the deployment location, the Id has not changed in the deployed copy, and all resid values are defined and ≤ 32 characters.
   • If the add-in only fails on specific machines, check for:
     • Antivirus blocking WebView2 (E_ACCESSDENIED (0x80070005)); add exclusions for the Office root folder and WebView2 executable if needed.
     • Outdated or unsupported browser components (for Outlook/Word web add-ins using IE or WebView2); update Office and the browser components.
6. Use Process Monitor if installation/loading still fails
   If the add-in still cannot be created or loaded, use Process Monitor on a working and a failing machine to compare file/registry access for Word and the add-in. Differences often reveal missing permissions, files, or registry keys that block COM activation.
7. Before broad rollout
   • Verify the add-in on a clean, fully updated Office installation.
   • Document supported Office versions and commit to updating the add-in when Office is updated, so internal and external customers know it is supported.

Following this sequence (Safe Mode → disable other add-ins → refresh Normal template/compatibility → Online Repair → manifest/antivirus checks → Process Monitor) will usually identify whether the failure is due to Office corruption, environment/configuration, or the add-in deployment itself.

---

References:

• Troubleshoot user errors with Office Add-ins
• Troubleshoot development errors with Office Add-ins
• Troubleshoot Word add-ins
• I get a "stopped working" error when I start Office applications on my PC
• Development best practices for COM, VSTO, and VBA add-ins in Office
• how to fix word error - Microsoft Q&A word has run into an error preventing it from working properly
• word will not open "Would you like to repair now? - Microsoft Q&A
• how fix run into an error problem - Microsoft Q&A
• We're Sorry but Word Has Run Into an Error - Microsoft Q&A