Discussion in 'other anti-malware software' started by Emre TINAZTEPE, Jan 20, 2015.
I think this test was done without Pandora activated. Default settings were used.
Taking into account that is a second opinion AV it did quite well. 1st against its competitors and 6th against the av's
It was a reply to your stament not to you. I really don't care your opinion.
This is an open forum if you don't like nobody is forcing you to stay, you are in the troll list of many people already
Zemana AntiMalware 126.96.36.199 Beta
Friday, September 9, 2016 5:48 PM
Added new experimental signatures
At the moment I seem to be having difficulty connecting to Zemana from GUI.
Will try later.
I had the same connectivity problem. It's okay now.
Zemana AntiLogger - The #1 Privacy Protection Software
Zemana AntiMalware 188.8.131.52 Beta
Wednesday, September 21, 2016 1:12 PM
Minor improvements and fixes.
With best Regards
winzip64.exe = scan FAILED
WinZip Folder in Program Files scanned: Again scan failed for many files.
I am also seeing some "Failed" items during a deep scan.
Report is the same as above, as is the image - but with different .exe files in this case.
What does "Failed" actually mean for the items in question ?
"Failed" is happening for me too using Zemana Antilogger 2. Seems to happen for me with big files.
I started the portable installer from the downloads folder, and I got a popup from VS, which I allowed. This updated ZAM portable to v184.108.40.206.
I ran my usual smart scan after the update, and it completed, but I also got the "Failed" message on one item in my downloads folder.
Getting many "failed" items with both stable and beta versions
I got the "fail" today too on one of the results after scan. Using latest stable version 220.127.116.11.
I just did another test run - no problems with Smart Scan but with Deep Scan some different items have now "Failed"
(the same happens with subsequent Deep scans - showing different Failed items)
Yes! Confirmed here! Deep scan gives a lot of "fails". I think their cloud server is at fault here. I don't think it can verify wether files are good or bad in some cases and then show "fail" instead.
It was the cloud server that I had issues with here
Obviously a bug, use the send feedback button and let the developers know
Reported since yesterday.
Scanned once again (few minutes ago), seems that "scan Failed" bug solved (at least for me).
Appears fixed here now also - maybe the server was choking temporarily or they tweaked something at their end.