EA Anticheat TeamIt's weird to call me a liar, when you and I have never spoke.
I e-mailed the Dr Web development team on the 24th of May, in 2024, and asked them to stop injecting their solution into our games. They e-mailed me back on the 3rd of June, 2024, and refused.
I replied that same day and said that if we can't come to an agreement, then we will need to prevent the game from running while this is enabled.
Their driver is signed by Microsoft, just like mine, that's not the point. All drivers running on Windows 11 are cross-signed by Microsoft, that's a requirement from Windows.
We have different configuration and controls based on different games, to address their specific needs. As Dr Web software creates a security vulnerability in our game, that the Battlefield team has agreed is unacceptable, it will continue to be blocked.
>>They e-mailed me back on the 3rd of June, 2024, and refused.
This is not true.
Don't ask me how I know. But if you want to refute this, publish the text of the original answer.
Otherwise, no one is going to call you a liar, but maybe it's time to establish a normal communication channel instead of silently blocking drivers of antivirus vendors?
People paid money for your games and for their antivirus. Blocking is a road to nowhere, because an antivirus vendor can, in principle, perform absolutely mirror actions in relation to your products. And I'm surprised that this has not been done yet, and instead, at various users requests, Dr.Web developers have been improving compatibility with EA games and EA anti-cheat, including adding trust to it and excluding injections.
The day Microsoft allows anti-cheats to get into the kernel will be the worst day in the history of gaming. Mark my words. I can't wait for MS to kick everyone out of there, and that's just around the corner.
>>Dr Web software creates a security vulnerability in our game
Sounds like a joke. Is this "security vulnerability" by any chance not a banal injection into system processes and presumably into some game processes? And if so, doesn't it seem that this is normal behavior for an antivirus, and not malicious or cheating actions? =) That is, the very fact of injection from a known process signed by a known publisher's signature does not mean that this process is involved in cheating. In a normal case, this is solved by creating a white list(from both sides), to which drivers and services of legitimate developers are added. You can determine this by the signature. All important antivirus services and drivers are signed with a valid digital signature. Instead of creating a white list, EA for some reason goes on the warpath and the easy way out, adding the antivirus driver to the blacklist.
Although I know that in a similar situation, the developers of Dr.Web added anti-cheat processes and various EA games processes to their whitelist. The problem is that EA has a lot of games and they are updated periodically, including the signature.
Moreover, this blacklisted driver drweblwf.sys has nothing to do with the main antivirus activity. It is just a firewall driver, which in most cases does not perform any work at all. Looks like random ban.
So, I think the best way to solve problems at all times will be "dialogue" and not "sanctions". Because a stick thrown at a neighbor can fly back. And friendship conquers all.
Let's make love, not war. (c) Stan
