Skip to content
VediramVediram

See every Office add-in. Decide which ones load.

Deck finds every add-in installed in Office on a machine, groups them into profiles you switch in one click, and names the add-in behind each crash. IT can set it all through Group Policy.

Read the Deck documentation
  • Five add-in kinds, nine Office apps
  • Your original setup, always one click back
  • 17 Group Policy settings
  • Sends nothing to Vediram

Add-ins Office keeps out of sight

Add-ins arrive with the tools the business buys: a CRM pane for Outlook, a reporting pack for Excel, a document stamp for Word. Each one loads every time its app starts, and Office spreads them across three dialogs and a set of registry keys.

When Excel opens slowly or Outlook crashes, nobody can tell which add-in to blame. After a bad start, Office quietly turns an add-in off, and the user finds the missing toolbar mid-deadline.

COM Add-insFile › Options › Add-ins › Manage › Go…
Excel Add-insA separate dialog, for XLLs and Automation add-ins
My Add-insA third place, for web add-ins

Every add-in in one list. Profiles for every kind of day.

Deck lists everything Office would load, with the publisher and version read from the add-in itself. Group add-ins into profiles, one for month-end close, one for the road, one for Outlook with nothing in it, and switch from the app or the tray.

Deck asks running Office apps to pick the change up. Any app that cannot gets it the next time it starts. When a profile enables an add-in Office had turned off, Deck clears that block too.

ExcelOutlookWordPowerPointOneNoteVisioProjectAccessPublisher

When Office crashes, get a name

Deck reads what Windows and Office record about a crash, then the crash dump itself, down to managed .NET code. The report names the add-in and the module at fault.

Start-up times are charted for every add-in at every Office start, so the slow one shows up on a graph.

IT sets the rules with Group Policy

Deck ships ADMX templates with 17 settings. Users see which settings IT manages, so a control that does not respond explains itself.

  • Profiles from one file on a share
  • Which Office apps Deck manages
  • Excel XLLs forced on, forced off, in order
  • Web add-ins from a trusted catalogue share

Install it the way you install everything else

  • One MSI, per user or per machine
  • Silent install for SCCM or Intune
  • Portable ZIP, no install
  • Signed releases with checksums

Deck runs on Windows 11 and manages classic desktop Office: Microsoft 365 Apps and Office 2024. The new Outlook for Windows only runs web add-ins deployed centrally, so Deck detects it and tells you so. Deck runs standalone; everything it finds stays on the machine and it sends nothing to Vediram.

See what a decade of installs left in your Office.

Install Deck on one machine and look. Then roll it out with the MSI and the ADMX templates.