So you don't know if Sophos removed the file or not. Sophos shows an alert when it finds a bad file, but there's nothing you can do about it. In the meantime, I deleted Sophos Home while it is also free, it has become harder to use in recent versions and lacks the kind of control Avira offers. My conclusion is to schedule a quick scan daily and to do a deep scan manually, less often and only when I can walk away from the computer for a few hours. You can inspect individual quarantined files if you are uncertain if you want to remove them. There is a button to select all the quarantined files and another to delete them, so the process was painless.
Nevertheless, the deep scan found 40-odd bad files that the quick scan overlooked, though they were all in e-mail in the junk folder and were thus non-threatening. The deep scan took two and-a-half hours and slowed down some other apps dramatically. The quick scan ran efficiently, took only a few minutes and did not affect system performance. However, I found there is a significant difference in performance between a quick scan and a deep scan of my computer. You can schedule a scan, set the scan type and see any quarantined files a scan finds. Ah uh, heh, I *always* want to know if these programs have an installer that actually uninstalls everything.Īvira is very easy to use. ("Crushes the threat of Mac malware!")Īvira seems like it's OK, but the lack of recent positive reviews makes me wary. Malwarebytes for Mac seems fine as far as it goes (trapping existing infections of common malware) but does it do anything beyond that? The marketing hype is insufferable. Intego Virus Scanner also seems to work well, is free, and has no real time feature. Feels like a minefield.ĬlamXAV 3 works well for me, and though it isn't free, I've used it for over a decade and am happy to support Mark Allan. There are so many entries in the Mac AV "space, it's almost impossible to sort through them all. The more detail you can provide the better. I'll just add a note here to thank all the reviewers. German companies are excused for occasional improper English.
"If Avira Antivirus for Mac is already installed on a computer that is being upgraded to macOS 10.14 "Mojave," the first time the program is run (after the macOS upgrade) the user will be asked to supply the administrator password.ĭear MacUpdate: Please change "Will Avira Antivirus work good on macOS 10.13.4?" to "Will Avira Antivirus work well on macOS 10.13.4?" "Good" is not an adverb, it's an adjective. I'm going to guess that what you mean to say is, The third bullet point is incomprehensible. (Right? If not, please define "user permissions." And how do you know that "later" installations will also require extended setup.?They haven't even been released in beta.) Installation on macOS10.14 (or later) has an extended setup process, which requires administrator permissions. I note that they are the same as here:Īvira Antivirus for Mac 3.10.4 is compatible with macOS 10.14 "Mojave." Also advising users to employ a third-party program to troubleshoot such a basic problem is not the best sign.The 3.10.4 Improvements as written above are poorly worded English.
Avira antivirus for mac review how to#
Bullguard antivirus for Mac, at the very least, should’ve been able to tell me where the troublesome files were or how to remove them. But a lot of these problems could’ve been avoided. The files may or may not have been a threat depending on which window you choose to believe. This was ultimately a very simple problem with some basic but annoying adware stuck on the machine.
Avira antivirus for mac review full#
Meanwhile, Bullguard’s customer service was offering very basic advice such as disabling browser plugins and running more full scans. The actual resolution came about because I knew what to look for and where thanks to EtreCheck. Why it continued to flag it as problematic, I don’t know.ĭuring this whole ordeal, Bullguard support wasn’t much help other than advising me to use EtreCheck. Trouble was, it was already in the antivirus’ quarantine section. After another few scans and some of my own troubleshooting I was able to find the problematic file that Bullguard kept flagging.
0 kommentar(er)
