Some files could not be scanned...because Avast file folder name is offer

I apologize if this appears twice. The forum page claims I already posted this but it’s not showing up on the forum. I tried to submit a screenshot that was too big, and I chose the option to try again with a smaller screen shot, thus eliciting the warning of re-posting (again, even though it hasn’t shown up).

After a full scan, I got the warning that some files could not be scanned. I read lots about it, namely that there are many possible causes, and that it is generally not a cause for concern. However, I never got that message before, and I haven’t made any significant changes to my system. Upon closer inspection, I found that all the files were Avast files (see attached image), and that the reason for the problem is that the path could not be found. So I tried to browse to that path and found that the folder containing all the problem files did not exist: /c/Program\ Files/Alwil\ Software/Avast5/defs/11042101 . Instead, the folder 11042200 existed, containing the problem files. Sounds like a version problem, I thought. I checked About Avast! and found the virus definition version to be 110422-0.

Perhaps this problem is because the time of the scan overlaps with the virus definition update. I don’t have full control over either. In particular, the scan occured at a unpredictable time…namely, when I log in. This scan seems to be a delay of the scan scheduled for 5am. The scheduled 5am scans sometimes occur on schedule, sometimes not. When they do not, they seem to launch when I log in (or wake up from standby).

This has been discussed many times in the forums.

  • Nothing to worry about, those are 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.

Ah, yes, I see them now (the notification as they pertain to Avast DLL’s). My initial search was simply for the notification only, so I did not see the postings about the notification as it pertained to Avast DLLs.

Thanks.

You’re welcome.