I'm sorry, if it seemed if I was being an Imbecile or an ass. It's just I seen other members that have done this and never came back.
I didn't know your current situation, and I apologize. Usually I never have seen it take more than 24 hours for someone to reply.
I hope you read this post, you don't have to accept my apology if you don't want to, and that's fine by me. I just hope that this can be left behind.
I'm Sorry :Cry:
It seems you are still having the same problem. Avira is known to flag even clean files if the Heuristics Sensitivity is set to high or enabled (Can't) Remember which.
I believe that Yasu hooks API Calls or something of the Sort, in order to hide virtual drives from known copy protections (Securom, Safedisc) I don't know if it works for Starforce though. It might be this very reason combined with The Heuristics Sensitivity on Avira, that is causing it to be detected as such.
However the file itself in retrospect is actually clean and exhibits no malicious activity whatsoever, It's the way it was programmed to hide Virtual Drives that causes this false detection or false positive:wink:
Someone correct me if I'm wrong, especially you sYk0 if you are reading this.
Hope that may answer the question, but you might want to see what sYk0 has to say about what I explained.
I didn't know your current situation, and I apologize. Usually I never have seen it take more than 24 hours for someone to reply.
I hope you read this post, you don't have to accept my apology if you don't want to, and that's fine by me. I just hope that this can be left behind.
I'm Sorry :Cry:
It seems you are still having the same problem. Avira is known to flag even clean files if the Heuristics Sensitivity is set to high or enabled (Can't) Remember which.
I believe that Yasu hooks API Calls or something of the Sort, in order to hide virtual drives from known copy protections (Securom, Safedisc) I don't know if it works for Starforce though. It might be this very reason combined with The Heuristics Sensitivity on Avira, that is causing it to be detected as such.
However the file itself in retrospect is actually clean and exhibits no malicious activity whatsoever, It's the way it was programmed to hide Virtual Drives that causes this false detection or false positive:wink:
Someone correct me if I'm wrong, especially you sYk0 if you are reading this.
Hope that may answer the question, but you might want to see what sYk0 has to say about what I explained.
Comment