i have done this and i HOPE this has fix the problem. it will be great for the customer if eset explain in detail what caused the problem, maybe...
thanks!
like in an other post, nod32 staff (Marcos) said that we should disable the threadsense feature....
see attached screens
Yes, and if i tryed to submit the "infected" exe file a error window poped up. im behind a proxy.
Thank you that u take time for us and send the boring standard answer. very impressed!
Separate names with a comma.