Forum Discussion
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.
It'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.