Avast has identified that the file C:\Windows\System32\fileops.exe is infected with the virus Win32:MalWare.gen (no other files came up after a full boot time scan).
Avast does not repair this virus when asked, I checked with Avira, AVG and adaware but none of them even spotted the virus.
You could also check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner and report the findings here the URL in the Address bar of the VT results page. You can’t do this with the file securely in the chest, you need to extract it to a temporary (not original) location first, see below.
Create a folder called Suspect in the C:\ drive, e.g. C:\Suspect. Now exclude that folder in the Standard Shield, Customize, Advanced, Add, type (or copy and paste) C:\Suspect* That will stop the standard shield scanning any file you put in that folder. You should now be able to export any file in the chest to this folder and upload it to VirusTotal without avast alerting.
This looks like a false positive as GData also uses avast as one of its two scanning engines.
You can scan the file again and when avast alerts click the report as a false positive link in the alert window.
Or - Send the sample to virus@avast.com zipped and password protected with the password in email body, a link to this topic might help and false positive/undetected malware in the subject.
Or add the file to the User Files (File, Add) section of the avast chest (if it isn’t already in the chest) where it can do no harm and send it from there. A copy of the file/s will remain in the original location, so you will need to take further action and can remove/rename that.
Send it from the User Files section of the chest (select the file, right click, email to Alwil Software). It will be uploaded (not actually emailed) to avast when the next avast auto (or manual) update is done.
thanks a lot for the help. so far I haven’t moved the file as I couldn’t repair it and its in the system32 dir. I think I’ll email it to avast zipped up.