New beta version 21.1.2444

[petr.kolacek]

Hi everyone,

there is a new beta testing - 21.1.2444 (build 21.1.5914).

What was fixed

• possible BSOD (blue screen of death) due to problems in identity protection driver (internally catched just once on one machine during a month, will fix it in next BETA)
• not responding dialog in case of multiple detections at the same time

Known issues

• some obsolete Antivirus program files and folders may remain on disk after update
• configuration of the program can be restored/reset after update without user interaction
• detection dialogs from Identity Protection are sometimes not on top (and therefore visible, but detection and removal works fine)
• BETA logo missing in main User Interface

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.

AVAST Team

[Asyn]

Thanks Petr, testing it asap…

• No details in German splash screen (Screenshot attached)
• Note, some additional data has been sent via AvBugReport

[Asyn]

@petr.kolacek post:1

What was fixed

• BETA logo missing in main User Interface

Can’t confirm the fix, it’s still missing here. (Screenshot)

[petr.kolacek]

@Asyn post:3

@petr.kolacek post:1

What was fixed

• BETA logo missing in main User Interface

Can’t confirm the fix, it’s still missing here. (Screenshot)

Hi Asyn, I am sorry, mea culpa, this one will be fixed in next beta, not in this one thank you for reporting it! Have a nice day, Petr

[Asyn]

@petr.kolacek post:4

@Asyn post:3

@petr.kolacek post:1

What was fixed

• BETA logo missing in main User Interface

Can’t confirm the fix, it’s still missing here. (Screenshot)

Hi Asyn, I am sorry, mea culpa, this one will be fixed in next beta, not in this one thank you for reporting it! Have a nice day, Petr

Hi Petr, no problem, it’s only a minor bug anyway. Have a nice day as well. Cheers

[schmidthouse]

Thanks, got it

[strakl]

Guys, quick question, has anyone experienced the restore/reset of their config of the program after update? i have a lot of settings set and i don’t want that to happen.

[DavidR]

@strakl post:7

Guys, quick question, has anyone experienced the restore/reset of their config of the program after update? i have a lot of settings set and i don’t want that to happen.

You can (or should be able to) use the avastUI > Menu > Settings > Troubleshooting > Backup Your Avast Settings function.
You should be able to save it to a folder of your choice, and use the > Settings > Troubleshooting > Restore Settings function if required.

[NON]

Thanks for the new beta

[Asyn]

@strakl post:7

Guys, quick question, has anyone experienced the restore/reset of their config of the program after update? i have a lot of settings set and i don’t want that to happen.

Hi, it didn’t happen here. But (as said by Dave) you can always export/import your settings.

[darkwaechter]

Still have following memory leak since 20.7 …

@darkwaechter post:73

@Paulino Sato post:70

Hi,
I found the the source of the problem, is the wpad.dat file used to auto define the proxy (or no proxy).

Sorry for delay.
Version 20.8.5684.602 not solved my situation. Same behavior, soon I connect network cable Avsta start eating all memory.
It happens on some networks, not on others. Or start after some time.
My network are the culprit? Why special have on these networks?

My test procedure is this:
Disable swap/paging on window, avoid system to use paging, a avast just eat all ram and killed by the kernel (I think).
Start computer with network cable disconnected (no wifi).
Open taskmanager, and Avast GUI.
Connect network cable and watch rise of memory usage by Avast.

If have some thing on my network causing the Avast memory issue, what can be?
My firewall is a linux machine, very simple, just for NAT, no complex packet filtering, multi internet access and Squid proxy (all most disabled).
I drop all forwarding from offending host. No change.
Dropped all input to firewall. NOW, avast no eating memory.
I opened port 80, and Avast start eating memory again. What Avast accessing? Check the webserver log.
Avast getting the wpad file for proxy definition on this network. Renamed wpad.dat file, and try again.
Whitout wpad, no problem, avast try to get file, get a 404 and nothing happens.

The log on webserver (lighttpd 1.4.19):
10.0.103.91 wpad - [09/Oct/2020:09:36:43 -0300] "GET /wpad.dat HTTP/1.1" 200 94 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.3.3626.1895 Safari/537.36 Avastium (20.8.2432)"

wpad.dat content:

function FindProxyForURL(url, host)
         return "DIRECT";
}

I hope this information helps to solve the problem.

Tanks, Paulino.

I confirm, it comes from the proxy !

Disabling the option “Automatically detect settings” of proxy under Windows, will no more cause the memory leak.
Activating it again, and Avast eats again all memory …

https://s23429.pcdn.co/wp-content/uploads/2015/11/windows-automatic-proxy-setup.png

[strakl]

@Asyn post:10

@strakl post:7

Guys, quick question, has anyone experienced the restore/reset of their config of the program after update? i have a lot of settings set and i don’t want that to happen.

Hi, it didn’t happen here. But (as said by Dave) you can always export/import your settings.

Oh yeah, I forgot I can backup :).

[strakl]

I have upgraded to the latest beta, no issues so far.

[Asyn]

Note, just got updated to Beta 21.1.2445 - no thread/changelog yet.

[schmidthouse]

Auto Update received. 21.1.2445
All good so far