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.
and why not installing proactive defence?
Proactive defense is a preset in both Comodo Internet Security (which has an offline antivirus on top) and the Firewall (which only has a cloud antivirus, making it most compatible to an AV product of your choice, with better signatures than Comodo Internet Security).and why not installing proactive defence?
that sounds interesting. could you elaborate on that technical error? Do you mean a user error, or a malfunction in COMODO defense?I've tested Comodo Internet Security for nearly a month now (without the Proactive Preset) and only due to a sudden (and not repeatable) technical error I had a ransomware not being sandboxed.
A malfunction related to my OS I'd say. When I started testing CIS, I regularly had BSODs, which I thought (and might be) related to conflicts of malware being sandboxed and performing their actions in there. However, since I had to refresh (kinda reinstall) my OS due to a beta test of CIS 10, which I couldn't get uninstalled, I never had any BSOD related to CIS again. I think there was something wrong on my base system (ShadowDefender protected) which you couldn't know by normal usage, but by chance due to CIS testing. The infection happened because a ransomware was not sandboxed, UAC accepted, encryption done.that sounds interesting. could you elaborate on that technical error? Do you mean a user error, or a malfunction in COMODO defense?
thanks.A malfunction related to my OS I'd say. When I started testing CIS, I regularly had BSODs, which I thought (and might be) related to conflicts of malware being sandboxed and performing their actions in there. However, since I had to refresh (kinda reinstall) my OS due to a beta test of CIS 10, which I couldn't get uninstalled, I never had any BSOD related to CIS again. I think there was something wrong on my base system (ShadowDefender protected) which you couldn't know by normal usage, but by chance due to CIS testing. The infection happened because a ransomware was not sandboxed, UAC accepted, encryption done.
However, I retried on the same system before the refresh, and did not have the infection again (sandboxed before and after UAC). I have tested many malware since then, everything unknown got sandboxed, system was clean every time (encryption inside sandbox), only dropped malware was detected by 2nd opinion scan when using Macro Viruses, because the Word file was not suspected malicious. However, the dropped payload was indeed sandboxed when triggered.
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.