Avast Beta 17.4.2294

[hectic-mmv]

Hi everyone,

new beta version 17.4.2294 is here 8).

What’s new:

• fixes and things under the hood
• fixed several crashes in web shield
• fixed crashing setup during VPS update on 32b OSes

Download links:
https://forum.avast.com/index.php?topic=179943.0

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

[Lord_Ami]

Thanks for the update! Went smooth as usual.

EDIT:
Same on second PC.

[Asyn]

Testing it asap…

[NON]

Thanks for the new beta ;D

[DavidR]

Just updated from the UI of 17.4.2293.

[Rednose]

Thnx guys

Greetz, Red.

[Asyn]

Found a GUI bug, see screenshot. (German GUI)

[NON]

@Asyn post:7

Found a GUI bug, see screenshot. (German GUI)

Confirmed here, too. I have 4 of them.
As each of their settings have certain path in the “Scan Areas” section, it looks like a remnant of context menu (Windows Explorer) scan in the past.

[system]

tested with Avast Beta 17.4.2294,
:(Nothing is fixed the problem ( https://forum.avast.com/index.php?topic=199732.0 ).

[Asyn]

@NON post:8

@Asyn post:7

Found a GUI bug, see screenshot. (German GUI)

Confirmed here, too. I have 4 of them.
As each of their settings have certain path in the “Scan Areas” section, it looks like a remnant of context menu (Windows Explorer) scan in the past.

Hi NON, seems you’re on the right track. Cheers.

[DavidR]

@Asyn post:10

@NON post:8

@Asyn post:7

Found a GUI bug, see screenshot. (German GUI)

Confirmed here, too. I have 4 of them.
As each of their settings have certain path in the “Scan Areas” section, it looks like a remnant of context menu (Windows Explorer) scan in the past.

Hi NON, seems you’re on the right track. Cheers.

Mine appears fine as I hadn’t done a context scan in some time.

I have however found another bug (the Invisible Smart Scan), after boot I opened the UI to check if the same issue as yours was present but mine was OK.

I did however notice that there was the Red circle with ‘1’ over the Bell (notifications), clicking that it reports Smart Scan - ‘We found some issues.’ Well I never ran a Smart Scan and as per previous issue No Report in Scan History or entry in the log file.

The is getting frustrating avast fix something and seem to break something else, though I did find and report this in 17.4.2293.

[Asyn]

@DavidR post:11

@Asyn post:10

@NON post:8

@Asyn post:7

Found a GUI bug, see screenshot. (German GUI)

Confirmed here, too. I have 4 of them.
As each of their settings have certain path in the “Scan Areas” section, it looks like a remnant of context menu (Windows Explorer) scan in the past.

Hi NON, seems you’re on the right track. Cheers.

Mine appears fine as I hadn’t done a context scan in some time.

After rebooting the system, the entry/bug (Reply #6) is gone. (Didn’t try to reproduce it yet)

[Asyn]

@DavidR post:11

I have however found another bug (the Invisible Smart Scan), after boot I opened the UI to check if the same issue as yours was present but mine was OK.

I did however notice that there was the Red circle with ‘1’ over the Bell (notifications), clicking that it reports Smart Scan - ‘We found some issues.’ Well I never ran a Smart Scan and as per previous issue No Report in Scan History or entry in the log file.

Hi Dave, can’t reproduce this one. The funny thing is, I don’t get any notifications after running a scan at all.
Wonder, if this is another bug or just a sloppy workaround for the smart-scan rescan issue…

[DavidR]

@Asyn post:13

@DavidR post:11

I have however found another bug (the Invisible Smart Scan), after boot I opened the UI to check if the same issue as yours was present but mine was OK.

I did however notice that there was the Red circle with ‘1’ over the Bell (notifications), clicking that it reports Smart Scan - ‘We found some issues.’ Well I never ran a Smart Scan and as per previous issue No Report in Scan History or entry in the log file.

Hi Dave, can’t reproduce this one. The funny thing is, I don’t get any notifications after running a scan at all.
Wonder, if this is another bug or just a sloppy workaround for the smart-scan rescan issue…

Sloppy may well be the case in getting rid of one bug only to create another. Given that my test system is my XP Pro SP3 desktop, as it has the greatest protection and a really robust backup and recovery strategy. And some had been reporting issues with XP, but I didn’t suffer with them.

However, I did experience this in the last beta and reported it also in the 17.4.2293 beta, https://forum.avast.com/index.php?topic=201164.msg1389908#msg1389908.

[Asyn]

@Asyn post:12

@DavidR post:11

@Asyn post:10

@NON post:8

@Asyn post:7

Found a GUI bug, see screenshot. (German GUI)

Confirmed here, too. I have 4 of them.
As each of their settings have certain path in the “Scan Areas” section, it looks like a remnant of context menu (Windows Explorer) scan in the past.

Hi NON, seems you’re on the right track. Cheers.

Mine appears fine as I hadn’t done a context scan in some time.

After rebooting the system, the entry/bug (Reply #6) is gone. (Didn’t try to reproduce it yet)

OK, just tried it again and this bug is reproducible.

[Asyn]

Erm, another Chrome ad, this time in the SU… :

[DavidR]

I’m in luck, no Chrome ad for me.

[Asyn]

@DavidR post:17

I’m in luck, no Chrome ad for me.

Lucky you…!

[DavidR]

@Asyn post:18

@DavidR post:17

I’m in luck, no Chrome ad for me.

Lucky you…!

I generally have no problem with the ad in the bottom quarter of the UI main page, but to start shoving them in other sections of the UI is I believe a step too far.

With popup ads, the one in the main page of the UI and now in other UI pages, isn’t going to endear the user to purchase (or install) what is being rammed down their throats.

[Giraffe]

Why all this pushing of Chrome - money? I wouldn’t ever use Chrome itself - possibly Vivaldi or another derivative at a push…