AVAST 2015 R4 Beta 5 & 6 (2015.10.4.2230 & 2231)

Consumer Products Public Beta Avast Antivirus Beta
1

Hi all,

New beta version is released: AVAST 2015 R5 Beta 5 (build number 2015.10.4.2230) and AVAST 2015 R4 Beta 6 (build number 2015.10.4.2231).

Today we again released 2 beta versions in order to test a new mechanism that will allow to avoid some compatibility issues in the future. For this beta testing we set the rule that machines with Windows XP will be able to update only to version 2230, all other machines will update as usual to the latest version 2231.

We won’t limit XP users in the future. This is just for testing purposes.

Changes:

How to install:

  1. If you have installed some beta version before you can update it to this latest version via Settings->Update->Program.

  2. Or you can download and install from here:

[b]http://files.avast.com/beta9x/avast_free_antivirus_setup.exe

http://files.avast.com/beta9x/avast_pro_antivirus_setup.exe

http://files.avast.com/beta9x/avast_internet_security_setup.exe

http://files.avast.com/beta9x/avast_premier_antivirus_setup.exe[/b]

How to provide feedback
Please for specific issues set a new topic in the Beta section (https://forum.avast.com/index.php?board=15.0). For general open discussion feel free to use this thread.

Avast cleaner:
http://files.avast.com/beta9x/avastclear.exe

It should be possible to install this version on top of your existing avast! installation (all settings should be preserved).

To report BSODs, crashes or any other none trivial problems please use new SupportPackage generating tool.

Instructions how to use it can be easily found:

We are looking forward for your feedback!

Thank you
Avast team

2

What is a new mechanism?And why Avast! not pushing Avast! 2016 product with less of “AD”?So Boring!!!

3

Is this forum so unattached from Avast that the users find out about an update before this forum does? Seems a tad strange.

4

The updates get pushed to the servers first then its posted on the forums :slight_smile:

5

Got the avast! message and let the program update.
It came out as advertised with update .2231 for my system. Then I downloaded my version from above links and it also made it to version .2231.
Version 2230 never showed up for Win7. 8)

6

Have just downloaded the avast free version, the file version is reported as 10.4.2231.1287.

I’m about to install it over the top of the regular release (having had to go back after the failed install to incorrect version for XP) and see if it does install 10.4.2230 and not 10.4.2231. Having first done a drive image.

EDIT: Well that was a short lived FAIL.

I had half expected this problem, given that the file version is one that is essentially blocked (10.4.2231) by the check on XP. See attached image 2 error popup.

So unless you do some more work on this feature you are going to have to release two different builds and not a single build that fails to install the correct version.

7

This is interesting. Unfortunately I’m not at my XP machine at the moment.
asap, I plan on Upgrading from an earlier final version of Avast Premier (see signature) using the GUI process;
I’m interested in seeing what transpires when the process involves a fairly distant version.

8

@Be Secure: When Avast! is ready to announce it’s 2016 products they will announce it here and after that it will through beta and RC testing and after that is done it will be released to the public. Different antivirus company has different release schedule like Norton, Trend Micro, Bitdefender, and etc. Bitdefender already released it’s 2016 products

9

So far working fine. Updated over 10.4.2229 without problems.

10

Concerning ‘2231’: No probs until now.

11

No problems with build 2231 here either :slight_smile:

Greetz, Red.

12

I confirm.

13

Any time frame on when this beta will become a final release ? ?
Currently on the latest stable release 2225 which is not too bad
but HTTPS scanning must be turned off or lots of sites (like https://us-mg6.mail.yahoo.com) will take forever to load. Personally, I really do not see
a need to scan what are supposed to be secured sites.

14

Or bring some optimization in https scan. Right now indeed performance is very bad on https pages, with high cpu usage.