Author Topic: How important is malware detection and blockage at start-up?  (Read 2095 times)

0 Members and 1 Guest are viewing this topic.

nine9s

  • Guest
Per AV-COmparatives latest performance test, Avast as well as many others do not protect at start-up:

"we test from sporadically in performance tests if the products are loading all their protection modules before e.g. malware in the start-up folder is executed. Several products failed this test, except AVG, Bitdefender, eScan, Kingsoft, Microsoft and Sophos. Those were the only products that detected and blocked the malware before its execution after system start-up"

http://www.av-comparatives.org/performance-tests/

Is this a concern or would it be very rare for malware to happen at start-up?

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 86501
  • No support PMs thanks
Re: How important is malware detection and blockage at start-up?
« Reply #1 on: May 09, 2013, 08:59:45 PM »
I have no idea what they mean by no protection at startup, obviously avast is being started as soon as is possible in the boot and is already scanning way before the avast UI tray icon is in place.
« Last Edit: May 09, 2013, 09:01:23 PM by DavidR »
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.2.6003 (build 22.2.7013.717) UI 1.0.697/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

nine9s

  • Guest
Re: How important is malware detection and blockage at start-up?
« Reply #2 on: May 09, 2013, 09:51:14 PM »
That testing group said all other tested AVs did not detect malware at startup except those mentioned.  I guess other things, including malware, load before the shields first come up at start-up.

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 86501
  • No support PMs thanks
Re: How important is malware detection and blockage at start-up?
« Reply #3 on: May 09, 2013, 11:26:31 PM »
The problem is there is no detailed information on just what that is.

Personally I'm not overly concerned with that as the whole point of a resident AV is to prevent the infection in the first place, so assuming that you were clean when you shutdown it shouldn't be an issue on startup. But I still don't feel avast starts so late as not to be able to stop before execution.

The bigger problem really is if it wasn't detected in the first place for it to be able to run on startup, so if it wasn't before I don't see it getting detected later. And there is no mention if this/these malware samples are/were detected to start of with.

I have been using avast for nine years and not had a single infection.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.2.6003 (build 22.2.7013.717) UI 1.0.697/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security