Enjoy this beta!
We are looking forward to your feedback.
[b]Also please be informed that we would appreciate if you would be so kind and try our Antivirus product based on so called âicarusâ setup (installation and update engine) already used for other Avast products but now available also for AV. More information is here: https://forum.avast.com/index.php?topic=264883.0.[/b] Please note that in order to get it, you need to uninstall the current one (automatic migration is not supported at the moment).
Hi, there is definitely update also for Omni. But as far as I remember, you are using Icarus build of AV, right? Anyway, update for Icarus AV is also in public now, so you should get new version soon.
Both issues you reported are being investigated.
Updated via internal update.
After the first required re-start I was greeted with the popup âOops, something went wrongâ
After the next re-start, I couldnât open the UI. I proceeded to do a repair and then re-started the system.
I was now able to access the UI but was again greeted with the fact that the program needed to update. (Same problem as before)
Hello Bob, can you please generate new support package? We checked your older logs you sent us but some important logs were missing there (they were overwritten by new records). Its possible that it will be necessary to generate support package âimmediatelyâ after you induce issue again to avoid mentioned problem but we can try to check your current logs if you send it to us. Thank you
Hi HK, log was sent to FTP. Filename: NON_Mail_log_20210608.zip
Please note I normally use âignore certificate errorsâ option on the mail client since this happens.
Last one attempt was logged without that option; having a certificate error.
Hello Bob, thank you for your support package. We probably found out reason why AV UI sometimes could not be load after program update and OS restart â âOops, something went wrongâ screen. Currently we are working on fix and if everything will be OK we will release it with (hopefully the first) AV 21.6 BETA so it means that it will not be included in next 21.5 RC build. Thank you again
Thanks NON for the support package. To fix that issue, could you please install the certificate that was used to sign the whole certificate chain of the mail server you are trying to connect to? The reason why you can not connect is that the certificate is signed by unknown certificate authority. In the future release it will be entirely on the application to the decide whether it is ok to connect or not (and warn the user about it).
Hi thanks for analysis, but one of mail server is GMail, and I donât think its chain is corrupted.
Also, without Mail shield there is no problem accessing these mail servers.
Anyway Iâll make a repair and (if time allows) Avast reinstall to see what happens after that.