Win32:agent Error in aswChestC: chest add file error 1753

[njguy99007]

Can anyone tell me what this erro means and did the trojan move or not?
I ran a fill scan in Sfae Mode and found 3 with this error.
Win32:adwarw-Gen and Win32:Agebt,fhr is my system still infected.
When I tried to move them seperatly I recieved an error.

[Lisandro]

It's not an avast error itself (http://forum.avast.com/index.php?topic=4818.msg65672#msg65672).
It seems a RPC (Windows) error.
Why don't you search the board for error 1753 and see if any thread helps?

Which is your Windows? 98, Me, XP?
Do you use any other antivirus in your computer?

Can you try to repair your installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove. Then choose Repair function in the popup window (Repair). You must be connected to the internet while repairing.

If this does not help, can you uninstall / boot / install / boot again?

[DavidR]

If it is a windows error 1753="There are no more endpoints available from the endpoint mapper." Whatever that means.

What is the infected file name, where was it found e.g. (C:\windows\system32\infected-file-name.xxx) ? 
Check the avast! Log Viewer (right click the avast icon), Warning section, this contains information on all avast detections.

[njguy99007]

I did a repair, this seemed to fix that issue, hopefully it will stay fixed.
I am running XP home, with the latest and greatest updates.
The error was found in system restore while I was running Avast in safe mode.
Thanks for your help in this matter as usual this forum is great.

[DavidR]

I assume you mean that the infected file was in the c:\System Volume Information folder, which is a part of the system restore function and that when trying to move this to the chest the 'error' occurred ?

If so the file would in theory still be in the c:\System Volume Information folder if the move to chest failed, have you done another scan to see if this is correct or is nothing found ?

[Lisandro]

I did a repair, this seemed to fix that issue, hopefully it will stay fixed.

If you sure you have fixed it, you can disable and then enable System Restore.
This will delete any previous restoration point (with their files, infected if they're infected) and will start the feature again.
Then you can create a new clean restore point.