New beta version 20.2.2400

Consumer Products Public Beta Avast Antivirus Beta
1

Hi everyone,

I`m glad to announce that new beta version is ready - 20.2.2400 (build 20.2.5125).

What was fixed
Fixed issue with firewall blocking PPTP and L2TP traffic
Fixed issue with failed installation on Windows 10 caused by windows update pending (user will be informed that he has to restart PC to successfully install AV)

Known issues
Http communication can be blocked 1 minute after installation (Windows 8.1)
Sensitive data shield does not work

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.

2

Thanks Jan, testing…

3

Good news, the stats are (finally) back…!! :slight_smile: (UI.501)

4

+1
Got it, thanks :slight_smile:

5

Thank goodness for the bloody stats are (finally) back…!!

6

thanks for the update do you think we will have the graphics as the old version of avast in the statistics?

7

Testing it now. First 2 reboots after installation some errors were logged by windows about various services not responding / starting up. On the 3rd boot these errors did not happen. Will post back if I see anything else.

Thank you.

8

It’s not uncommon to have to reboot a few times before all drivers/etc to settle in.
Especially with Security software :slight_smile:

9

I agree, and I am happy to update that report a little, the system is solid, feels solid. I am going to go out on a limb and say this is a big improvement for Win 10 over the 20.1.

10

Thanks for the new beta :slight_smile:

Working fine so far.

11

When it’s ready… :wink:

12

So i experienced more windows startup errors…the most concerning one said that the user profile service was locked by avast. After that i started seeing really slow boot up. Not sure but I think something got corrupted. So I took the following steps, uninstalled avast, system restore, restored windows to before avast installation, and reinstalled Avast but AFTER FIRST disabling windows defender. Much better. Defender was disabled with following registry entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender]
“DisableAntiSpyware”=dword:00000001

13

@ Jimbo93
Is your post related to this beta build in the forum subject ?

If so, you might want to check out the new beta build that has just been released, see https://forum.avast.com/index.php?topic=233071.0

14

Thanks. Already updated to it. It was interesting that after the update the above mentioned registry tweak was removed. I put it back because right away I started getting the crap on reboot.

15

My guess would be that this is being added by either Microsoft or you’re Defender settings.

I did a search on the error message and got this: https://www.google.co.uk/search?q=HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows+Defender]+“DisableAntiSpyware”%3Ddword%3A00000001
Some possibles there.

A point of note or two:

  1. You shouldn’t need to disable Defender to install Avast.
  2. Related - Avast doesn’t actually disable Defender, that is done by the OS. So something strange happening there.

You said “reinstalled Avast but AFTER FIRST disabling windows defender.” how did you do that, in the OS settings of by creating the registry key ?

Check your OS Virus & Threat Protection settings > Windows Defender Antivirus options - I also switch off the Periodic Scanning function.

16

I added the registry key and set it to 1. Please note that this was originally suggested by avast customer support. I posted about it maybe a month or two ago. Based on 2 months of troubleshooting it’s either put that in the registry or stop using avast.

17

Well changing the setting as suggested above disabling Defender from within windows could well be the better (windows OS) option. Your change to the registry would I guess be a limited permission level (even if done as an Administrator) and may be changed by the OS.

I’m fairly sure that when you uninstalled Avast the OS would probably get involved in changing back to Defender enabled (in much the same way it disabled Defender when you install a third party AV), resulting in this registry entry being deleted or modified.

I have that registry key on my win10 Home version 1909 64bit laptop and I never had to set it manually, so I don’t really know why it is occurring on your win10 Home system

18

Thanks for adding your thoughts. A couple things i want to clarify…i only had to add the value name in right pane, and the issues dont become acute untl after 5 to 10 boots after installation. What is happening apparently is that windows in trying to optimize boot order, keeps changing things around. Avast boot order never settles down when defender is enabled. Never had this issue with windows 7, and never zeroed in on it till i had been running win 10 for a few months, although the errors would happen, i ignored them.

19

I haven’t experienced that, but I haven’t had the symptoms you mentioned so I haven’t gone hunting for it.

As I mentioned I don’t think that this is Avast beta related, so it would probably have been better in its own topic keeping it all together rather than getting mixed in with beta comments.