New Beta version 19.1.2359

Hi everyone,

new beta version 19.1.2359 (build 19.1.4140) is released.

What was fixed

  • Update progress is visible in UI (applicable during update to next version)
  • Small changes in exceptions related to Behavior Shield
  • Minor changes before release to public

Download links:
http://public.avast.com/mkt/betaav/avast_free_antivirus_setup_online.exe
http://public.avast.com/mkt/betaav/avast_internet_security_setup_online.exe
http://public.avast.com/mkt/betaav/avast_premier_setup_online.exe
http://public.avast.com/mkt/betaav/avast_pro_antivirus_setup_online.exe

Enjoy this beta!
We are looking forward to your feedback.

AVAST Team.

Thanks Karel, testing it asap…

Thanks, updating now. :slight_smile:

WFI is opening really slooooow (5-8 seconds).
Else, the new beta is running smooth, so far…

OS was very reluctant to ‘Reboot’ on HP Envy, my other HP was immediate.
Other then that all seems fine…

Will there be ‘further/future development’ to the “Geek Area” in next betas???

A valid question, nothing was added there since it was introduced. :frowning:

Agreed, and having more control and access to settings (especially the “Firewall”) is of major interest to me. ???

yes we are working on geek area right now and it will appear in UI in January

Thanks for the new beta :slight_smile:

Thanks for the information Martin. :slight_smile:

:wink: Minor changes before release to public

coming soon release to public

I have a process in taskmanager it is normal?

“Avast Dump Process”

It is a partial of the beta version?

Yes, it is normal. I believe it will be a regular part of Avast in the final version as well.

What is it’s function ???

Thanks, I calmed down.

I was thinking about it. First: this is only part of the BETA version (stronger error detection) or Second: Because it is an independent process and It can also work in case of a complete crash.

But not problem because very low resource requirement. 1MB CPU load= 0

As the name suggests, its purpose it to create a crashdump when one of our processes crashes.
Now this is nothing new, that functionality has been there for years - but we (gradually) learned that it didn’t work for all possible crash types and that a new (standalone) process is the only option to get a (so far) complete coverage.

@igor,
Thanks for the information.

Bankmode bug, not sure if this is related to the AV or ASB or both, see screenshot.

+1
Here also. :slight_smile: