Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Vlk on November 27, 2008, 11:51:35 AM
-
Howdy,
we have released yet another program update (4.8.1296) - probably the last one in this series of updates.
Changes are minor, but somewhat important for us.
The update size (if coming from v1290) should be fairly small.
Thanks
Vlk
-
Hiļ¼sir! I wonder whether the next version will be 5.0? ???
from China......
Welcome to the forum! :)
Please search before you ask something, many things have been discussed before!
Vlk said Avast 5 will be released sometime in H1 (first half of 2009)
http://forum.avast.com/index.php?topic=39327.msg330271#msg330271
Edit: Sorry, now I see that you ask for IF the next update will be 5.0, and not WHEN it will be released! I have to read better next time :)
-
I installed the update on my XP Pro system.
Reboot required.
-
Installed...
-
Installed on 2 XP and 1 Vista computers.
-
The below quote is from the revision history (http://avast.com/eng/avast-4-home_pro-revision-history.html) is for lazy people. ;)
Version 4.8.1296
November 26, 2008
* minor improvements in some unpackers
* improvements in the false positive submission system
* speed optimization in kernel-mode components
* XML scan reports now generated in UTF-8 format (allow for non-Latin characters)
-
Does this updated address the problems it has with Online Armor??
-
Installed here on Vista Ultimate.
-
updated and again - like expected from avast! - no problems! ;)
yours
onlysomeone
-
I installed the update on my XP Pro system.
Reboot required.
If that is a question rather than a statement, then yes after a program update a reboot is normally required to effect any change to running drivers, etc. So considering this update has a mod to kernel-mode components a reboot would be required.
Does this updated address the problems it has with Online Armor??
Isn't that a problem with OA interacting with the web shield or blocking avast processes after an avast update rather than avast causing a problem with OA. There is a recent update for OA which is supposed to resolve its interaction with the web shield.
If not it should be continued outside this topic.
-
Does this updated address the problems it has with Online Armor??
Isn't that a problem with OA interacting with the web shield or blocking avast processes after an avast update rather than avast causing a problem with OA. There is a recent update for OA which is supposed to resolve its interaction with the web shield.
If not it should be continued outside this topic.
I believe I had changed to OA and then read about the problems both softwares were having AFTER the Avast update, both here and in OA forum. No reason to get all defensive David, seems both should attempt to work together instead of apart and blaming each other like 1st graders. You yourself used the "after an avast update" which wold indicate that Avast was last. Both are great software packages
-
I'm not being defensive, I'm just an avast user like yourself with no affiliation or sway over Alwil software or OA developers. I was simply pointing out that there has been an OA update which is supposed to resolve an issue it had with the web shield.
There are also many topics relating to how to ensure OA allows avast's updated on the reboot, such as putting it into learning mode (was one suggestion), so the potential solutions are out there, to stop OA blocking changed components of avast without any pop-up notification on a changed component, so this wouldn't just happen with avast but other program updates if they become active on boot or connect to the internet, etc.
Which is why I suggested continuing in another topic so as not to drive this one off-topic not an attempt to silence you or be defensive.
-
Couple of things I am seeing with the avast! 1296 and the latest OA beta. I have been running with OA mail shield and web shield off and avast! mail shield off because of issues with OA/avast!
1) After reboot, I found that the OA rule to allow ashwebsv.exe had changed to "block" untouched by human hands, so only 2 providers were running. But changed it back to allow, and the avast! web shield provider restarted without incident. Otherwise no issues at reboot.
2) Mentioning changes to kernel mode components always gets my attention, so I turned the OA web shield back on-used to cause Opera to crash consistently when both are running. Will report back if I see another crash, but so far nothing. Did not work with same OA and avast!1290. Problem as early as avast! 1229 and early OA Vista betas.
3) If I don't see another Opera crash, will try the email components and Stunnel again.
Will post the same info on the OA forum.
-
I believe I had changed to OA and then read about the problems both softwares were having AFTER the Avast update, both here and in OA forum. No reason to get all defensive David, seems both should attempt to work together instead of apart and blaming each other like 1st graders. You yourself used the "after an avast update" which wold indicate that Avast was last. Both are great software packages
Sounds like a general firewall/HIPS problem rather than an OA problem to me. Any firewall/HIPS should block new versions of a program until allowed by the user. OA has a whitelist with known, trusted applications. Maybe some updates to the list were missing?
-
Yes they should block changed processes but to do so without notifying the user leaves them totally in the dark other than they now have a problem. The user isn't getting the opportunity to allow the changed elements as they aren't notified.
My firewall Outpost Pro notifies me of changed elements with a pop-up and I can allow them, it doesn't just block and say nothing.
-
Yes they should block changed processes but to do so without notifying the user leaves them totally in the dark other than they now have a problem. The user isn't getting the opportunity to allow the changed elements as they aren't notified.
My firewall Outpost Pro notifies me of changed elements with a pop-up and I can allow them, it doesn't just block and say nothing.
Probably a result of the whitelist design, which I hate. It's impossible to have a 100% correct list at all times.
Should be on the Avast list of known issues, if there is such a thing.
I have never been impressed by OA. I'm quite impressed by Avast.
-
we have released yet another program update (4.8.1296)
Installed... :)
-
Just downloaded / installed 4.8.1296 on WinXP Media-ctr. All normal :)
-
Updated Computer #2 (Same avast!/OA configuration, but Vista Home Premium) and avast! web shield again did not start for some reason at boot. Terminate and restart the Provider fixed it. This time OA created duplicater entries for the new avast! processes, not just a blocked web shield. Turned on OA web shield again here too to see if Opera crashes again.
-
Installed and so far all ok.
-
i hope this fixed the false positive issue when false rootkit was found on HDD inside some binary and Avast! said that rootkit is memory and boot scan must be done which scared off poor non IT skilled users :)