I have a problem with Defense+ and Setpoint.exe (the executable file for Logitech Keyboard and Mouse SetPoint software). Defense+ is detecting it and blocking it every few seconds filling the log of Defense events completely. I have added the executable to my safe list, but it still appears here. Under the “flags” column, it reads “Acess Memory”.
It took me a while to figure it out, since the instructions to actually get there were a bit different in the latest version of CIS (5.0)
I tried what you suggested but I still have these spam entries in my Defense+ event log. I’m attaching a few screenshots of what I did modify, trying to follow the instructions you provided. Most likely, I didn’t do something correctly.
I think I finally got it. Here is a screenshot of the options I followed / modified. The way I did it before was totally wrong.
The events in Defense+ concerning Logitech SetPoint stopped spamming the log.
I cleared the Defense+ event log to give it a fresh start, too bad CIS main screen still says “Defense+ has blocked 414 intrusion(s) so far”, (400 of which were caused by SetPoint :P) and it didn’t reset accordingly. I know its a minor cosmetic thing, and it’s supposed to show the number of detections over the product life, but, anyways… hehe.
I’m very sorry pushing the Thread but is there a way to solve the problem more …gracefully?
The solution from cool1007 worked for me very well. :-TU
But what exactly is happening here? Before the update to V5 everything I recognized was a direct memory-inter-access issue. But in V5 I have to grant the memory-access from SetPoint to the Comodo-Core? Is this right?
So if this is the case, there may have to be a mail to Logitech so that they can fix their driver and stop accessing every process that is running?