Hello, Sorry for my reply. I am only an F-Secure user (their home solutions). Just interesting: Does your experience still show that HitmanPro partner engine detects an F-secure file as 'potentially' malicious? Or it was one-time experience? Based on your log and item SHA-256 hash - this file has been corrupted(?). At least, digital code signing signature/cert were. Perhaps this is possible if the item was during writing/creation (temporary or even update); interrupted during update/create/write; broken item (temporary trouble). Otherwise, item is modified or tricked during certain stage. What is a little be strange for home use situation. And likely that troubles with signature verification was a reason for generic detection (HEUR:Trojan.Win32.Generic). Maybe if your experience is still about such a detection (or if the original item is still available) - possible to check it manually. What is state of file's digital signature? My own experience and "aeoffice.dll" are about valid situation probably (though, I check it with beta F-Secure SAFE solution). At least, the file is signed normally; and HitmanPro did not detect after a brief check. But as was suggested with other replies - detection of each other's signatures is most likely a probable situation. Although my own steps in this kind of situation with detection are attempts to contact F-Secure Labs: https://www.f-secure.com/en/web/labs_global/submit-a-sample#sample-file and the company that detects the item. Thanks!
... View more
Prolem solved after uploading the file to F-secure: "Thank you for bringing this to our attention. Our analysis indicates that the file you submitted is clean. We have identified the issue as a False Positive, which will be resolved in an upcoming database update." Thanks for the support !
... View more