Open MalwareTips from your Home Screen or desktop. Follow discussions, find answers and pick up where you left off.
If you cannot find an install option, update your browser or use its bookmark option to keep MalwareTips close.
After installation, open the app and sign in. Enable push notifications in Preferences if you want alerts. On iPhone and iPad, push requires a Home Screen web app and iOS or iPadOS 16.4 or later.
Sign in to manage notificationsInstallation is optional. Your notification settings stay under your control.
This option exists on CCAV. The CCAV gives alerts before the unknown files trying to run.Can you set Comodo autosandbox to alert for action, instead of automatically sandboxing the process?
If so, is this a good way to deal with the problem of processes that get mistakenly sandboxed?
I agree with your approach all the way. I love not having to make decisions.Shmu- When something is about to be sandboxed having Comodo ask the user every time to Allow/Deny would be a VERY bad idea as they would be reducing protection to a coin flip. Essentially this would be equivalent to an antivirus asking the user to Run/Don't Run every time a trojan is detected.
Now, what can you do when an application is sandboxed and you are absolutely positive it is good (also, the most common reason for something valid to be sandboxed is that the developer didn't sign something):
1). At the initial sandbox alert, click on the Do Not Sandbox Again link on the popup. Or,
2). if you missed doing the above, run the application again and just go into Sandboxed processes from the main GUI, look for the main application and right click it and change it to Trusted. Or,
3). Go into Advanced settings/Security settings/File Rating/File List. From there tou can find the process you want to make Trusted and change it right there.
I tried that, and the problem processes are rated as trusted, but they still fall into autosandbox.Try this then-
Go into the File List Window as I noted in my last post- when that screen comes up you'll notice that stuff can be sorted by File Path, Company, First Observed, and File Rating.
Click on the File rating and you'll note things now will be categorized by Trusted, Unrecognized, and malicious. Look for the process you want to make Trusted (which will probably be under Unrecognized), click on the link and make the change right there.
This may seem like a pain to go through, but it is (in my opinion, which is identical to the Word of God) very nice and very safe.
Can you set Comodo autosandbox to alert for action, instead of automatically sandboxing the process?
If so, is this a good way to deal with the problem of processes that get mistakenly sandboxed?
If I install Kaspersky Internet Security, they get suppressed and don't start at all -- unless I run KIS in interactive mode, and make an allow rule for them.
both files are 100% clean according to VT, they have been on my system as long as I can remember, and they are signed by intel and microsoft.KIS does not suppress processes unless moved to Application Control > Untrusted\Blocked.
If the Intel processes are those installed by the OEM partition or your driver installer, then they're safe. In other words, if the files have been on your system from day-one of having your brand new, out-of-the-box system then their safe.
It's simple enough to certify the files clean.
both files are 100% clean according to VT, they have been on my system as long as I can remember, and they are signed by intel and microsoft.
but Kaspersky and COMODO don't like them, can't figure out why.
maybe this is where I am going wrong: I don't see these auto-sandbox rules that you are talking about, for the problem files. I see only the ignore rules that I created to override the autosandbox function.At the same time, you also have to delete the auto-sandbox rule created.
maybe this is where I am going wrong: I don't see these auto-sandbox rules that you are talking about, for the problem files. I see only the ignore rules that I created to override the autosandbox function.
COMODO file rating gives these files trusted status, so the issue is not there.
thanks for help. my ignore rules are higher in the list than the global autosandbox rule.The order of the rules in the list is the order in which they are applied; top of list - first\bottom of list - last.
So, if your ignore rules are at the bottom of the list then they will be the last to be enforced.
If that's not it, then I'd do a clean install of Windows and start from scratch.
If you are playing with a lot of softs - which I think you are - installing\uninstalling - then you are only asking for problems with CIS and KIS; both require clean installs to work properly. Remnants of other security softs will cause malfunctions or mis-behavior with both CIS and KIS.
I've never seen an Intel driver cause problems with security softs; Nvidia and AMD I've seen auto-sandboxed. Never seen a single problem with KIS.
okay, it turns out that Windows was failing in its attempts to update my Intel graphics driver. I downloaded the driver installer directly from Intel, and after booting into safe mode, I was finally successful in installing it.The order of the rules in the list is the order in which they are applied; top of list - first\bottom of list - last.
So, if your ignore rules are at the bottom of the list then they will be the last to be enforced.
If that's not it, then I'd do a clean install of Windows and start from scratch.
If you are playing with a lot of softs - which I think you are - installing\uninstalling - then you are only asking for problems with CIS and KIS; both require clean installs to work properly. Remnants of other security softs will cause malfunctions or mis-behavior with both CIS and KIS.
I've never seen an Intel driver cause problems with security softs; Nvidia and AMD I've seen auto-sandboxed. Never seen a single problem with KIS.
Members and guests who viewed this thread in the last 5 minutes
We use essential cookies to make this site work, and optional cookies to enhance your experience.