new beta version is live: 12.2.2276
In this release, we are trying to finish a few long-going internal projects. Especially improved licensing and registration to Windows Security center.
Fixes and improvements:
Resolved compatibility issues with Windows 10 Anniversary Update (and the latest Windows Insider builds)
Fixed bug in the Settings export (Back up settings)
Known Issues:
From time to time, Avast GUI opens without any apparent reason
Download links as usual or just update your current beta.
I have had with online installer start and finish installing the error occurred.Virtual machine stopped running with windows xp crash the system, with offline installer the error is displayed at the beginning of installation.CyberCapture contains this option always block application suspicious,i had not seen previously.
The same thing happens with Windows 7 Enterprise.
nothing, just released the final version and error was not corrected.
The bug was discovered later with you already said. It is because they were worried about windows 10 and forget the most important thing.
The beta program started this morning but with all shields off. Since I was at the mall, the Secureline prompt appeared and I selected it to connect. Oddly, there was a message about unpacking a gift for me that appeared on the user interfaces of Avast AV and Secureline.
What was running for the Avast AV user interface was a file named: avastui.exe.146989429457801
I could not get the shields to be active, so I killed the Avast AV UI task and launched the avastui.exe file instead. All was well, including the absence of this “click here to unpack your gift” message.
What is going on with what I have described above?
This isn’t a beta build - this was a regular program update release - the fact they the beta and release had the same program version 12.2.2276, but they had a different underlying build number.
This has been causing confusion for ages and I wish it would stop.
