Avast deletes OpenOffice scalc.exe

Some time during the last week I guess there’s been a definitions update that has caused Avast to delete scalc.exe, which is the OpenOffice 4.0.1 spreadsheet program launcher. I’ve been away for most of last week, so can’t be more precise when this started happening, but it did it on 29 May as soon as I got back. My scalc.exe is now in the virus chest, and the reported virus is “FileRepMalware”.

scalc.exe has been on my machine since September 2013 without causing any apparent problems, so I hope this is a FP which can be fixed soon. scalc.exe won’t work outside its home directory, so I can’t restore it to a temp directory somewhere and exclude that. I don’t want to have to exclude the whole of the OpenOffice program directory from Avast scans, for obvious reasons.

I’m using Avast free edition, which declares itself fully up to date: prog version 2015.10.2.2218, definitions version 150530-0. Windows 7 64-bit Pro.

You can report a possible FP here: https://www.avast.com/contact-us.php?subject=VIRUS-FILE

OK, thanks, done that. (Sorry I’m a newbie, wasn’t aware of this link).

You’re welcome.

You do know that OpenOffice is not really maintained anymore ?
Perhaps it is time to switch to LibreOffice.

Yes I do know, but I’ve used OO for years, it does what I need it to, and if it ain’t broke…

Right now I have a time critical project on the go, and I don’t want to rock the boat at
this stage. Perhaps when this project is off the books…

Until avast has fixed the false positive, you can set a exclusion for scalc.

I’ve had a very helpful response from the support desk which has explained how to do that. (Previously I had incorrectly understood that it was only possible to exclude at the directory level.)

Thanks to everyone here for quick and helpful responses.

I can vouch for scalc being a FP. I mean, don’t use much in terms of security anymore (Including an AV), but scalc, swriter and all those are apart of OpenOffice

For completeness here, and for anyone else with the same issue, Avast Tech Support have confirmed this is a FP, which will be fixed in “the next virus definition update.”

Thanks for the feedback.