Forum Discussion
this is working. this is what i added to my webroot file allow list. i have verified with this with several users that had this as well as me. We run corporate Webroot but they should act the same
C:\Program Files (x86)\Origin Games\Battlefield 2042\bf2042.exe
C:\Program Files (x86)\Origin Games\Battlefield 2042\EasyAntiCheat\EasyAntiCheat_Setup.exe
C:\Program Files (x86)\Origin Games\Battlefield 2042\BF2042_launcher.exe
This hasn't worked in the past, and even after reinstalling Webroot fresh, it still doesn't work. I'm pretty sure most with the non-business edition of Webroot are going to be having the same problem. If the problem were that simple of a fix for all of us, there wouldn't be this many people waiting for an official fix from Webroot.
They do not act the same.
- 5 years ago
regardless of version, the core is still the same with Webroot. Business is cloud maintained and consumer is local. the same logistics is in both. reinstalling Webroot wont fix, i have tried that many times. either uninstall 100% or add the path and file names to the allow list worked from the business side as it should for the consumer too.
- 5 years ago@Danno_USMC Out of curiosity, I went to the Webroot management console instead of the App itself. I don't even have access to that kind of management within it. I can only allow files clientside, not through the Management Console as you can.
Doing the process clientside is different, doesn't work, and hasn't worked since the start of this issue. You're saying it should work based off almost no knowledge of it. I do appreciate that you've included images though, since it allowed me to be 200% sure that I couldn't replicate what you're doing.