FAQ: TBarCode Office Installation
TBarCode Office Listed as Inactive Application-Add-In
TBarCode Office Listed as Inactive Application-Add-In
Office 2010, 2013, 2016+
Download the latest service pack (SP) for your Office version: Download Office Updates (Service Packs). For instance, Office 2010 needs SP2 for the add-in to work correctly. Furthermore check your Office version for available updates: Install Office Updates.
After updating your Office installation you may need to re-activate the Add-In: How to: Re-enable an Add-in That Has Been Disabled
If the add-in already worked before and suddenly (e.g. after a Windows update) becomes inactive, try an Office Repair. In addition, make sure that you have the latest add-in version installed.
Office 2007
You need Service Pack 3 to be installed. You can download this service pack from Microsoft: Office 2007 Service Pack 3
In several cases a new installation combined with cleaning the VSTO cache may be required. The cache cleaning script/tool can be downloaded here. Uninstall, execute the cache cleaning, then install again.
After updating your Office installation you need to re-activate the Add-In: How to: Re-enable an Add-in That Has Been Disabled
If the add-in already worked before and suddenly (e.g. after a Windows update) becomes inactive, try an Office Repair.
VSTO Runtime
In some cases it may help to update the Visual Studio 2010 Tools for Office Runtime (VSTO Runtime). You can download the VSTO Runtime installer from the link below. If this update helped in your case, please give us feedback and let us know (thanks!).
Roaming User Profiles
There were problems reported with Roaming User Profiles (e. g. you see "Faulting module name: KERNELBASE.dll" in the event log). Temporarily switch to a local user profile to see if the problem is caused by the roaming profile. After new logon or reboot try to activate TBarCode Office in Options - Add-In - Manage COM Add-ins. If TBarCode is not listed there, try a complete reinstall.
Antivirus
If your antivirus solution is blocking specific files, there may be .NET runtime errors like "0xc0000005 - Unexpected parameters" during the startup of the add-in. This causes the add-in to be disabled.