Direct Access wrongly detected as a keylogger by Spy Sweeper
I received a message from a customer telling me Direct Access was identified as a key-logger by Spy Sweeper.
Installing the trial version confirmed that as the following screen appeared. Apparently, even with Spy Sweeper active, Direct Access continues to work properly: sometimes a window appears telling me about the “threat”. That’s not the best welcome mat for a prospect who’s just installed the new software!
I cannot blame Spy Sweeper for that: Direct Access works like a key logger since it needs to detect which keys are pressed to recognize the user commands. I tried to contact Webroot about the problem but the case has to be opened by a customer and, unfortunately, it looks like mine is not willing to go through their loops to solve this issue.
If you happen to be a Spy Sweeper customer, please write them about Direct Access so that they can update their definitions.
3 Comments so far
Leave a reply
To be fair, Spy Sweeper 5 flags almost everything as a key-logger. I’ve had two builds issued that promise to fix this up and so far nothing has changed. This is one shield that I keep “off” at all times in Spy Sweeper. Having it activated leads to just about every M$ service running on my machine being flagged. There is as yet no means for the end to user to set Spy Sweeper to ignore trusted services and applications.
Yes, that’s the reason I’m not running it on my PC. It constantly pops up alerts and warnings. I noticed that, by default, Spy Sweeper starts with the keylogger detection set to false and you can’t tell to white list a program.
I suppose the same problems are present with other software that detect keyloggers. I’ll have to check.
I can’t figure out why everyone doesn’t use Grisoft.com’s AVG - even the free edition does a better job than Spysweeper (says happy client of 6 years)