Author Topic: Is "Warn when downloading files with poor reputation" still functioning?  (Read 1798 times)

0 Members and 1 Guest are viewing this topic.

Offline Evjls

  • Jr. Member
  • **
  • Posts: 96
hello everyone,

For a long period of time since avast updated to the new UI, I haven't seen "warn when downloading files with poor reputation" working or notifying even once

I have done some testing with newly updated projects in SourceForge or some download websites, usually avast warns at least 1 download as poor reputation. However, until now, I have downloaded ~30 of them but received no notification from avast

So my question is "warn when downloading files with poor reputation" still functioning? How to verify that it's still working correctly

Thank you

Version: avast free 18.5
OS: windows 10x64 v1511

Offline NON

  • Japanese User
  • Avast Überevangelist
  • Massive Poster
  • *****
  • Posts: 4452
  • Whatever will be, will be.
I didn't see it neither recently. It looks like last warning was issued at Dec 2017 for me...
Main: Win10 Pro 2004 64bit / Core i5-7400 3.0GHz / 16GB RAM / Avast 20 Premier Beta / Comodo Firewall 12
Mobile: Win10 Pro 1903 32bit, Vista SP2 32bit / Core 2 Duo SU9300 1.2GHz / 4GB RAM / Avast 20 Free / Windows Firewall Control

Avast の設定について解説しています。よろしければご覧ください。

Offline Alikhan

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2234
I've contacted a developer of the Web Shield regarding this and they have said it should still be working.

The dev will do more research and update the thread when it is completed.
Windows 10 Home 64-bit • Avast Free (latest stable version) •  Malwarebytes 4 Premium (On-Demand) • Windows Firewall Control • Google Chrome • LastPass • CCleaner • O&O ShutUp10 •

Offline Filip Braun

  • Avast team
  • Jr. Member
  • *
  • Posts: 98
Hello,

Thanks for the report.
Due to some changes in scanning approach this feature currently works only when File Shield is OFF (which I do not recommend :) ).
We are discussing the future of this feature and will see whether it is still worth having there.

Regards,
Filip
« Last Edit: June 22, 2018, 12:03:46 PM by Filip Braun »

Offline Evjls

  • Jr. Member
  • **
  • Posts: 96
Hello,

Thanks for the report.
Due to some changes in scanning approach this feature currently works only when File Shield is OFF (which I do not recommend :) ).
We are discussing the future of this feature and will see whether it is still worth having there.

Regards,
Filip
thank you for your reply :)
Please, keep this feature because it's extremely helpful in detecting zero-day malwares. It may help detecting malware downloaded by scripts (.js, .vbs, .jar, .cmd) where they can bypass hardened mode

It works very similarly to Norton's download insight, which they are very proud of

Offline MartinZ

  • Moderator
  • Advanced Poster
  • *
  • Posts: 1069
  • Product Manager
This functionality of course stays, it's just part of web shield. no more settings needed for it.

Offline Evjls

  • Jr. Member
  • **
  • Posts: 96
thank you for your replies
I know this might be not a good question but would it be fixed in the next version update?

Thank you

Offline MartinZ

  • Moderator
  • Advanced Poster
  • *
  • Posts: 1069
  • Product Manager
yes, in next version the setting will be removed

Offline Evjls

  • Jr. Member
  • **
  • Posts: 96
yes, in next version the setting will be removed
sorry but I don't understand this sentence. Could you please clarify it a bit?

in the next version, the setting will be removed so it means either:
1/ the feature of "warn..." will be enabled by default -> users can't disable it anymore if they want to
2/ it will be also removed forever

Offline MartinZ

  • Moderator
  • Advanced Poster
  • *
  • Posts: 1069
  • Product Manager
1/ is correct

Offline Evjls

  • Jr. Member
  • **
  • Posts: 96
Re: Is "Warn when downloading files with poor reputation" still functioning?
« Reply #10 on: August 30, 2018, 10:52:52 AM »
this feature still hasn't worked in the latest version unless file shield is disabled
I don't see it in the changelog :(