Author Topic: "Some Files Could Not Be Scanned"... AWS Files??  (Read 3294 times)

0 Members and 1 Guest are viewing this topic.

Offline The Sniggler

  • Full Member
  • ***
  • Posts: 120
"Some Files Could Not Be Scanned"... AWS Files??
« on: December 12, 2012, 11:10:41 PM »
Periodically, when doing a full scan, Avast reports some files could not be scanned. When I look into what those files are, it is always a series of AWS files with an invalid path. What's this all about?
Thanks

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37005
Re: "Some Files Could Not Be Scanned"... AWS Files??
« Reply #1 on: December 12, 2012, 11:14:34 PM »
is it located in avast/defs.....folder?

it sometimes happens if you do a scan right after avast have done some house cleaning in the definition folder..
if you reboot and scan again it should be gone.....is it?

Offline The Sniggler

  • Full Member
  • ***
  • Posts: 120
Re: Now Won't Update Again "Some Files Could Not Be Scanned"... AWS Files??
« Reply #2 on: December 14, 2012, 04:29:33 PM »
Thanks for your reply.

I noticed that the files not scannned appeared after Avast updated def file, and files not scanned  had a broken file path error, C: Program Files.... so I uninstalled Avast with the uninstall tool in Safe Mode and reinstalled Avast. Did this twice and used CCleaner to make sure all was wiped off.

Now, the fresh install of Avast WILL NOT UPDATE!!!.  Stuck on initializing -- again!. Went to Control Panel and tried repair. Rebooting shows today's def file instead of yesterday, but still hung on initializing.
Have no idea what is going on... never even got to the files not scanned issue.

What gives?
« Last Edit: December 14, 2012, 04:45:05 PM by The Sniggler »

Offline Slawek

  • Newbie
  • *
  • Posts: 11
Re: "Some Files Could Not Be Scanned"... AWS Files??
« Reply #3 on: December 14, 2012, 06:03:14 PM »
I get this too!  Except mine is Chrome user data folder, cache files, they are all password protected so it can't scan.

What should I do?  Right now I Just ignored it...

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84864
  • No support PMs thanks
Re: "Some Files Could Not Be Scanned"... AWS Files??
« Reply #4 on: December 14, 2012, 06:17:14 PM »
Ignore is the correct option. You don't know the password, avast doesn't know the password (only chrome would), so nothing that you or avast can do about that.

Files that can't be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline The Sniggler

  • Full Member
  • ***
  • Posts: 120
Re: "Some Files Could Not Be Scanned"... AWS Files??
« Reply #5 on: December 14, 2012, 06:28:58 PM »
OK.... but what about the update situation??

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84864
  • No support PMs thanks
Re: "Some Files Could Not Be Scanned"... AWS Files??
« Reply #6 on: December 14, 2012, 08:32:58 PM »
My reply was directly to the post above mine otherwise I would the Quote function.

Did the repair report any errors ?

Did you reboot after the repair, if not do so. Whilst it isn't entirely necessary it is worthwhile as a reboot may also resolve that problem.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline The Sniggler

  • Full Member
  • ***
  • Posts: 120
Re: "Some Files Could Not Be Scanned"... AWS Files??
« Reply #7 on: December 17, 2012, 05:21:19 PM »
OK.. finally got it all working, thanks for your help. Subsequent scans do not report files not scanned. Repair did not report any errors.

Also, pulled AVG off a Vista machine, what a hassle to remove AVG. Long waits for reboots and cryptic DOS type messages. Avast Removal Tool is more user friendly. Vista machine working OK, so far. No apparent update problems... again thanks!

One more XP machine to go!!!


Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84864
  • No support PMs thanks
Re: "Some Files Could Not Be Scanned"... AWS Files??
« Reply #8 on: December 17, 2012, 06:37:47 PM »
You're welcome.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security