The ridiculous XIGNCODE we all love bans ProcessHacker2, which is a TASK MANAGER REPLACEMENT.
First I thought: OK, they’re afraid of the features it has, or one is able to suspend a certain protection thread of XIGNCODE to enable cheating.
Well, that’s not the problem here. My guess after my findings is: it doesn’t like “hack” in process names or “C:\Program Files”.
To be able to use Process Hacker while being able to play Dirty Bomb, do the following:
- uninstall Process Hacker
- install it again, without enabling KProcessHacker service (gets detected), choose a destination directory without “hack” in its name, don’t create any icons
Have fun.
And NEXON/Wellbia: start being smart.