Since upgrade to 8.1 and reinstall of Comodo at the time around Oct 20, everytime CIS runs a full scan and perhaps at other times, such as quick scans, SAS Pro’s Core Service Process runs at 13-14%, bringing my computer to a near halt. Stopping that Core process solves it for the moment. I’ve reported it to SAS, but am wondering if there’s something about CIS causing it, or in the configuration of CIS that needs adjusting. I’ve got the main SAS Pro files excepted in CIS, but that doesn’t seem to be solve it. Anything else to try in CIS? Thanks,
Try adding the CIS folders to the exclusions of SAS Pro and the SAS Pro folders to the AV exclusions of CIS.
When that is not enough add the SAS Pro folders to the Exceptions of Detect shellcode injections.
Let us know if that helps or not.
After several minutes of scanning, SAS Core process kicked in at the 11-12.8% level. I paused the scan and added the SAS folder under Detect shellcode injections, but that hasn’t changed it. So far, there isn’t any computer sluggishness, though there was some briefly a couple of minutes ago. Perhaps 13.0% cpu in Task Mgr is the threshhold.
Update: I spoke too soon. The computer started feeling jerky, so I checked Task Mgr and SAS Core is running in the 13-14% range.
As a rule of thumb we do not recommend to run two security solutions of the same kind at the same time as there is a fair change they may interact adversely. In this case of problems we advice to choose to either use the AV of CIS or SAS to check for malware in the background.
Adding a second program for detection only brings very limited extra security. A good security set up is layered using various techniques to protect the computer. CIS has a proactive strategy with the Sandbox/(HIPS) as a first line of defense.
First of all, I didn’t have this problem prior to going from Win 8.0 to 8.1. Whatever is going on here, I can’t emphasize that enough.
For some reason, CIS didn’t make it whole through the update for some reason and had to be reinstalled. Why I was never clear about (SAS Pro had no problem). Don’t know if that has anything at all to do with the problem I’m encountering.
Second, running a couple of security apps has long been quite common and sometimes commented on as a not a bad idea in computer newsletters (e.g., Windows Secrets). Even SAS developers have told me they run Comodo as well on their own computers (and who know, perhaps if truth be told some at Comodo are too). In general, I’ve found one program picks up things another doesn’t, and vice versa. Of course, doing so makes it harder and more costly for security program companies to pick apart problems that arise, such as in this case.
Installing of a service pack is a significant step and is big enough to break things that worked before.
For some reason, CIS didn't make it whole through the update for some reason and had to be reinstalled. Why I was never clear about (SAS Pro had no problem). Don't know if that has anything at all to do with the problem I'm encountering.If the problem still happened after the reinstall then it was not related to the upgrade to W8.1.
Second, running a couple of security apps has long been quite common and sometimes commented on as a not a bad idea in computer newsletters (e.g., Windows Secrets).Our advice is a rule of thumb; it is possible to have more than one AV's at the same time. I did that years ago with AV's of Norton and AVG. Im those days I once tried I think NOD32 or Avast with Norton and they did not work together.
Around here we hold the view it is best to use a layered approach with Firewall, HIPS and or sandbox, AV. I prefer a one stop shop solution like CIS but you can mix and use various products delivering the various layers.
Even SAS developers have told me they run Comodo as well on their own computers (and who know, perhaps if truth be told some at Comodo are too).If a combination for whatever reason breaks it breaks and when a clean install does not bring solution it is a bug and as such worth an investigation and a bug report. :-\
In general, I've found one program picks up things another doesn't, and vice versa. Of course, doing so makes it harder and more costly for security program companies to pick apart problems that arise, such as in this case.Still I prefer a layered approach with a proactive HIPS/Sandbox solution empowering the user to get alerted for each unknown program to run or have it run on a leash. That way you stay ahead of the curve. Detection always runs after the facts.