What Kind of Problems (security ??) with 4.7.826

[UweS67]

Hi all
I was surprised, that only a few days after update to  Version 4.7.826, I need to update the program again (to 4.7.827).
May be there where some problems 
I didnt have any kind of problems (it seems ...) on my pc.
I dont hope with my security while surfing in the web or scanning E- mails. 
I received a rss newsfeed from alwil - software about the issue- but the link to the url doesnt work in my opera browser.
Sorry but I´m not able to read the very long thread about the version 4.7.826 (lack of time) - because of that I startet a new topic. 
Uwe

[DavidR]

Since you are obviously in a hurry the short answer is update to the latest version 4.7.827 there was nothing wrong with my installation of 4.7.826, but it did effect some with different OSes and system configurations.

[greenhatch]

Heh I was one of the apparent 'under 1%' of users affected by the duff .826 update, probably being too quick off the mark. I'm still wary of .827 to be honest. Still too many problems being posted in these forums.

[DavidR]

Where are these problems being posted on the forums that are related to 4.7.827 ?

Problem are problems are problems, this is after all a support forum, but where is the relationship with the problem being a result of having 4.7.827. Other than the fact that it's now what the majority are now using, 4 days after release (28/4/2006). With the auto updates all should be notified within 7 days, assuming people haven't set it to manual update).

So based on the 7 day spread of the program update cycle 3/7ths will still be using 4.7.826 so the very small percentage of people experiencing problems with 4.7.826 (you included) may yet to have updated to 4.7.827. Not the small percentage of those effected is any consolation when you are one of that figure, it is still a big issue.

[greenhatch]

David, I am back with .817, for a little while at least.

[DavidR]

Yes, but where are these problems you are talking about with 4.7.827 ?

[greenhatch]

Not specifically .827, but that update was necessitated by the .826 debacle, so I am (and I'd bet quite a few others)  back with .817, the link for which someone kindly provided at filehippo.com .

Yes, but where are these problems you are talking about with 4.7.827 ?

[igor]

The problem with .826 installer was clearly identified (and removed), so there's no need to downgrade to .817 - you're missing the other fixes done previously.

[DavidR]

There may well have been an issue for some with 4.7.826, but that has by all but been resolved based on the feed back on these forums. Taking a backward step is fine if there is no other solution but not updating to a version that is supposed to resolve the issues of 826 when released  isn't helping either you or Alwil in ensuring that 827 has resolved the issues people had.

If problems are experienced with 827 that are reported through the forums, etc. then the Alwil team will react promptly as they have with 826 and this will help everyone. However, if people don't try it and any issues aren't reported then Alwil are in the dark, if the worst comes to the worst after trying it you have always got file hippo.

[Vlk]

Here's the official statement about the 4.7.826 release: http://www.avast.com/eng/4-7-826-problems.html . It was out there only for about 16 hours, so a vast majority of our users didn't see it at all.

[greenhatch]

I will update the program, of course, say at the weekend; just not within the first few hours any more, that was my error before. I am not computer savvy enough to be able to ride out any initial problems. So I intend to always wait a few days in future; it's not as if program updates are very often.

[alanrf]

greenhatch,

not for the first time I have to agree with you.

Honestly, unless you are someone who is really happy about, has the time to deal with and is fairly confident about dealing with difficult system issues then I do think it is better to let others test the waters first.

We users of avast have not had to deal with any really significant issues in beta releases since I started to use the product, that does not mean I have not complained (or raised issues I could not go back and reproduce  - 826 was a case in point).   However, the folks I support leave me to dip my toe in first with the beta releases before they wait for the green update flag from avast. 

I have to say that the 826 issues were fairly minor compared to some new release issues I've seen in other products in my time and the avast team is more open and up front in communicating with the user community than many other development  teams - one of the greatest strengths of this product.

That being said, the folks I support and I are now on 827 and working away just fine.