*** Introducing: beta version of upcoming avast update (now 4.7.1096)

[rdmaloyjr]

I'm using 4.7.1089 beta.  It was doing just fine till I got online this morning.  After I got online avast! did an auto-update (tried to), up popped the red square saying error updating.  I tried a manual update, it reported I was already up to date.

Here is another thread about an update failing this morning. http://forum.avast.com/index.php?topic=31692.0

It doesn't say which version number of avast! he's using.  I'm using the English language version, he is using Dutch.

[Lisandro]

I'm using 4.7.1089 beta.  It was doing just fine till I got online this morning.

A single failure of automatic update could be just a temporary glitch.
Does this happen after you boot, again?

[Vlk]

Sorry, another forced update is going to happen in a short while (4.7.1091).
Hopefully, the last one.

I apologize for the inconvenience, this is really important to us (the problem we're chasing generates huge traffic on our updating servers and we absolutely need to have it solved).


Thanks
Vlk

[jadinolf]

Just got 1091.

Looking good.

[Lisandro]

Just got 1091.

Me too. Need to boot...

[Marc57]

Sorry, another forced update is going to happen in a short while (4.7.1091).
Hopefully, the last one.

I apologize for the inconvenience, this is really important to us (the problem we're chasing generates huge traffic on our updating servers and we absolutely need to have it solved).


Thanks
Vlk

No need to apologize Vik, You're trying to make Avast the best it can be.

[essexboy]

Got it still no problems

[rdmaloyjr]

Sorry, another forced update is going to happen in a short while (4.7.1091).
Hopefully, the last one.

I apologize for the inconvenience, this is really important to us (the problem we're chasing generates huge traffic on our updating servers and we absolutely need to have it solved).


Thanks
Vlk

When I got home from work I booted up & auto-updates worked just fine, got 1091 with no problem.

the problem we're chasing generates huge traffic on our updating servers

I guess this is the cause of the updating error I & at least one other has reported.  I thought it might have been a beta bug.

In a round about way in was a beta bug.

[Lisandro]

Just got 1091.

Me too. Need to boot...

No problems after boot.

[Jahn]

NP with 1091 on XP Home.

[martosurf]

Runs smooth

[bcool]

sorry if I missed this in the thread but...

I got .1091 this morning but in reality all of the program files are still .1087.  I even had to reboot. This is expected behavior? 

NB.  I wasn't running betas to my knowledge, fyi

[DavidR]

No problem here all processes are shown as 4.7.1091, see image, have you rebooted yet ?

[bcool]

Thanks.   Yes I had to reboot yet if I go to actual folder   all files are still .1087    When I attempt to update manually, I'm told that I'm running .1091 and up to date.  Something wacky somewhere?

[DavidR]

Several of my file properties still report version .1087 not all files will have been updated, but with a beta build I'm sure they are less concerned with the aesthetics if you look at the about avast that will/should report the correct build. Though you will also notice Alwil have invested in a Time Machine as the build date is Dec2007 (4.7.1091), all of this will get tidied up in due course before a regular release for sure (I hope).