Author Topic: "files could not be scanned" in AVG's own folder  (Read 2924 times)

0 Members and 1 Guest are viewing this topic.

clamage45

  • Guest
"files could not be scanned" in AVG's own folder
« on: August 03, 2013, 04:36:59 PM »
Every time the scan runs, AVG complains about password-protected files in its own data directory. (Ignore the complaint about drive G, it is not a Windows file system.) Should I delete these files, or just ignore the complaints, or what?
« Last Edit: August 03, 2013, 04:49:48 PM by clamage45 »

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: "files could not be scanned" in AVG's own folder
« Reply #1 on: August 03, 2013, 04:41:11 PM »
No idea as I use Avast

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37529
  • Not a avast user
Re: "files could not be scanned" in AVG's own folder
« Reply #2 on: August 03, 2013, 04:42:36 PM »
Quote
AVG complains about password-protected files in its own data directory
you mean avast.....as the picture is from a avast scan...

general info on files not scanned  http://forum.avast.com/index.php?topic=131504.0

however it seems you have avast and AVG installed
never install multiple antivirus, this will give you a slow machine, windows errors and false detections

so uninstall one, the run the vendors removal tool to clear any leftover files that may conflict
tools found here  http://singularlabs.com/uninstallers/security-software/


« Last Edit: August 03, 2013, 05:10:24 PM by Pondus »

clamage45

  • Guest
Re: "files could not be scanned" in AVG's own folder
« Reply #3 on: August 03, 2013, 04:48:53 PM »
Doh! I forgot that AVG and Avast are not the same thing. I used to have AVG but uninstalled it before installing Avast. The program data files must have been left behind.

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: "files could not be scanned" in AVG's own folder
« Reply #4 on: August 03, 2013, 05:02:45 PM »
Duh I just saw AVG and totally failed to notice which programme detected them  :-[

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6700
  • Trust only what you test yourself!
Re: "files could not be scanned" in AVG's own folder
« Reply #5 on: August 03, 2013, 05:06:58 PM »
Duh I just saw AVG and totally failed to notice which programme detected them  :-[
Thanks essexboy! I don't feels so bad when "I" miss something.

@ the OP have you tried to clean-up the leftovers with CCleaner?  ???
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37529
  • Not a avast user
Re: "files could not be scanned" in AVG's own folder
« Reply #6 on: August 03, 2013, 05:14:32 PM »
Quote
@ the OP have you tried to clean-up the leftovers with CCleaner?
the vendors removal tool is the one to use....that is what they are made fore


Quote
AVG Remover eliminates all the parts of your AVG installation from your computer, including registry items, installation files, user files, etc. AVG Remover is the last option to be used in case the AVG uninstall / repair installation process has failed repeatedly.