False positive GSCclient.exe after updating to 3456

It seems the problems are solved for me. I'll confirm this permanently once I've found things are still okay after a few updates.

 

agoretsky,

the issue im refering to that still has not been resolved is "does this mean that NOD32 is no longer flagging usage of madcodehook as a virus?"

will continue the post until i hear from ESET that this issue has been solved.

 

Well, the problems are definitely solved for me. Thanks ESET.

Sorry to hear you're still having problems musikit

 

agoretsky or any other admin care to answer?

 

bump because another day where NOD32 has not answered my question has passed.

 

bumping thread again because a moderator has not replied.

 

Very mature of you ! Congratulations , this way is the only way you will receive an answer , right ?

 

thank you for helping me keep this thread on top!

 

bumping again as it seems ESET refuses to fix their broken software.

 

bumping again as it seems ESET refuses to fix their broken software.

 

copy/paste from private message.

i'm sorry i dont believe it is being looked into. if you believe it is being looked into i cant change that however no admin has posted in thread that the issue does exist and it is being reviewed. so until then i can only continue to bump the thread to keep it active as your software is a piece of garbage this is a major flaw in it that the presence of madcodehook and openssl in the application continues to get it flagged as a virus. i have sent you numerous binaries over the last 2 years hoping you would stop flagging it and as of late 2 binaries when requested. and your team continues to flag good software as bad software. until you and your team can honesty reply to the thread stating the issue is being looked in to and can continue to keep people updated on this issue i will continue to keep people updated on your irresponsibility

 

closing in on over 40 days since metalalbert posted this issue and over 2 weeks since i originally posted this issue and eset still chooses the irresponsible path of not admitting their software contains a bug and giving details of when the bug will be resolved.