Error: The Add-in cannot be loaded by Outlook
Posted by Dave Mellors | Filed under Fixes to problems
After uninstalling Symantec Anti-virus I found that when I started Outlook 2007 it came up with the following error:
The Add-in “Symantec AntiVirus 10.1″ (c:\program files(x86)\Symantec Antivirus\vpnsece4.dll) cannot be loaded by Outlook. Please contact the Add-in manufacturer for an update. If no update is available please uninstall the Add-in.
The problem was that the addin didn’t appear in Tool->Trust Center->Add-ins so I couldn’t uninstall it from there.
Fortunately, deleting the file extend.dat from c:\users\<User Name>\AppData\Local\Microsoft\Outlook and restarting Outlook done the trick. That was obvious – NOT!!
NOTE: I am running Vista x64 so if your running a different version of Windows the file is likely to be located elsewhere. Possibly C:\Documents and Settings\<User Name>\Local Settings\Application Data\Microsoft\Outlook
August 4th, 2008 at 2:17 am
worked for me too.
have you experienced any negative side effects after deleteing?
so far so good for me.
THANKS!
August 4th, 2008 at 5:48 am
No side effects. The extend.dat file contains cache information and just gets rebuilt when you start Outlook.
Thanks for letting me know the post helped you.
August 12th, 2008 at 3:56 pm
Did a Google search for this add-in issue and your post about deleting the extend.dat file did the trick for my 25 users.
Thanks!
Mark
Mark Cefaly
Manager, Information Services
Maryland Crime Victims’ Resource Center
August 19th, 2008 at 10:18 pm
It did the work. No negtive side effect. Thanks a lot
September 15th, 2008 at 3:34 pm
Worked for me too.
Many thanks
September 16th, 2008 at 8:19 pm
Thanks! your post helped me as well get from that annoying message….
Take care
Ronen
October 8th, 2008 at 4:49 am
Typical of Symantec uninstalls. You’d almost think they didn’t want to make it easy for you to migrate to a different AV product
October 11th, 2008 at 5:25 am
Worked for me too in XP
October 29th, 2008 at 9:19 pm
Worked for me, too… with F-Prot
November 20th, 2008 at 10:54 pm
Thanks a lot. I was using Outlook 2007 in XP and just move to Vista, thus the interface changes make me confused. Your post is really helpful.
January 7th, 2009 at 10:24 pm
Hey thanks alot. I had a different addin failing after migrating outlook for my wife onto a new build. Emon.dll from nod32 was the culprit for me. Extend.dat is not an obvious solution at all.
July 1st, 2010 at 11:44 pm
For W7 x64 with Outlook 2007, you do not delete the extend.dat file. That may not solve the problem anyway.
Instead, to the following after you open Outlook:
1. Select ‘Help’ from the menu bar.
2. Select ‘Privacy Options’.
3. Select ‘Add-ins’
4. At the bottom of the page use the drop down menu to change ‘COM Add-ins’ to ‘Exchange Client Extensions’
5. Uncheck ‘ESET Outlook Plugin’ and click ‘OK’
6. ***Restart Outlook.
No more ESET error message.
July 20th, 2010 at 11:50 pm
There you go – Google is your friend!
I didn’t see this article and after using registry scanning and other utils to remove NOD32 from a migrated system so I ran Process Monitor from http://www.sysinternals.com. Sure enough, just prior to trying to read a non-existant path Outlook checks a file “C:\Users\XXX\AppData\Local\Microsoft\Outlook\extend.dat”.
I renamed it extend.data and restarted Outlook. VIOLA! It re-creates extend.dat and the problem is solved!
Not very obvious at all so I looked to see if I could help others solve this glitch. Beat me to the punch!
May 10th, 2011 at 9:55 pm
Thanks B_Solid. You solved my problem as the Eset site told me to look for ……extend.dat which couldn’t be found.