Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: Endt on April 04, 2016, 09:29:16 PM

Title: NEW Beta released - 2016.11.2.2259
Post by: Endt on April 04, 2016, 09:29:16 PM
2016.11.2.2259
2016-04-04

+ minor fixes
+ added translations

Download links as usual or just update.
https://forum.avast.com/index.php?topic=179943.0

Keep it on,
B.
Title: Re: NEW Beta released - 2016.11.2.2259
Post by: Be Secure on April 05, 2016, 04:32:23 AM
2016.11.2.2259
2016-04-04

+ minor fixes
+ added translations

Download links as usual or just update.
https://forum.avast.com/index.php?topic=179943.0

Keep it on,
B.
What are those fixes?@Endt
Title: Re: NEW Beta released - 2016.11.2.2259
Post by: NON on April 05, 2016, 03:54:52 PM
Thanks for the update. So far working fine. Still need one more reboot to close welcome screen though.
Title: Re: NEW Beta released - 2016.11.2.2259
Post by: heikwith on April 05, 2016, 11:44:49 PM
Certificate problem with Avast 11.2.2259 in windows 10 build 14279.
No problem with Avast disabled.
I already told you this in avast 11.2.2257.
Why is this bug still unresolved.
Even I can not display this topic with Avast 11.2.2259 enabled.
Please can I get some reaction from Avast people?
Title: Re: NEW Beta released - 2016.11.2.2259
Post by: heikwith on April 06, 2016, 02:20:51 PM
Certificate problem with Avast 11.2.2259 in windows 10 build 14279.
No problem with Avast disabled.
I already told you this in avast 11.2.2257.
Why is this bug still unresolved.
Even I can not display this topic with Avast 11.2.2259 enabled.
Please can I get some reaction from Avast people?
I just upgraded to windows 10 build 14295 and I see my Certificate problems are GONE.
Title: Re: NEW Beta released - 2016.11.2.2259
Post by: Endt on April 06, 2016, 03:42:34 PM
Hello heikwith,

sorry for delayed response. At the moment, we cannot provide support for insider builds of Win 10. From time to time something stops working on one build of Win and in the other build it is back again working.

Thanks for testing,
B.