AddInSpy is a specialized diagnostic and troubleshooting tool designed to discover and report detailed data about registered Microsoft Office COM add-ins on a computer.
Originally developed by the Visual Studio Tools for Office (VSTO) team at Microsoft, it serves as an essential utility for software developers, IT administrators, and power users who need to analyze or debug complex Office integrations. Over time, independent open-source developers have also maintained disassembled and expanded versions of the tool, making it publicly accessible on platforms like the NetOffice AddInSpy GitHub Repository. Core Purpose & Functionality
When dealing with multiple tools or custom enterprise software built inside programs like Excel, Word, or Outlook, figuring out why a specific plugin fails to load or crashes can be challenging. AddInSpy scans your Windows registry and acts as a central control panel to audit everything running under the hood.
The tool utilizes a dedicated backend scanning engine (AddInScanEngine.dll) paired with a simple WPF desktop front-end to reveal the following diagnostic details:
Status Tracking: It monitors whether the host Microsoft Office application is running and verifies if the add-in is successfully loaded.
Add-in Type Identification: It detects whether an add-in is a VSTO (Visual Studio Tools for Office) project, a standard managed non-VSTO add-in, or a native COM add-in.
Registry & Metadata Insights: It reports critical identification markers like the FriendlyName, ProgID, CLSID, and LoadBehavior values. It also identifies whether the add-in is registered under the current user (HKCU) or machine-wide (HKLM) registry hives.
Deployment Paths: It tracks down exact file paths for manifests, underlying assemblies, assembly strong names, and specific installation dates.
Environment Requirements: The tool highlights exactly which Common Language Runtime (CLR) version or VSTO runtime version the add-in was compiled against, making it easy to spot version mismatch conflicts.
Extensibility Interfaces: It detects what UI elements the add-in hooks into, including custom Ribbon tabs and custom task panes. Who is it for?
Software Developers: For those building custom Office solutions, AddInSpy provides a quick way to verify registry configurations without manually digging through the Windows Registry Editor.
IT Administrators: When troubleshooting enterprise workstation crashes caused by conflicting Office updates or legacy COM plugins, admins use it to rapidly audit every third-party addition installed on a system.
To see general built-in settings or how to manage basic plugins on the front-end without diagnostic software, check the official guide on how to Manage Store add-ins via Microsoft Support.
If you are trying to solve a specific issue,) you are working with.
The exact error message or behavior you are experiencing (e.g., add-in won’t load, crashing on startup).
Leave a Reply