You claim that you contacted Dr.Web and that they refused to cooperate. That’s a lie.
According to Dr.Web staff, there was no contact at all, and they were never informed about the block.
Moreover, they quoted the following from you:
"I cross checked with my team and unfortunately as you requested to excluding the driver of our antivirus drweblwf.sys from the EA blacklist.
This is something not possible as it can cause trouble with actual game performance."
You say drweblwf.sys “causes performance issues”. Where’s the proof? Where are the tests? Where’s the technical explanation?
This is a system-level driver, signed by Microsoft, used for firewall and parental control features. It has nothing to do with cheats.
FC25 works fine with this driver. Battlefield 1 does not. Where’s the logic? The block isinconsistent and unjustified.
You:
Block legitimate software.
Mislead users.
Ignore the issue for over half a year.
Stop lying about “vendor communication”.
Either explain why drweblwf.sys is blocked, remove it from the blacklist, or get in touch with Dr.Web.
This is not anti-cheat. This is incompetence.
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.
Two IT giants can't find common communication to solve the problem, for a year, shifting the blame to each other! What a shame...
Ok. The ongoing blocking of Dr.Web’s legitimate driver drweblwf.sys by your anti-cheat system remains unresolved despite multiple reports and inquiries.
Dr.Web is a reputable, official antivirus vendor with a long history. If their driver truly created a serious security vulnerability affecting your games, it is EA’s sole responsibility as the developer and operator of the anti-cheat system to provide:
Clear, detailed technical evidence about the nature of this vulnerability;
Concrete reproduction steps and explanation of how it compromises game security or integrity;
A rationale explaining why this issue affects only Dr.Web’s driver, while other antivirus drivers with similar or broader system-level access remain unblocked.
You claim to have contacted Dr.Web, but no evidence or details of this communication have been provided. Simply stating that Dr.Web refused cooperation without sharing any proof is insufficient and unconvincing.
Attempting to shift responsibility by suggesting users or third parties should “contact Dr.Web” is unacceptable. Your anti-cheat system is the entity enforcing the block and controlling the user experience — this is your problem to solve.
Further, your statement that Dr.Web “injects its software into the game” needs concrete technical proof. Antivirus drivers operate at the system level, not inside game processes. Vague accusations without explanation only create confusion and erode trust.
Also, the inconsistency in your blocking policy — with FC25 running fine alongside this driver, while Battlefield 1, Battlefield 6, EA FC 23, and EA FC 24 are blocked — raises serious questions about your decision-making process and internal standards.
I expect EA, as the responsible anti-cheat authority, to:
Take full ownership of the blocking decision regarding this driver.
Provide transparent and verifiable technical explanations and evidence.
Engage directly and constructively with Dr.Web’s development team to collaboratively resolve any legitimate concerns.
Remove drweblwf.sys from the blacklist immediately, pending transparent investigation results.
This is a matter of professional accountability and user trust. Evading responsibility or deflecting blame damages EA’s credibility and user confidence.
I expect a prompt, clear, and fully technical response from EA — not deflections or vague statements.
What do you mean by injecting their solution into your games? It’s just antivirus with a firewall, it doesn’t do anything specifically with your games. Let us at least add them to the exceptions in antivirus and make it work this way so we don’t have to rename drweblwf.sys and disable updates, which basically kills almost all antivirus functionality. I tried adding BF6 to all possible exceptions, and that’s still not enough—your anticheat hates the fact that this file drweblwf.sys even exists. It’s not a good solution. Please consider finding another way.
I also contacted Dr.Web, and they said they tried to reach out to you, but no reliable information has been provided by EA. You can play this “we contacted them” game back and forth forever, but it will never end—and it does affect players. Why don’t you just fix it on your side? Or at least make it avoidable so we can play without breaking our antivirus.
Hello! Just add "drweblwf.sys" to your Anti-Cheat exceptions or whitelist. I know, you can do it. We paid money for this protection and for your games too. It's just an antivirus, why are you blocking it? It's worked together before the anti-cheat update in 2024. What changed?
>>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
