Beta 2251 released

[hectic-mmv]

Hello,

we have just released new beta version 2016.11.1.2249.

Major changes:

• for Win8+ replacement of Firewall AswNdis driver by new driver - AswNetSec.sys based on WFP
• all binaries are now signed according to new MS security recommendations
  – http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx
  –If you see any problems with installation or not working Firewall after update, please report to us.
• improved DeepScreen (NG) performance
• “Improved OpenVPN connection method for SecureLine VPN. Connection setup should be 2x faster. Please try to connect and give us your feedback”

Find installers here:

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

thanks,
Avast Team

[Rednose]

Thanks for creating a new topic this time

Greetz, Red.

[Secondmineboy]

I hope youre gonna improve the detection and performance of DeepScreen (NG) much further, same for your cloud backend, phishing protection and hopefully the HIPS improvement will come soon

[hectic-mmv]

@Rednose post:2

Thanks for creating a new topic this time

Greetz, Red.

We would like to release beta once per week, what whould you prefer, 1 post for each beta or 1 post when beta1 for release is out and continue posting into this post until release?

[irongod]

@Rednose post:2

Thanks for creating a new topic this time

Greetz, Red.

Hurraa!!!

[irongod]

@hectic-mmv post:4

We would like to release beta once per week, what whould you prefer, 1 post for each beta or 1 post when beta1 for release is out and continue posting into this post until release?

In my opinion both are good solutions. Only one suggestion: in case you decide to keep one post for n betas up to the RC, I think it’s better if the post title reports the current release number .2xxx that is changed everytime a new beta is added

[DavidR]

@irongod post:6

@hectic-mmv post:4

We would like to release beta once per week, what whould you prefer, 1 post for each beta or 1 post when beta1 for release is out and continue posting into this post until release?

In my opinion both are good solutions. Only one suggestion: in case you decide to keep one post for n betas up to the RC, I think it’s better if the post title reports the current release number .2xxx that is changed everytime a new beta is added

Personally I feel it should be a new topic for each new beta release.

Simply changing the beta topic, doesn’t change the previous posts Title only subsequent posts Title. Also any previous issues in a beta would still be in the now current beta version. I think this could lead to confusion, not to mention the topic posts could soon get very big, making it hard to navigate and people aren’t really going to read the whole topic to catch up to where we are…

[Dwarden]

I think ideal would be read-only sticky with the on-going changelog (updated with new ones)

and then new thread per each new beta

[Asyn]

@DavidR post:7

Personally I feel it should be a new topic for each new beta release.

+1

[Rednose]

@Dwarden post:8

I think ideal would be read-only sticky with the on-going changelog (updated with new ones)

and then new thread per each new beta

Not a bad idea : It would be easier to keep track on what has been changed/fixed earlier.

Greetz, Red.

[RejZoR]

Is the new firewall driver also used for anything else (Web Shield etc) or just for actual firewall?

[MartinK]

New driver is part of firewall only. It is not related to webshield etc.

[RejZoR]

Why did avast! beta installer offer “avast Virtual Machines” on my crappy laptop but didn’t on my powerhouse PC with Core i7 5820K and 32GB RAM?

Same thing I’ve noticed with stable builds. I just don’t have avast! VM, the NG version of DeepScreen. And I have all virtualization enabled in BIOS for my CPU. Virtualization and that VT-x or whatever it is.

[lukor]

Hi Rejzor, and what aboud disks? SSDs on laptop or desktop?

[Patrick2]

Yeah Noticed even on my newer System, AMD FX 8310 8 core processor, Virtulization says Enabled, on Windows 10 Home 64bit, yet don’t even have Secure Virtual Machines even listed when I installed Avast on this newer System. Standard 7200RPm 2tb hard drive, not SSD as yet, supports Virtulization, task manager shows enabled

[RejZoR]

@lukor post:14

Hi Rejzor, and what aboud disks? SSDs on laptop or desktop?

Laptop has SSD, but it’s so stupendously slow due to crappy CPU it just makes no sense.

PC on the other hand has a speedy 2TB 7200RPM HDD with a M.2 AHCI SSD cache (using PrimoCache software). Essentially what I have is SSHD.

I did notice that Windows Resource Monitor doesn’t show any Read activity (it’s just blank) for disk. It doesn’t list apps and how much disk reading they are doing. Could this be the reason why avast! thinks my disk is too slow and refuses to activate Secure Virtual Machines? Apparently has something to do with how PrimoCache hooks in between HDD and SSD to form a SSHD “array”.

Why can’t we just have a damn override for this thing so I can manually enable it and be done with it forever? I’m tired of this thing disabling itself because its detection mechanism seems wonky or doesn’t predict scenarios like I have.

PrimoCache:
https://www.romexsoftware.com/en-us/primo-cache/

[essexboy]

Same here have not had NG for nearly 6 months

[skinnypops]

ditto!

[RejZoR]

They’ve fixed this long ago and apparently broke it again. And it used to work just fine on my HDD.

[Asyn]

Hi guys, (atm) you need a SSD for NG to work, afaik.