New beta version 21.5.2467

[karel.stavik]

Hello,

we released new build 21.5.6324 to beta with some last minute changes related to User Interface and Software Updater.

Happy beta

Karel

---

Hi everyone,

there is a new beta version ready - 21.5.2467 (build 21.5.6320).

What is new

• Rescue disk is now working properly
• Few crashes fixed

Download links
Avast free https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_ONLINE/build_BETA
Avast premium https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_APR/platform_WIN/installertype_ONLINE/build_BETA

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).

AVAST Team

[bob3160]

Is there also a new version for Avast Omni - Beta and have any of the bugs been addressed?
Thanks.

[karel.stavik]

@bob3160 post:2

Is there also a new version for Avast Omni - Beta and have any of the bugs been addressed?
Thanks.

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.

Karel

[bob3160]

@Karel Šťavík post:3

@bob3160 post:2

Is there also a new version for Avast Omni - Beta and have any of the bugs been addressed?
Thanks.

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.

Karel

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)

[non_pc001]

Thanks for the new beta

[wphschmidt]

Got it. Auto update
Thanks.

[asynchron]

Thanks Karel, already up and running (Icarus).

[lukas.munduch]

@bob3160 post:4

@Karel Šťavík post:3

@bob3160 post:2

Is there also a new version for Avast Omni - Beta and have any of the bugs been addressed?
Thanks.

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.

Karel

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

[karel.stavik]

Hello,

we released new build 21.5.6324 to beta with some last minute changes related to User Interface and Software Updater.

Happy beta

Karel

[urh.strakl]

Hi the beta is working very well here, keep it up.

[asynchron]

@Karel Šťavík post:9

Hello, we released new build 21.5.6324 to beta with some last minute changes related to User Interface and Software Updater.

Happy beta

Karel

Two updates within 24 hours, you guys are keeping me/us busy…

[non_pc001]

Thanks for the new beta

Mail shield certificate issue still present with 21.5.6324 (icarus channel).

[bob3160]

@lukas.munduch post:8

@bob3160 post:4

@Karel Šťavík post:3

@bob3160 post:2

Is there also a new version for Avast Omni - Beta and have any of the bugs been addressed?
Thanks.

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.

Karel

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

Here is the packabe ID, U1KUT
It was created while the UI still showed the following.

https://d1ka0itfguscri.cloudfront.net/Lh/2021/06/04/12/21/cr1flrVha4j/preview.jpg

[hlavacekj]

@NON post:12

Thanks for the new beta

Mail shield certificate issue still present with 21.5.6324 (icarus channel).

Hi NON,

can you please send us mail.log for further investigation?

Thanks in advance,
HK

[non_pc001]

@HK post:14

@NON post:12

Thanks for the new beta

Mail shield certificate issue still present with 21.5.6324 (icarus channel).

Hi NON,

can you please send us mail.log for further investigation?

Thanks in advance,
HK

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.

[hlavacekj]

@NON post:15

@HK post:14

@NON post:12

Thanks for the new beta

Mail shield certificate issue still present with 21.5.6324 (icarus channel).

Hi NON,

can you please send us mail.log for further investigation?

Thanks in advance,
HK

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.

Thanks for the log. Could you please send the whole support package? Unfortunately, the log does not contain anything suspicious.

Thanks in advance,
HK

[lukas.munduch]

@bob3160 post:4

@Karel Šťavík post:3

@bob3160 post:2

Is there also a new version for Avast Omni - Beta and have any of the bugs been addressed?
Thanks.

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.

Karel

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, 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

[non_pc001]

@HK post:16

@NON post:15

@HK post:14

@NON post:12

Thanks for the new beta

Mail shield certificate issue still present with 21.5.6324 (icarus channel).

Hi NON,

can you please send us mail.log for further investigation?

Thanks in advance,
HK

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.

Thanks for the log. Could you please send the whole support package? Unfortunately, the log does not contain anything suspicious.

Thanks in advance,
HK

Package was sent to FTP: 20210608_1324_IVCCE_2988736846.zip

[hlavacekj]

@NON post:18

@HK post:16

@NON post:15

@HK post:14

@NON post:12

Thanks for the new beta

Mail shield certificate issue still present with 21.5.6324 (icarus channel).

Hi NON,

can you please send us mail.log for further investigation?

Thanks in advance,
HK

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.

Thanks for the log. Could you please send the whole support package? Unfortunately, the log does not contain anything suspicious.

Thanks in advance,
HK

Package was sent to FTP: 20210608_1324_IVCCE_2988736846.zip

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).

Best regards,
HK

[non_pc001]

@HK post:19

@NON post:18

@HK post:16

@NON post:15

@HK post:14

@NON post:12

Thanks for the new beta

Mail shield certificate issue still present with 21.5.6324 (icarus channel).

Hi NON,

can you please send us mail.log for further investigation?

Thanks in advance,
HK

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.

Thanks for the log. Could you please send the whole support package? Unfortunately, the log does not contain anything suspicious.

Thanks in advance,
HK

Package was sent to FTP: 20210608_1324_IVCCE_2988736846.zip

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).

Best regards,
HK

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.