Subject line auto-correct in Outlook 2016

Hi,
I have a paid version of Avast Internet Security and Outlook 2016 as part of office 365.
in my received email, the subject line changes for SPAM…(title of an old email) or PHISHING … (same) or even adds CC list from older email and attached documents. So my emails are completely messed up.
I see that already happened with Outlook 2010 see:
https://forum.avast.com/index.php?topic=104246.msg834002#msg834002
I know that it doesn’t come from my email provider (hotmail) since on my other computer it doesn’t happen: same Windows 10 version, same outlook 365 but use of Windows Defender instead of Avast and fortunately it doesn’t Sync the modified subject line to the other computer…

Ok, many people have read my message but none of the pros/moderators have taken the pain to answer or try to help.
So I see only one solution: ditch Avast and use Windows defender instead: Free and apparently more efficient.
Too bad I was with Avast for at least the last 10 years…

Sorry, i don’t use Outlook, but feel free to contact support: https://support.avast.com/support/tickets/new

Or you can just stop using avast mail shield and let hotmail (outlook) handle spam filter

lalrecht,

refering to a 4(!) year old thread isn’t exactly helpful especially since it is about Avast Inernet Security, version 7.0.1466
If you had read the entire thread you would have seen that the problem was solved and also that there is workaround.

As you are the only one mentioning this problem, it very much look like the problem is specific to your system and without knowing more details we or avast can’t help you.

Thanks Asyn, Pondus, Eddy!
@ Eddy: I didn’t see any other solution than to look into that old thread that described exactly the same problem I have…
You didn’t suggest any alternative anyway… I know it was about a beta version and I know it was considered as solved at the time, so what?
Anyway I have tried this work around:" turning the Avast COM add-in off on my computer within Outlook’s Trust Center off"
Is it the one you were referring to?
@ Pondus: thank you for your suggestion. I’ll try it if the work around doesn’t fix it.
I’ll report anyway.