Author Topic: Unable to scan  (Read 964 times)

0 Members and 1 Guest are viewing this topic.

Offline rospci

  • Newbie
  • *
  • Posts: 1
Unable to scan
« on: September 25, 2019, 11:03:11 PM »
Full System Scan found 0 infections and 17 files unable to scan.
How can I identify the files that cannot be scanned?

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37504
  • Not a avast user
Re: Unable to scan
« Reply #1 on: September 25, 2019, 11:10:43 PM »
Quote
How can I identify the files that cannot be scanned?
Ignore it, avast is just telling you it could not scan those files for whatever reason (there can be many) and there is nothing you can do about it. This is something that happens with all security programs but it is not all that display it in the log.
It is also something avast is planning to remove

It does NOT mean they are infected


Here is some info from 2014   https://blog.avast.com/2014/02/28/how-do-i-handle-files-that-avast-cant-scan/


« Last Edit: September 25, 2019, 11:15:20 PM by Pondus »

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88895
  • No support PMs thanks
Re: Unable to scan
« Reply #2 on: September 25, 2019, 11:50:24 PM »
Full System Scan found 0 infections and 17 files unable to scan.
How can I identify the files that cannot be scanned?

Have you looked in the Scan History ?
AvastUI > Protection > Virus Scans > Scan History. 
This assumes that you have elected to Generate report file in the scan settings (or that is the default).
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security