Updates: Oct. 31, 2012 - avast! v7.0.1474

As a reminder, users can control how and if they want avast to update itself:   Open the avast user interface (click on the orange "a"-ball in your system tray), and toward the upper-right select SETTINGS, then on the left-hand side select the UPDATES tab.

Avast offers two categories of updates.   the first is ENGINE AND VIRUS DEFINITIONS, and I strongly advocate this is be set to AUTOMATIC Update.

the second is for the PROGRAM itself.   the choice here is really up to the user.

AUTOMATIC update (for program) will automatically install the latest program version, without having to ask you for additional permission.   So, for example, you would automatically receive the 1474 build that Joe is writing about in this thread.

ASK WHEN AN UPDATE IS AVAILABLE will monitor avast's server for the release of new program updates, and will advise you whenever one is found, asking your permission to proceed with it.

MANUAL update leaves everything in the users control.   It will not even check for new updates.

I have chosen to set my PROGRAM updates to MANUAL.   For I have chosen not to update since build 1416 (released in March).   My primary reason for keeping the old build is that I like the way the auto-sandbox works in that build.   It functions very differently in both prior AND newer builds.   If you don't use, or are not concerned about, the auto-sandbox, then this won't be a factor in your decision whether or not to update avast's program.

While I like and use avast, I believe they're trying to do too-much-too-fast, which results in them releasing a new build only to find numerous faults from its many users.   Just take a look at the avast forum to see what's happening:  http://forum.avast.com/index.php?board=2.0

Therefore, I strongly recommend that users who prefer to keep avast up-to-date adjust their PROGRAM update setting to "ASK when an update is available".   This gives you time to check-out the avast forum, to see what's being reported there.   I believe Hernan likewise advises avast users to wait at least a week before updating the program, just to make sure things seem calm enough [it seems that every time avast offers a "significant" update, it has to follow it with one or two "service" updates a week or two later].   http://www.avast.com/release-history

I agree with most of what ky says.

I allow no programs to auto-update. Not my browsers, not my security software, not Windows patches, etc. I generally wait for a few days to see what problems are reported with new versions before I manually update. I'm sure there are exceptions to this, to adress certain critical patches, but not as a rule.

I also look at the changelog to see if the new version adresses any problems I might be having. In this latest version of avast!, for example, ask yourself:
- Am I having BSODs with Win8?
- Am I having crashes or freezes in WinXP 64 bit?
- Am I having problems with WebRep?
- Is the sandbox unstable?

If they ain't broke, don't fix them!

I have a later version of avast! than ky, and have had no problems with it on my XP system. I see no reason to update it at this time. YMMV.

Joe's point, to contemplate the changelog, to see which (if any) of the issues "fixed" are applicable to your particular version/build, is indeed a valid consideration.   For example, IF I were running avast on Win8 AND IF I were experiencing blue screens there, then YES, I would be inclined to install and try-out the newer build quickly, perhaps as soon as it were made available.

In my case, using avast on WinXP (32-bit) and Win7 (x64-bit), the only thing remotely relevant to me is WebRep, which sometimes connects and sometimes doesn't.   But it's my belief that the problem is at their server end, with WebRep "not broadcasting" data, rather than a problem at my end in the program itself.

If it ain't broke, don't fix it!   --- Words of wisdom we should all heed.

This upgrade was expected. As mentioned before by David (Ky331) and myself, Avast! releases most of the time a follow up upgrade to iron things out. Also there are too many users, more than 150 million active users around the world, with so many combinations of hardwares and softwares that it is bound to encounter some users with problems. I think this is unavoidable. It would be extremely hard to replicate each and everyone of those combinations of programs and hardwares in avast! facilities and there are not enough betta testers to match that number.

I agree that if the upgrade has really nothing to do with what one needs, and Avast! is working flawlessly, there is no rush to install the new program. This upgrade was directed to Windows 8 users, some Windows 7 users with problems because some Avast! driver and their hardware or software, Windows XP 64 bit (rare) where Avast! behavioral Shield was killing some OS driver making it unbootable, and to fix WebRep under FireFox 16.0.2.

Let see how this version behaves. Still Avast! itself admits to continue testing for a few unresolves issues. So there might be another upgrade real soon.

Thread locked due to age.  If you have a similar question, please feel free to start a new thread.  Thanks.