Yes, mine is now showing ".42" after a reboot. It would be nice to know what the build update addresses. The full scan not showing progress bug is still there.
imo i am finding its light then 2016 myself in *most* cases. the one area where it seems slower for me is browsing but just by a tiny bit. otherwise everything else runs (for me at least) better then 2016
I assume you are basing this on how it "feels"? As it undoubtly uses more ram, cpu, etc than 2016 did without the new IDS module.
I don't think today's machine's should have any problems running any antivirus program seeing the amount of ram they come with. Avast is running fine even on my low end laptop and i am not noticing any slowdowns.I am not bothered about the ram i have enough to run avast.
RAM usage has very little impact on performance (unless your computer has not much RAM installed), but CPU and disk usage do, which is why I find most antiviruses are too heavy for my liking.
correct. i have more ram and cpu then ill ever use. so im talking about how the system responds. how things load, open, extract, browsing etc etc. i run tests to actually time things. i can 100% say according to actual times recorded the newer version is lighter in almost all ways. browsing is a bit slower. but its still equal to even eset or avira which also slow down browsing just a bit.
There's a major woops with the latest virus definitions for Avast. https://forum.avast.com/index.php?topic=197572.0 https://forum.avast.com/index.php?topic=197571.0
@Krusty, There is no need to read the links from Avast Forum as I already knew (re the fix) it from another (inner) source.
https://forum.avast.com/index.php?topic=197572.msg1371425#msg1371425 False positive VBS:Malware-gen detection in VPS 20170221-1 (22.2.2017) What happened? The VPS 20170221-1 contained an invalid script detection that resulted in a significant false positive across the Avast userbase. How did this happen? The Threat Labs team deployed a change in detection verification logic which moved the verification to an earlier stage of the detection release process. Multiple factors including deployment of new backend version caused this detection to bypass safety checks that are normally in place resulting in its release. What are we doing to fix this? We are implementing additional checks in the detection generation, detection validation and detection testing processes to prevent such errors in the future. On the mitigation side, Avast has the capability to stream updates to select detection containers. However this particular detection type is not included in the streaming updates at this time. We will enable streaming also for this detection type so we can remove these detections much faster in the future. Conclusion We apologise for the released detection and are working hard to prevent such occurrences in the future. - Avast Threat Labs
Hi all avast! Free Antivirus 17.2.2288 Beta https://forum.avast.com/index.php?topic=197813.0 With best Regards Mops21
Avast 17.2.2288 (Build 17.2.3419.0) available from the internal updater. https://forum.avast.com/index.php?topic=197955.0
Thanks Krusty! I manually updated to the new program version and rebooted as per its request, after booting up it alerted that a new version of avast! had been installed and tried to sneak google browser in with the continue radio button lol...Anyway I thought I'd just run the definitions update manually anyway and it began, "uploaded" the hmpa alert .dll and then gave your defs are already up to message date..What was that upload all about!
Sending Stats? The release notes say, "installation of web extensions on 64-bit version of Firefox", and sure AOS installed in FF 64-bit but it doesn't work. The icon is grey and clicking on it brings up a blank window.
Avast makes Windows in VirtualBox run slower than usual (Avast is installed in host only,no security software is installed in guest). Is this because the option "enable hardware-assisted virtualization". Is it safe to disable it?