Author Topic: Files could not be scanned  (Read 9488 times)

0 Members and 1 Guest are viewing this topic.

ronnycopeh

  • Guest
Files could not be scanned
« on: January 01, 2009, 01:30:54 AM »
I did a scan and there was a lot of files that could not be scanned, attached is the cleaner log file. Is this the norm or is something wrong somewhere? thanks for any help

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89061
  • No support PMs thanks
Re: Files could not be scanned
« Reply #1 on: January 01, 2009, 03:10:34 AM »
Well none of these look suspicious, avast normally gives the reason why a file can't be scanned (there are many legit reasons) and that is in the Home version, so I'm surprised at the lessor info of the Pro version log.

See http://forum.avast.com/index.php?topic=35347.msg297170#msg297170 this topic for more information on why files can't be scanned. Was there a pop-up list displayed after the scan with these files (this is where the Home version displays files unable to be scanned and why) ?

Unfortunately, the above like will be of little use as you can't really compare as you haven't been given a reason why they can't be scanned.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

ronnycopeh

  • Guest
Re: Files could not be scanned
« Reply #2 on: January 01, 2009, 03:54:41 AM »
That log was from the virus cleaner in avast, I just ran a scan from the task within avast the first thing was *BOOTC: unable to scan. no more data is available, but it continue to scan my pc and found nothing.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: Files could not be scanned
« Reply #3 on: January 01, 2009, 01:34:11 PM »
*BOOTC: unable to scan.
Strange... avast was not able to scan the boot sector of the drive C ::)
Did you run avast at boot time?
The best things in life are free.

ronnycopeh

  • Guest
Re: Files could not be scanned
« Reply #4 on: January 01, 2009, 01:52:09 PM »
No, I didn't but I do it and report back

ronnycopeh

  • Guest
Re: Files could not be scanned
« Reply #5 on: January 01, 2009, 03:51:38 PM »
I did a boot scan and this is what the report says, How to I repair this?

01/01/2009 08:54
Scan of all local drives

File C:\Windows\System32\dgmcrrx.dll is infected by Win32:Fasec [trj], Repair: Error 42060 {The file was not repaired.}
Number of searched folders: 13925
Number of tested files: 89055
Number of infected files: 1

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: Files could not be scanned
« Reply #6 on: January 01, 2009, 03:52:46 PM »
A lot of files can't be repaired. In fact, only few executables that are present in the VRDB could.
Move the file to Chest for further analysis. It's a dll.
The best things in life are free.

ronnycopeh

  • Guest
Re: Files could not be scanned
« Reply #7 on: January 01, 2009, 03:57:22 PM »
Okay, please tell me how do I do that, it scanned at boot and I don't see what I'l suppose to do, need help here, how do I get rid of it anyway

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89061
  • No support PMs thanks
Re: Files could not be scanned
« Reply #8 on: January 01, 2009, 04:33:22 PM »
Well if you were able to select Repair, you would equally have been able to select the number for Sent to Chest. In the boot time scan you should get a screen like this when something is detected, chose the number for Send to Chest.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: Files could not be scanned
« Reply #9 on: January 01, 2009, 06:14:10 PM »
Okay, please tell me how do I do that, it scanned at boot and I don't see what I'l suppose to do, need help here, how do I get rid of it anyway
It's not possible to repair.
You should be able to send file to Chest at boot time (see the picture David posted).
The best things in life are free.

ronnycopeh

  • Guest
Re: Files could not be scanned
« Reply #10 on: January 01, 2009, 06:40:19 PM »
Thank you all so much and Happy New years, I finally got all the stuff repaired, I was searching and found a program called combo fix and it scanned, found, delete and repaired the drive, now it scans the boot and defrags the drive. I have avast with 3 shields running, mail, web, & standard and all thats listed in my signature and I wonder how I still got this, but you all were so helpful and thanks again.

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89061
  • No support PMs thanks
Re: Files could not be scanned
« Reply #11 on: January 01, 2009, 07:51:18 PM »
I would enable the Network Shield as it now has extra functionality, e.g. blocking known sites that can infect your system.

You don't say what combofix found (file name, location and malware name), so it is hard to speculate how something got on your system.

Commonly things get on your system through vulnerabilities in out of date software, JAVA being a very common one. I would also suggest a visit to this site, which scans your system for out of date programs that have patches to close vulnerabilities, http://secunia.com/software_inspector/.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

ronnycopeh

  • Guest
Re: Files could not be scanned
« Reply #12 on: January 01, 2009, 08:06:10 PM »
What it found was the same thing avast did but it cleaned and deleted it "File C:\Windows\System32\dgmcrrx.dll is infected by Win32:Fasec [trj], Repair: Error 42060 {The file was not repaired.}"

I usually try and keep all my drivers and software up to date but I know they are updated daily and thanks. I have java set to keep updated, so it up to date.

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89061
  • No support PMs thanks
Re: Files could not be scanned
« Reply #13 on: January 01, 2009, 08:13:16 PM »
An avast boot-time scan is likely to have been able to detect and move to the chest (rather than the failed repair attempt in the boot-time scan).

You would be surprised what software is found to have an out of date version, which could leave you vulnerable, acrobat, windows media player, etc... The actual scan doesn't take long at all.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

ronnycopeh

  • Guest
Re: Files could not be scanned
« Reply #14 on: January 01, 2009, 08:38:07 PM »
Thanks just did the scan, the only thing it found was that my java was outdated, but I had just went to java verify and it said I had the latest version so I decided to download from secunia results and it said the program was already installed would I like to reinstall, so I see their scans are not to accurate but thanks I'll add the network shield