Client-Program-Update-Release-Version-10-3-2507

[REDACTED]

Hi Everyone,

See this link for information on the new release

https://support.business.avast.com/hc/en-us/articles/206460823-Client-Program-Update-Release-Version-10-3-2507

Thanks!

Jeff

[Vladimyr]

Thanks Jeff 

[REDACTED]

Excellent - thanks Jeff!

If I have my settings in the Cloud console set for "Program Updates:  Automatic", will the clients all automatically update to the new software and restart?   Or do I have to manually update them all with a task?

[Zeniit]

Thanks Jeff!

I wanted to download the new installer, but I got the old v2505 build.

Please fix it, thank you very much.

Zeniit

[REDACTED]

Okay - now I have users showing "In Danger" and the console is saying there is a new program released 11/02/15 (today) and it's showing version 10.3.2505.  What happened to 2507?  Was it pulled and those clients need to downgrade?

Edit:  My clients with 2507 already installed can't downgrade - when attempting it says "The client is already up to date", since it has a newer version.

What are we supposed to do?  Do we uninstall Avast completely, and let the old version reinstall?

[REDACTED]

Okay - it's getting confusing:

1) Original version installed on clients:   10.2.2505
2) New version released last week:  10.3.2507
3) New version released this morning:  10.3.2505

Which version is the correct version?

[REDACTED]

Okay - it's getting confusing:

1) Original version installed on clients:   10.2.2505
2) New version released last week:  10.3.2507
3) New version released this morning:  10.3.2505

Which version is the correct version?

Apparently build 10.3.2507 was pulled from public updates,  see:
https://forum.avast.com/index.php?topic=178529.msg1263893#msg1263893

Automatic program updates are evil IMHO, I always prefer a push-controlled deployment of any program update personally for this very reason.

[Vladimyr]

Er.. Ok.
So if I have PCs running 10.3.2507 which are not showing any evidence of a problem, but,
about which I am getting notifications that the software is 21 days out of date, BUT,
updating from 10.3.2507 to 10.3.2505 doesn't work,
is it safe to just do nothing until an update with a version number exceeding 10.3.2507 comes along?

[REDACTED]

is it safe to just do nothing until an update with a version number exceeding 10.3.2507 comes along?

Difficult to say for sure without more info from Avast on what the fault is! 

I also have a Win7 machine that doesn't seem to be experiencing symptoms except for the 21 day thing, and is in regular contact with the cloud and the definitions are current so I assume the service is OK.  I'm going to leave it installed as it's my sandpit test box anyway and it should update when >10.3.2507 arrives.  Depending on how many machines you would have to visit to uninstall and reinstall 10.3.2505 might sway your approach too (ie, you might choose to fixup only mission-critical machines to ensure the service doesn't randomly stop).

I think downgrading the release number was a a poor choice for Avast since 10.3.2507 was announced (via this thread) and began deploying, however I like to think they had a very good reason to do so.  But then to withdraw it and replace with a new build again without any warning on what the issue was so the unlucky ones can take appropriate action, doesn't fill me with much confidence...   

[Eddy]

oops
You're not authorized to access this page.

Program version : 2015.10.2.2205
Checking for updates show : Already up-to-date

[Vladimyr]

I think downgrading the release number was a a poor choice for Avast since 10.3.2507 was announced (via this thread) and began deploying, however I like to think they had a very good reason to do so.  But then to withdraw it and replace with a new build again without any warning on what the issue was so the unlucky ones can take appropriate action, doesn't fill me with much confidence...   

Pretty much what I'm thinking GFM.
I only updated 1 XP machine (multiple times previously bitten with home-user releases) and wouldn't have known there was a problem but for the out-of-date warning emails and console messages.

[g.yearsley]

oops
You're not authorized to access this page.

Program version : 2015.10.2.2205
Checking for updates show : Already up-to-date

yeah I get the same message, where can I get the working version downloaded from.?

[Eddy]

Created tasks for scanning and updating.
Scanning worked, updating not.

[REDACTED]

Jeff - please don't leave us hanging like this.  If Avast releases something, and then pulls it, let us know.  Tell us what to do to fix this issue?  I see you put out a new version on 11/2/15 (10.3.2505), however none of the 2507 clients will upgrade to it, as the version number is smaller.

The silence is killing us.

[REDACTED]

Hi Guys,

Sorry for the delay, it's been really busy as you can imagine. As everyone has noticed the 2507 release caused the services to randomly stop on some devices. We had hoped to get a new release the next day but unfortunately this was not the case. Our guys are working as quickly as possible to fix the issue(s) and get the release out. The last word I had was "atleast a week" so I wouldn't look for anything until the early part of next week. I'll try to keep you guys posted on the update as I get more info and again, sorry for the silence, I didnt mean to ignore you guys just been very busy.


Thanks!

Jeff