Forum Discussion
150 Replies
- UtahUtes325 years agoSeasoned Ace
Shutting down protection of Webroot will not fix this. If you run procmon after WSA is "shut down" you will still see the WRCoreServices64.exe scanning the files at the time the game is launched. This is why only a full uninstall will allow the game to run.
I looked at the Webroot logs but see nothing to indicate anything is blocked, but it obviously is. If I uninstall WSA, the game launches.
- xGBx_Boogie5 years agoNew Adventurer
@NeonDogeCoinYeah pretty much. I contacted them, they gave me times to choose from on when to be called. They called me right at the time I set. He then remoted into my computer, stopped certain Webroot processes, restarted my computer and then the game was able to launch. Literally no more than 15 minutes on the phone.
- @fidstang you have to uninstall Webroot.. not disable
what resolution? the link doesnt provide * process they killed
add this folder to exception
C:\Program Files (x86)\Origin Games\Battlefield 2042\EasyAntiCheat
- @Danno_USMC Did this work for you or is this just another suggestion?
- DravinClaw5 years agoNew Rookie@Danno_USMC This didn't work for me
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
i attached a pic and the 3 lines i added. so 1 of those 3 is making it work. it should be the anti-cheat one causing the issue because when the game tries to start, thats what you see running before ERROR 🏈. maybe you dont have the right exe and file path in webroot. in business webroot cloud the file name is not on the same section as the path
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.