New beta version 21.5.2465

[KarelŠťavík]

Hello,

we had to release new build 21.5.6303 to fix issue when product does not report correctly crashes to the application backend. Issue is fixed in new build.

Karel

---

Hi everyone,

there is a new beta version ready - 21.5.2465 (build 21.5.6297).

What is new

• Webcam Shield now notifies you about apps using your webcam (in both Strict Mode and No Mercy Mode)
• Internal changes related to User Interface (new version of Chromium Embedded Framework)

Known issues

• Rescue Disk cannot be created due to recently changed location of some file(s)

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

[Asyn]

Thanks Karel, testing it asap (on Icarus channel)…

[NON]

Updated via icarus channel.

After this update, mail client starts to fail to receive e-mails with error “0x800B0109, failed to verify certificate”.
Is something changed with this update?

[bob3160]

Program did an auto update and I was asked to reboot.
After the reboot, I was greeted with the following when trying to open the UI.

https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/28/11/45/crhuXGVhoFV/preview.jpg

Selecting the repair wasn’t possible.
I’ve done 2 reboots the UI does not open.
After the restart, the icon reveals that the system is not protected
I can select update program and that fixes the problem till the next restart. (This is an ongoing problem that hasn’t been resolved.)
I’m about to do a repair via Apps and Features to see if I can get the UI to show up when requested.

[bob3160]

@bob3160 post:4

Program did an auto update and I was asked to reboot.
After the reboot, I was greeted with the following when trying to open the UI.

https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/28/11/45/crhuXGVhoFV/preview.jpg

Selecting the repair wasn’t possible.
I’ve done 2 reboots the UI does not open.
After the restart, the icon reveals that the system is not protected
I can select update program and that fixes the problem till the next restart. (This is an ongoing problem that hasn’t been resolved.)
I’m about to do a repair via Apps and Features to see if I can get the UI to show up when requested.

After a repair the latest beta version’s UI now opens when requested.
The old problem of always needing to do a program update to clear the unprotected message remains.

https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/28/11/57/crhuXPVhoqT/preview.jpg

[Asyn]

@bob3160 post:5

The old problem of always needing to do a program update to clear the unprotected message remains.

Confirmed, same here.

[Asyn]

@NON post:3

After this update, mail client starts to fail to receive e-mails with error “0x800B0109, failed to verify certificate”.

Hi, out of interest, which mail client are we talking about…!?

[NON]

@Asyn post:7

@NON post:3

After this update, mail client starts to fail to receive e-mails with error “0x800B0109, failed to verify certificate”.

Hi, out of interest, which mail client are we talking about…!?

I mainly use a client called “nPop” but certification error can be confirmed with Thunderbird too.

Edit:
OK it seems Avast signs its MITM certificate with “Untrusted” root, that makes client not to trust these certificates.

[schmidthouse]

Thanks, got it

Received Splash Screen on first Reboot

[Asyn]

@NON post:8

@Asyn post:7

@NON post:3

After this update, mail client starts to fail to receive e-mails with error “0x800B0109, failed to verify certificate”.

Hi, out of interest, which mail client are we talking about…!?

I mainly use a client called “nPop” but certification error can be confirmed with Thunderbird too.

Edit:
OK it seems Avast signs its MITM certificate with “Untrusted” root, that makes client not to trust these certificates.

I see. Cheers

[KarelŠťavík]

@bob3160 post:5

The old problem of always needing to do a program update to clear the unprotected message remains.

Hi Bob, can you please send us the screenshot of main UI with the “unprotected message”? Please also generate and send the logs (Menu / Settings / Troubleshooting / Send logs) and let me know the number of the support package.
Thank you.
Karel

[bob3160]

@Karel Šťavík post:11

@bob3160 post:5

The old problem of always needing to do a program update to clear the unprotected message remains.

Hi Bob, can you please send us the screenshot of main UI with the “unprotected message”? Please also generate and send the logs (Menu / Settings / Troubleshooting / Send logs) and let me know the number of the support package.
Thank you.
Karel

https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/30/12/00/crhvlcVhqOx/preview.jpg

https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/30/11/56/crhvX8VhqOY/preview.jpg

Further details of obtaining those lags would be helpful. Thanks

[KarelŠťavík]

Hello,

we had to release new build 21.5.6303 to fix issue when product does not report correctly crashes to the application backend. Issue is fixed in new build.

Karel

[bob3160]

@Karel
Full Dump sent here is the id# 3A4YB

[HK]

@NON post:8

@Asyn post:7

@NON post:3

After this update, mail client starts to fail to receive e-mails with error “0x800B0109, failed to verify certificate”.

Hi, out of interest, which mail client are we talking about…!?

I mainly use a client called “nPop” but certification error can be confirmed with Thunderbird too.

Edit:
OK it seems Avast signs its MITM certificate with “Untrusted” root, that makes client not to trust these certificates.

Hi NON,

Thanks for your report, problem has been isolated and fixed. You can expect a fix in one of the upcoming 21.5 beta releases.

Best regards,
HK

[schmidthouse]

Updated to v. 21.5.2466

[bob3160]

@schmidthouse post:16

Updated to v. 21.5.2466

https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/31/13/15/crhwIoVhrd2/preview.jpg

[NON]

@HK post:15

@NON post:8

@Asyn post:7

@NON post:3

After this update, mail client starts to fail to receive e-mails with error “0x800B0109, failed to verify certificate”.

Hi, out of interest, which mail client are we talking about…!?

I mainly use a client called “nPop” but certification error can be confirmed with Thunderbird too.

Edit:
OK it seems Avast signs its MITM certificate with “Untrusted” root, that makes client not to trust these certificates.

Hi NON,

Thanks for your report, problem has been isolated and fixed. You can expect a fix in one of the upcoming 21.5 beta releases.

Best regards,
HK

Thanks

[Asyn]

@Karel Šťavík post:13

Hello, we had to release new build 21.5.6303 to fix issue when product does not report correctly crashes to the application backend. Issue is fixed in new build.

Karel

Thanks Karel, testing it asap (on Icarus channel)…

[bob3160]

Program did an auto update and I was asked to reboot.
After the reboot, I was greeted with the following when trying to open the UI.

https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/28/11/45/crhuXGVhoFV/preview.jpg

Selecting the repair wasn’t possible.
I’ve done 2 reboots the UI does not open.
After the restart, the icon reveals that the system is not protected
I can select update program and that fixes the problem till the next restart. (This is an ongoing problem that hasn’t been resolved.)
I’m about to do a repair via Apps and Features to see if I can get the UI to show up when requested.