NEW VERSION: 2016.11.2.2262

[MartinZ]

Hi all,

I am happy to announce new version AVAST 2016 (build number 2016.11.2.2262).
This update fixes some critical crashes during installation and program update.

What’s new:

• fixed crashing installations

• fixed critical crashes on some AMD processors

• fixed problem with huge antispam logfile

• fixed repeatedly adding SafeZone browser icon on desktop after avast update

How to install:

1. Update from existing Avast version via Settings → Update → Update program

2. Or you can download and install from here:

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

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

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

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

We hope you enjoy the new version!
AVAST Team

[Vapor]

Just installed the latest update on avast Pro and surprisingly all works good.
Why can’t avast stay consistent and instead of adding add-ons that lots of users don’t even want (I can’t stand them) and make their updates /upgrades as smoothly as this 1 ;D

[priestlucas123]

Sadly this release does not include the fix for creating rescue disks (iso or usb). Disabling Avast self-defense module allows rescue disks to be created.

[MartinZ]

Thanks for positive feedback. We plan to do more changes in the product soon. We will remove some features that aren’t used or are causing more troubles than goodness. Our current focus is on improving detections and overall performance impact on the PC ( disk space, ram usage, web browsing speed). We will continuosly introduce these changes in the beta channel - https://forum.avast.com/index.php?board=15.0

[MartinZ]

@priestlucas123 post:3

Sadly this release does not include the fix for creating rescue disks (iso or usb). Disabling Avast self-defense module allows rescue disks to be created.

Sorry it didn’t make it to this version, but this bug is fixed on internal versions, we just have to test it and then will ship the fix via microupdate.

[DavidR]

Why, Why, Why are beta builds released to regular release versions without a build change. This practice confuses the hell out of people.

[Vapor]

Why, Why, Why are beta builds released to regular release versions without a build change. This practice confuses the hell out of people

Tell me about it

So this .2262 its beta release!!!

[Secondmineboy]

@Vapor post:7

So this .2262 its beta release!!!

Its clearly a final release but Avast should stop releasing Beta build as final builds.

[DavidR]

@Vapor post:7

Why, Why, Why are beta builds released to regular release versions without a build change. This practice confuses the hell out of people

Tell me about it

So this .2262 its beta release!!!

NO it has been released for normal program update release - that is why it is so damn confusing using what was the last beta build number.

[Alikhan]

@MartinZ post:4

Thanks for positive feedback. We plan to do more changes in the product soon. We will remove some features that aren’t used or are causing more troubles than goodness. Our current focus is on improving detections and overall performance impact on the PC ( disk space, ram usage, web browsing speed). We will continuosly introduce these changes in the beta channel - https://forum.avast.com/index.php?board=15.0

That’s nice to hear.

You should also look to improve startup times.

Anyways, I’m happy with this release since it doesn’t seem to have any major issues.

[Vapor]

Its clearly a final release but Avast should stop releasing Beta build as final builds.

OK that just doesn’t make sense, you contradicting your statement

[MartinZ]

@DavidR post:6

Why, Why, Why are beta builds released to regular release versions without a build change. This practice confuses the hell out of people.

Because we don’t distinguish between beta versions and release versions, but between beta and release channel. The number doesn’t change because the binaries are the same, we just promoted this build to the release channel. Yes now on beta channel you will have the same version as on release, but don’t worry you will get new version for beta channel next week…

Or what exactly confuses you?

[Secondmineboy]

@Alikhan post:10

@MartinZ post:4

Thanks for positive feedback. We plan to do more changes in the product soon. We will remove some features that aren’t used or are causing more troubles than goodness. Our current focus is on improving detections and overall performance impact on the PC ( disk space, ram usage, web browsing speed). We will continuosly introduce these changes in the beta channel - https://forum.avast.com/index.php?board=15.0

That’s nice to hear.

You should also look to improve startup times.

Anyways, I’m happy with this release since it doesn’t seem to have any major issues.

You really need to finally get the HIPS, better anti-phishing, automated axploit protection and flippin NG working or added, youre way overdue with this.

[Vapor]

NO it has been released for normal program update release - that is why it is so damn confusing using what was the last beta build number

Alright

[MartinZ]

@Alikhan post:10

@MartinZ post:4

Thanks for positive feedback. We plan to do more changes in the product soon. We will remove some features that aren’t used or are causing more troubles than goodness. Our current focus is on improving detections and overall performance impact on the PC ( disk space, ram usage, web browsing speed). We will continuosly introduce these changes in the beta channel - https://forum.avast.com/index.php?board=15.0

That’s nice to hear.

You should also look to improve startup times.

Anyways, I’m happy with this release since it doesn’t seem to have any major issues.

Yes startup time is something we work on as well…

[DavidR]

@MartinZ post:12

@DavidR post:6

Why, Why, Why are beta builds released to regular release versions without a build change. This practice confuses the hell out of people.

Because we don’t distinguish between beta versions and release versions, but between beta and release channel. The number doesn’t change because the binaries are the same, we just promoted this build to the release channel. Yes now on beta channel you will have the same version as on release, but don’t worry you will get new version for beta channel next week…

Or what exactly confuses you?

It was never like this in the past, this practice seems to have crept in from avast 2016.

As for confusion, you only have to look at the forums to see people are asking is this a beta build, because they know that 2262 was a beta version.

[Alikhan]

I don’t see any NG service running…

Has this been addressed or will be fixed in future versions?

[MartinZ]

Yes we did this in the past, but we changed it last year, because it was causing troubles. To ensure the best quality we always want to have the “release” binaries in beta channel first for few days to see if it’s stable, before we push it for general use.

Yes of course we have our internal QA, automated/manual testing, but we are never able to simulate all scenarios, machine configurations etc that exist in the real world. Here is the great help of the beta community.

I hope this makes sense…

[Alikhan]

@MartinZ post:18

Yes we did this in the past, but we changed it last year, because it was causing troubles. To ensure the best quality we always want to have the “release” binaries in beta channel first for few days to see if it’s stable, before we push it for general use.

Yes of course we have our internal QA, automated/manual testing, but we are never able to simulate all scenarios, machine configurations etc that exist in the real world. Here is the great help of the beta community.

I hope this makes sense…

Yes it makes sense.

In simple terms, you are delaying it for a few days after a new version is released to see if it’s stable for daily use.

[bob3160]

http://www.screencast-o-matic.com/screenshots/u/Lh/1461786189179-46659.png

After a new install on the latest insider preview build of Windows 10 (14332)