Author Topic: registry files can not be scanned  (Read 2163 times)

0 Members and 1 Guest are viewing this topic.

Sick Nasty

  • Guest
registry files can not be scanned
« on: February 25, 2009, 08:57:26 PM »
When I run a scan on my C:/ I get some files reported as un-scanable due to password protection.  I tried to run in safemode but got the same issue. 

Is this a problem? They look like registry entries.

Spiritsongs

  • Guest
Re: registry files can not be scanned
« Reply #1 on: February 25, 2009, 09:02:59 PM »
 :)  Hi :

 More than likely your Question(s) are answered in our "FAQs" at
 www.avast.com/eng/faq-avast-4-home-professional.html !? Have you at
 least "browse" through them ? Perhaps it is what is posted there, as follows :
 "Q: When the file scanning is finished, avast! comes up with a number of files listed as "unable to scan", even though I have used a thorough scan. Should I be concerned?

A: Some files are permanently locked by the system or they are in password-protected archives. These files cannot be scanned. It is normal and you donĀ“t have to be worried about that. "

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: registry files can not be scanned
« Reply #2 on: February 25, 2009, 10:53:57 PM »
avast can't scan files that are password protected, it doesn't know the password.
There are many legitimate reasons why a file was password protected. For instance, Lavasoft Ad-aware and SpyBot store their data in a password-protected ZIP archives (to prevent other similar tools from messing up with them). It's really nothing to worry about - it's normal.

In AdAware and S&D, when you fix/remove things it keeps backup/recovery information so you can restore anything that was mistakenly fixed/removed, etc. After a reasonable time your system has suffered no adverse effects, you can get rid of the older recovery/backup points. This should reduce the number of protected files.

By examining 1) the reason given by avast! for not being able to scan the files, 2) the location of the files, you can get an idea of what program they relate to. You may need to expand the column headings to see all the text.

Files that can't be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned.
Also, the packaging of the file could have some error, or use a non-standard pattern...
The best things in life are free.