They'll deal with their own shortcomings. They always do and I certainly wouldn't think twice about the update. Just watch what advice you take. It seems like there are alot of folks who are more concerned with posting a few hundred of the same old line in order to become one of those "evangelists". Make's one wonder just how literate some of the testers are. ::)
I’m hoping Alwil will rise to the occasion as they always do. I’m not questioning so much whether this problem will get fixed; it’s more of question of where it is in the list of priorities and whether the fix comes in the next build or not. I know I can always update to find out whether a particular bug has been eliminated or not, but that is something of a pain if the problem is still there after the update.
If I’m not too lazy when the new build comes out, I’ll probably take my chances.
please let us know when this problem with dell laptops are fixed so i can update my clients who have dell laptops
I have sent out an email for them not to do the upgrade until i hear in here that it is fixed.
Hey guys, I’ve been having this exact problem. Any advice on how to downgrade until something gets fixed? I’d rather not download from a site I don’t really know about-- Is there an official download somewhere on the Avast website?
I don’t believe Alwil makes old versions available on its website so I doubt you have any choice but to go to a general download site. FileHippo has always been a reputable site in my experience.
can we get an answer from AVAST please to see if they are working on a fix?
I would hate to move my clients to another AV who are on laptops- all of them have Dell
robin
Please stop telling people to downgrade. :(
That fixes nothing and only prolongs the amount of time that it takes to work out any missed bugs.
If downgrading (or going back to the previous stable version) is the only way to get a system functional again while bugs are being worked out, does a user really have any other choice? I don’t see how getting my system working again is going to slow down the Alwil developers. Speaking only for myself, if my system has been crippled by a new software update then I’m not really going to be interested in keeping it on my system and looking for any additional bugs.
do you seriously think I do this because I want have fun or whatever? No I do it becasue Avast 5.0.677 work well on their machine. Could you please give me the bug report?
I really hope you understand what my intention are when I tell people to downgrade to Avast 5.0.677.
[at] rwaters: Thanks for understanding what my intention are and I hope your machine is working.
[at] rwaters: Thanks for understanding what my intention are and I hope your machine is working.
Regards,
Tenko
I’m back up now; thanks for asking. I originally went back to the 5.0.677 version but there is a workaround using 5.1.864. If you uninstall (not disable) the Behavior Shield after updating to the new version, the wireless driver conflicts go away. But I can certainly understand not wanting to tell customers that they are operating with a workaround, so I would probably ask them to stay with the previous (stable) version for now.
I think you are only making one mistake: we are NOT beta testers.
We are end users that want their system to be stable.
We have just hit the “update program” button on the GUI, we haven’t signed anything saying “yeah we want a buggy program in order to find bugs related to drivers and other software”.
Of course, this merely hides the problem and will also hide any other legitimate Windows notifications. If you want to stay with the new 5.1.864 version instead of going back to the previous 5.0.677 version, I’d recommend re-enabling Windows notifications and uninstalling the new Behavior Shield instead.
Personaly I never use Avast! Support to report bugs. I do that here on the forum and notify an Avast! Developer about it. But sometimes it is easier to troubleshoot a bug in a one to one conversation, like I had with Petr in the past
If you want to stay with the new 5.1.864 version instead of going back to the previous 5.0.677 version, I'd recommend re-enabling Windows notifications and uninstalling the new Behavior Shield instead.
Disabling it is easier then you only need to reactivate it once the problem is solved.
You'll also need to make a change in the settings - status bar - uncheck behavior shield monitoring.
By doing that you will not get the warning that your system isn't secure which is usually displayed when one or more shield are off.
Bob most users are reporting that even if you disable the Behavior Shield the problems still remain. Apparently only a complete un-install of the Behavior Shield fixes it…
