Author Topic: Files couldn't be scanned, sliding malfunction  (Read 6296 times)

0 Members and 1 Guest are viewing this topic.

Offline ehmen

  • Poster
  • *
  • Posts: 498
Re: some files could not be scanned
« Reply #15 on: June 05, 2015, 07:38:43 PM »
If Avast reports at the end of a scan that "some files could not be scanned", will it also notify the user if it detected other malicious files as well (in addition to those it can't access), or will it get "distracted" as it ware, and only report those files that come up as: "Error: Archive is password protected" ?

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89336
  • No support PMs thanks
Re: Files couldn't be scanned, sliding malfunction
« Reply #16 on: June 05, 2015, 08:35:33 PM »
I just scanned "C:\Program Files\Clearwire\Connection Manager\CWMultiModePlus.skx" (that Avast couldn't scan) with MBAM and SAS and they both claim in their reports they scanned it.

Do they actually say that these were scanned or don't list them as having not been scanned. Many AVs don't list files that weren't scanned and why, avast however list files that couldn't be scanned and why.

If Avast reports at the end of a scan that "some files could not be scanned", will it also notify the user if it detected other malicious files as well (in addition to those it can't access), or will it get "distracted" as it ware, and only report those files that come up as: "Error: Archive is password protected" ?

The scan report lists everything, infected files found and files that couldn't be scanned.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.5.6116 (build 24.5.9153.762) UI 1.0.808/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security