Reports from users that 10.2.2505 will not update to 10.3.2505

Vladimyr · 2015-11-07T13:53:23.000Z

More info tomorrow

system · 2015-11-07T17:58:57.000Z

There is no version 10.3.2505. It’s 10.2.2505. Someone at Avast accidently let the console think there is a 10.3.2505, so the clients all think they need to update, but when you try, they say they’re on the latest version (10.2.2505).

Vladimyr · 2015-11-08T12:24:50.000Z

Well, that kinda makes sense… I mean the explanation, not the error :o

Then there’s the very strange situation on one of my accounts.
2 machines,
both with 10.2.2505 for as long as it’s been released,
both in contact with the management console,
both with up-to-date defs.
BUT, one “Safe”, the other “in danger” (1st pic).

At the request of the home user of the “in danger” machine, I replaced “Avast for Business” with Avast “Free” 11.1.2241.
However the uninstallation did not quite go to plan (2nd pic).
Fortunately, ‘avastclear’ cleaned up the remnants.
Whew! :

Announcements