NEW: Beta version released - 12.2.2276

[petr.chytil]

Hi all,

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.

Enjoy,
Petr

[jefferson sant]

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.

attached logs

[bob3160]

Why did the UI open on my desktop this morning when I booted my system

[Eddy]

Known Issues:
+ From time to time, Avast GUI opens without any apparent reason

[Alikhan]

Known Issues:
+ From time to time, Avast GUI opens without any apparent reason

From the OP.

[Gopher John]

The graphic shows that Avast Self Defense is turned off.  I don't know if that would trigger the AvastUI to open.

[bob3160]

The graphic shows that Avast Self Defense is turned off.  I don't know if that would trigger the AvastUI to open.

One has nothing to do with the other. As posted, it's a known issue and will be fixed before the final release.

[NON]

Thanks for the update, so far no problems.

[jefferson sant]

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.

[Patrick99]

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?

[DavidR]

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.

See this topic and many others relating to you are unprotected or shields not active https://forum.avast.com/index.php?topic=189221.0.

[bob3160]

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.

See this topic and many others relating to you are unprotected or shields not active https://forum.avast.com/index.php?topic=189221.0.

Just to clarify, the shields were always active, the messenger however that gave you that information, was not.

[Patrick99]

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?

Are these the actual beta executables that should be running:

aswstrm.dll.1404488694718
aswstrm.dll.sum.1404488694718
avastui.exe.1404488694718
avastui.exe.sum.1404488694718

If not, why are they included in the program folder?

[bob3160]

The final has been released:
https://forum.avast.com/index.php?topic=189131.0