avast! don't repair files

[ant222]

Hello, all!

My OS: win98se;
Hardware: celeron 766, 256 Mb RAM;
avast! version: 4.1 Professional, build 4.1.357;


I have the following problem. When avast! finds an infected file it
offers me to choose what to do to it. All the options are performed
successfully except repair. When I try to repair the file I got this
message: "Cannot process "d:\tmp\dc1.exe" file". The caption of the
message box reads: "avast!: The file was not repaired." I have met
this problem three times with different files and viruses. avast!
successfully deleted that files after failure to reapir them. That is
strange.

Thanks in advance,
Anton

[ant222]

Oh, I mistaken. Instead of "Cannot process d:\tmp\dc1.exe" one should read: "Cannot process d:\tmp\<infcted file>", where <infected file> is the file avast! found infected.

[MikeBCda]

Hi,

The most obvious possibility is that your Repair "engine" may be damaged or missing -- see if you can find  clnr0.dll, it should be in an avast sub-folder under Window/Temp.  If it's missing, try repairing avast (under add/remove programs) and see if that replaces it.

Next most likely is that <infected> was added too recently to be in your VRDB, which is what Repair looks to for the good data.  It might be a legit new file that got infected afterwards, or it might have been added by the virus itself.  Take a look at its Properties/Version to see if that gives you any clues.  In either case you'll want to delete it, and if it's from a legit program you'll probably want to re-install that (after scanning the installer, of course).

Hopefully that'll give you some things to try.

Best,
Mike

[Lisandro]

Mike is right (as usual)  
You may not have that dll at your temp folder (it is the avast Cleaner application).
If you only boot, the dll must 'come back' to that folder.

Other posibility is that you are working with 'temp' files and they were deleted before avast could repair it.

Btw, was that your default temporary folder?

[MikeBCda]

Mike is right (as usual)  

Thanks, Technical, but you're gonna make me conceited yet, with your flattery.  And I can't be conceited, that's a personality defect.  

[Vlk]

More likely, it was a WORM (not a pedigree VIRUS). One of the differences between those two is that for worms, REPAIR more or less equals to DELETE (i.e. worms do not infect existing files, the "infected files" are the worms themselves - so there is nothing to "repair"...).


Hope this helps,
Vlk

[ant222]

Thank you very much!
The problem was caused by the VRDB not fresh enough. I should have read the help file before posting this question.

Anton Shepelev