You can upload it to ftp://ftp.avast.com/incoming
One important question though: how exactly do you copy the file? Using Windows Explorer, or some other file manager?
This detection is very generic and triggers easily on broken word documents.
It seems that TC is copying in smaller chunks, avast scans them and finds broken file…
This detection looks like it needs some reworking…
I am having the same problem, while copying a MS Word file in English from an external hard disk to an internal disk. The original copy that put the file on the external hard disk did not report any problems, and the file was created and resided on a system that had a well-established security system (not Avast).
I have a similar problem. several weeks ago i wrote a big thesis paper for university, and now, as i wanted to print it to give it to my professor, avast tells me that this very file is infected with the MW97:1TableBroken [Expl]. when i don’t get it, i am really f****ed up…
First of all, i moved the file to the container, but due to the fact that i really need it, i have to figure out how at least to print it so that i can transcribe it. I tried to open it with several programs (several ms-office-versions, wordpad and open office), tried to rename it (.rtf / .txt / .odt), but all that doesn’t work out. Also i can’t copy or move the file, when i don’t let it rename by avast.
by the way: the first computer on which i tried to open the documetn is a new one, i installed avast some days ago. the word-document is on an extern harddisk, and of course i copied it on my old laptop (in the last three years also protected well by avast) to try to open it - without any results. i am completely aware that this is extremly dangerous, but i do have to open that file.
i can’t imagine that the file is only broken, something else must have occurred…
The only way you could access the file to say print it would be to pause the standard shield or add the file to the standard shields exclusions list.
Whilst there is a risk involved, as has been mentioned this could be just a broken word document and not infected. However, to haul your ass out of the fire so to speak you may need to take this risk.
The safest option I would say would be to exclude the file rather than pause the standard shield, as if it were infected you wouldn’t want it to be able to do anything with another file.
Add it to the exclusions lists: Standard Shield, Customize, Advanced, Add and Program Settings, Exclusions (right click the avast ’ a ’ icon)
Now you could print the file off and do a save file as and select .rtf or .txt format so you should be able to import the raw text into word again or keep it as an rtf file.