@Adoxa - clienthook DLLs being picked up by Windows Defender and Antivirus software

Aingar

Hello and sorry for bothering you again.

We’re dealing with the issue of our clienthook DLLs tripping up Windows Defender as well as various antiviruses. None of our test-build DLLs were ‘accepted’ by all playtesters, and as the release of the next patch is drawing close, we’re running out of ideas on how to remedy the situation, especially since several major features are bound to clienthook code.

Stuff we already tried (in various configurations):

Blocking the memory hacking unless common.dll is loaded
Enabling various optimizations to try and scramble the code enough to not trigger any virus signatures
Disabling all optimizations
Moving to a modern compiler (visual studio 2022)
Moving to the oldest compiler we could find (Visual Studio 2008 Express Edition)
Adding an .rc file containing various metadata, similar to what you’re doing with your DLLs

We have never had such issues with DLLs compiled by you, so if at all possible, I’d appreciate any suggestions/wisdom you might regarding the matter.

adoxa

Idk, I don’t do anything special. I use VC6, but find it hard to believe that would resolve the issue. If you could point me to your DLLs I could try on my system; point me to the source and if they build with VC6 I could try those.

Aingar

I appreciate the offer, if we’re up against the wall I’ll reach out.