Not only VAC also BattleEye.
Sorry about that... I accidently merged some changes yesterday that were not compatible with BattlEye and the nightly builds were automatically blocked by BattlEye anticheat protection. I've reverted those changes and it's fixed the problem. Please update to the latest nightly build and you'll be able to use Process Hacker with BattlEye once again.
If anyone is still having issues with BattlEye after updating to the nightly release then please create a new bug report
Valve refuses to discuss why they're blocking Process Hacker and we have not been able to identify code or reproduce evidence of Process Hacker having ever been used to cheat in any Valve games.
The simple fact that you're only kicked from Valve games instead of getting permanently banned shows that Valve also don't even consider Process Hacker a cheating tool.
Process Hacker is also compatible with BattlEye anti-cheat and all features are compatible with BattlEye protected games. Both of those features they want removed can be very easily disabled using the ObRegisterCallbacks API and if Valve was using that function they would be able block a large number of cheaters overnight and every other anti-cheat has been using that function for this exact reason (e.g. BattlEye).
All Valve is doing by blocking Process Hacker is preventing users from being able to identify performance problems and from being able to check processes for malicious activity and what does removing features exactly achieve when those features can be easily disabled?
Here's what every other anti-cheat company has done:
1. Downloaded this code: https://github.com/Microsoft/Windows-dr ... obcallback
2. Compiled it.
3. Signed it.
4. Used it.
5. Stopped blocking Process Hacker.
Microsoft wrote that code for this exact reason and it's very easy to setup and configure... Valve already have a certificate to sign the code so this whole process would take less than an hour to configure and setup but here we are 1 year and 7 months later and Valve has done absolutely nothing to stop anyone cheating and continued to target Process Hacker instead...