Outlook integration

I'm running NOD32 on three machines in our home office. I just realized that, on one of them, there is no integration of ESET into the Outlook 2003 context menu (i.e. there's no way to re-scan a selected message in Outlook). NOD32 is identically configured on all three machines. Uninstalling and reinstalling the a/v on the problem machine does not correct the issue. The most notable difference of this particular machine is that it's a laptop with Embassy Trust Suite installed. Has anyone else encountered this issue?

 

Hello layman,

Please try the following Knowledgebase procedure that focuses on correcting issues with Outlook integration:
http://kb.eset.com/esetkb/index?page=content&id=SOLN767

Thank you,
Richard

 

Does the ESET toolbar appear in Outlook at all?

 

No. It used to be there on that machine, but went missing at some point.

 

Try the following:
1, disable EAV integration with MS Outlook
2, restart MS Outlook
3, close MS Outlook and enable integration again
4, start MS Outlook

 

SP 3 is already installed and Office is up-to-date. Deleting extend.dat doesn't help.

 

No change.

 

Could you try restarting the computer before trying my suggestion? It wouldn't work if Outlook is closed but the process outlook.exe still running in the background for some reason.

Should the problem persist, try the following:
1, in MS Outlook, go to Tools->Other->Advanced Options->Add-ins Manager…” and make sure the ESET plugin is checked.
2, with MS Outlook closed, disable EAV integration with MS Outlook
3, delete the file "c:\Documents and Settings\%USERNAME%\Local Settings Application Data\Microsoft\Outlook\extend.dat"
4, enable EAV integration with MS Outlook
5, start MS Outlook

 

I've done all this with no effect. Checked Process Explorer to make doubly sure outlook.exe was not running.

 

Perhaps I should mention that NOD32 has always behaved rather differently on this machine than on our other two. During sign-on after reboot, the NOD32 faceplate appears for approximately 5 minutes during which Process Explorer shows nothing much happening. The machine isn't completely stalled, but it's not normally operational either. After this long pause, ekrn.exe finally appears and operation becomes more normal. This slow start-up has been a nuisance.