after the last update, i had curseclient running and kicked off wow, curse client tried to access wow.exe, its never done that before, is there a reason it would be trying to access wow in memory?

i blocked the request with my firewall, curseclient shouldnt be touching anything except curse.com and the folders where wow is installed.  was there a reason for that change?

no response?  so no one has any idea if the curseclient is supposed to be accessing wow.exe itself or not?

The only thing the client does with wow.exe is find the path to it, and in the newer v4 client it has a launch wow button.  I'll see if I can find out more info.

The client will check for the existence of wow.exe on disk and check to see if it's running in memory before it does certain tasks.  That's the only things I can think of that it should be doing.  

Oh well as Ackis mentioned the v4 client will start wow for you.

i dont mind it checking for existence, as that makes good sense,  i'm not sure if my firewall (comodo) can tell the difference between searching for it and accessing it - i presume it may depend on how youre checking for existence?

not overly bothered as i've configured the firewall to block access anyway, just thought i'd mention it as people have become very security concious lately (i dont trust anyone when it comes to wow security no matter how well intentioned, so not picking on you guys)