Author Topic: some files could not be scanned  (Read 2268 times)

0 Members and 1 Guest are viewing this topic.

weihanwang

  • Guest
some files could not be scanned
« on: August 27, 2011, 10:35:55 PM »
I have this problem, and the files that can't be scanned are actually avast's own files, like C:\program files\avast software\avast\defs\11070401\algo.dll or \aswcmnbs.dll or\aswscan.dll or\aswcmnis.dll or\aswcmnos.dll or \aswengin.dll.  I just installed avast today, and this is the first scan I ran immediately after the installation.  Should I be concerned about possibly a trojan?

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37561
  • Not a avast user
Re: some files could not be scanned
« Reply #1 on: August 27, 2011, 10:43:19 PM »
files that can not be scanned are just that.....it does not mean they are infected
there can be many reasons why files can not be scanned, password protected or protected by another security program installed.....

if they are all in avast def folder i guess you did a scan right after avast did a cleanup in the def folder..so some files are gone
reboot scan again and i guess it is gone....
« Last Edit: August 27, 2011, 10:45:35 PM by Pondus »

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76035
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: some files could not be scanned
« Reply #2 on: August 27, 2011, 10:44:07 PM »
Should I be concerned about possibly a trojan?

No.
Old avast! defintions - Nothing to worry about.
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89186
  • No support PMs thanks
Re: some files could not be scanned
« Reply #3 on: August 27, 2011, 10:59:26 PM »
- Nothing to worry about, those are files in old virus definitions folders and avast is doing some housecleaning to keep the size used on the hard disk to a minimum. This just happens to have occurred between the time you started the scan and it reaching that old defs folder.
« Last Edit: August 27, 2011, 11:04:25 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 24.4.6112 (build 24.4.9067.762) UI 1.0.803/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security