Hello DavidR
Thanks for answering:
The index.xml in the chest isn't infected it is there for information on the contents of the chest as files sent there are a) encrypted and b) have the name changed. These measures are to prevent outside access to infected files in the chest.
I am trying to be EXTRA cautious;
also when I open the *.xml file I get a warning from MS I.E. re: the file "blocked from running scripts etc." etc.
I have 9 items from definable sources in the chest:
I wanted to record details about the 9 items: what they were, where they were originally the dates etc.
E.G. I found 1 on a boot scan and I know it is the same as 4 other files in the chest.
Why is it that you are trying to access/save this file, essentially there shouldn't be a need to access it. Saving it would be pointless if you did a clean install there would be no contents in the chest, so the index.xml saved would not match the new installation.
A clean instal of what?
I installed the program (updated from 5.0.545 to 6.0.1125 and the chest contents are the same (I never UNinstalled 5.0.545)
Want me to post the index.xml?
I have a question for you: This all started as follows:
I got a suspicious email (IMO) (4/2011) and moved it from the inbox to a new folder I created for it. (I did
NOT open it)
I ran it through Avast! (5.0.545) (folder | right click | Scan "Folder name") and File | right click | scan "file name": File (email) and folder (newly created for the email) were "clean".
(I had also run folder / file through a free program from Trend's Web site also negative)
I deleted the message at some point but not the folder.
Used MozBackUp to back up mail -> The back up files (since the time the message came (4/2011)) were "infected" (the folder was). (Also found by "Trend" on another PC).
Why didn't Avast! find the folder / message to be a potential threat initially?
Thanks!