Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: petr.chytil on June 14, 2016, 04:34:53 PM
-
Hi all,
new beta version is live: 2016.12.1.2270
As we are getting closer to release, please expect beta builds to come with higher frequency and shorter changelogs.
Changes:
+ Fixed service crashes caused by the new implementation of Web Shield
+ The new implementation of Web Shield is now fully turned on, please report any issues with browsing or with downloads
+ Fixed explorer scan settings - it is now possible to edit and save settings for this scan
+ Updated translations
Known issues:
- Registration to the Windows security center may still have some issues
- Highest HIPS sensitivity setting can prevent user from logging into Windows
Download links as usual or just update your current beta.
Enjoy,
Petr
-
+ Fixed explorer scan settings - it is now possible to edit and save settings for this scan.Thanks for quick fix.What happend to Ransomware protection & HIPS Improvments?
-
+ Fixed explorer scan settings - it is now possible to edit and save settings for this scan.Thanks for quick fix.What happend to Ransomware protection & HIPS Improvments?
Dito.
-
I still don't understand how CyberCapture works (I understand the basics, I don't understand the specifics). The part to which files it reacts. From what I've heard from one avast! team member, it only acts on files that are a link on the web. If it's a new unknown file from USB drive or local disk, it will not do anything. Is this true?
-
Soon I return to the forum.I did a test yesterday with zero day files received in email.CyberCapture
did virtually nothing to what at least understand works only for executable as well as Deepscreen.The VBS files, VBE and JS no reaction, it will be introduced in a next beta ?
https://virusscan.jotti.org/en-US/filescanjob/mszygoto5j
https://www.virustotal.com/en/file/43fb22edcd56ef805356d77c8c0e3faccff2e518e6928a1010c5c46c2841519e/analysis/1465938388/
-
Soon I return to the forum.I did a test yesterday with zero day files received in email.CyberCapture
did virtually nothing to what at least understand works only for executable as well as Deepscreen.The VBS files, VBE and JS no reaction, it will be introduced in a next beta ?
https://virusscan.jotti.org/en-US/filescanjob/mszygoto5j
https://www.virustotal.com/en/file/43fb22edcd56ef805356d77c8c0e3faccff2e518e6928a1010c5c46c2841519e/analysis/1465938388/
VBS, VBE, PHP, JS ... are not executable so they can't be detect as program by cloud/cypercapture.
VBS/VBE are Windows Scripting Host so it is legitim (program)
PHP/JS/HTML are file by Firefox/IE/Chrome so it is legitim (program)
Sorry for bad english
-
VBS, VBE, PHP, JS ... are not executable so they can't be detect as program by cloud/cypercapture.
VBS/VBE are Windows Scripting Host so it is legitim (program)
PHP/JS/HTML are file by Firefox/IE/Chrome so it is legitim (program)
Sorry for bad english
You are misunderstanding this examples are not is files legitimate,received by e-mail box with targeted for phishing sites, Bankers etc.I know they are not executable,but also modified the extension of the files to exe and tested there was no action,not blocked by Hardened mode.
-
Well, I know some vendors use VM to analyze scripts and other stuff that isn't EXE files...
-
Well, I know some vendors use VM to analyze scripts and other stuff that isn't EXE files...
that's good point and hopefully Avast! will do it sooner than later too ...
-
The new implementation of Web Shield is now fully turned on, please report any issues with browsing or with downloads
I get quite a few disconnects (LAN), lately.
Usually, it doesn't happen here at all or only very seldom.
I wonder if the new implementation of WS could be the reason..!?
-
Thanks for the update, hopefully there is some advance in HIPS issue.
-
After updating to Wind. preview release 14366, the following things occurred:
1. Avast UI opened after the update
2. My license to SecureLine was not recognized by the Avast server.
A repair seems to have fixed the exceptions.