GSA SER & ESET Smart Security
I recently changed from using ESET NOD32 anti-virus to ESET Smart Security which is their security suite product that incorporates NOD32. Ever since I've changed the ESET scanning process ekrn.exe has high CPU usage and SER seems to take much more CPU resources to do the same tasks.
Previously when using NOD32 I added the SER program files and user profile directories to the exclusion list which worked in terms of making it play nice with NOD32 but doing this with Smart Security doesn't work.
So just wondering a couple of things:
Does anyone else have the same issue and have you managed to remedy it?
Are there only 2 folders that GSA SER uses that I should add to the exclusions list?
If I can't fix the issue I'll go back to NOD32 but maybe there's a way to make them play nice.
Comments
ESET is the one to blame. It's a horrible virus scanner as so many others. Do yourself a favour and get something that:
I always recommend AVAST, Kaspersky and AVG.
Virus checkers in general are a problem today. They give users a wrong feeling of security. Almost anyone can create a torjan/virus not being detected by all scanners and infect your PC. If someone wants to, he always can. You don't have to be a smart coder anymore.
But some scanners are still more evil like the mentioned one. They detect everything as virus that was e.g. compiled with a certain compiler just because they are unable to create proper signatures for the virus. It's getting worse all the time.