Community Manager
As of today, may 28th, the game won't start and Easy ANticheat gives me a Security Violation c(111) error
I made no changes since yesterday, so I fail to see what could trigger EAC, though I know it's a trash anticheat and might think my RGB application is Cheat Engine or something
Anyone else had that particular error?
Update:
I enabled Secure Boot two different ways and guess what?
still doesn't work. Guess I won't play EA games anymore, as if I needed an insentive
All of you can double check your Secure Boot state with PowerShell as on that example:
To PowerShell:
Confirm-SecureBootUEFI
PowerShell will return True or False
I've seen all of your replies and there is something wrong with you. Are you some sort of EA bot? Do you work for EA as some sort of weird damage control?
This is not a solution.
EA **bleep**ed up, it is absolutely and unequivocally unacceptable for them to push a patch that requires a hardware change.
By definition a bios configuration change IS a hardware change, this one may not be significant, but it is. Its a change in system requirements.
This patch needs to be **bleep**ing reverted immediately. And at that, there absolutely needs to be compensation.
This cannot stand, and if you think this type of change is acceptable, you need to take a step back and really think and understand what actually is happening and what the implications are.
If this is not the solution for that problem what you all asked for then what is the solution? Wanted to fight against cheaters? How can EA control what other brilliant ideas cheat makers come up with to bypass anticheat? Right now cheat makers found their way in through Secure Boot and only way to stop it is to block that entry point by enabling Secure Boot. That feature is standard for everyone at this time anyway. This fight is getting only worse and worse.
