Forum Discussion
Outlook crashing when sorting emails
I've been advised by Symantec support to disable Outlook scanner add-in via policies. Also had to make additional setting so clients won't show an error about the disabled scanner. Now Outlook is not crashing anymore. Symantec reasoning was that this scanner is not needed as we already have main Auto-Protect module scanning everything, also the temp files when attachment is opened or saved.
Yeah.. Just updated one PC to the latest SEP version (14.2). Same issue. Not sure what to do next. There is a way to uninstall Outlook scanner manually via Programs and Features > Modify. But not an option to do this centrally for all the clients, that i know of.
I've been advised by Symantec support to disable Outlook scanner add-in via policies. Also had to make additional setting so clients won't show an error about the disabled scanner. Now Outlook is not crashing anymore. Symantec reasoning was that this scanner is not needed as we already have main Auto-Protect module scanning everything, also the temp files when attachment is opened or saved.
It wasn't a decision to enable it to do something along side the EOP. It was just there for many years and this scanner is always a part of client protection package, by default. Symantec server has been setup maybe 7+ years ago when we were still on some local POP3 mail, so i actually didn't remember there were additional scanners like Lotus Notes, etc. until this issue came out. Although i can see some companies still wanting to use the scanner in case EOP doesn't catch something (who said EOP is 100% fail proof?) and if they want for a malicious attachment to get caught without it being opened by a user and then caught by the AV file system scanner.
Why would you have any security tools scanning Outlook anyway? Is there something that Symantec does that you cannot accomplish with EOP?
I've had exactly the same issue with my personal machine while testing 1808. Likewise, disabling the Symantec Endpoint Protection add-in within Outlook immediately resolved the issue.
