Forum Discussion
150 Replies
- @th3m4r1n3 It worked for me! Im definitely not going to wait for Webroot to give another update so I just uninstalled it. I had this problem for hours and turned out Webroot was preventing the game from starting. So just give it a try sir.
I've contacted EA support twice, and both times left me even more upset than this recurrent issue did. The first person told me to, more or less, disable my Antivirus entirely. If that didn't work, uninstall it. It's not really a surprise that it worked, but having to make your system vulnerable is not an acceptable "fix", it's like patching a leaking pipe with duct tape.
The second time I contacted support shows just how terrible the state of EA is. They quite literally linked me the very first thing that pops up if you search this problem. They didn't even bother trying to help me themselves, or even offer anything about Webroot. They JUST kept linking me to the first articles you find if you search the issue. I've never seen such a zero-cares response before from a company still trying to save face.
I want to play this buggy mess of a game, because despite it all, I do enjoy it more than current alternatives. Too bad I'd have to remove my Antivirus to do that, and this game certainly isn't worth the risk.
Let me get this strait. I have used Webroot for years with no issues. Had no issues during the 2042 beta and have had no issues starting the game until the 9 Dec 2021 update. Now all of the sudden Webroot is an issue?
Hearing I should reinstall Windows or disabling my anti virus should not become the go to answer to fix this problem.
- MasterBlaster735 years agoRising Traveler@DeathSquared1 Read my posts. I already opened a ticket with Webroot just like I did when EAC stopped B4B from working, and they will release an update just like they did for B4B and BF2042 will run again. They will send me the build and I will run it and confirm it works and all Webroot users will get it immediately.
- fidstang5 years agoRising Traveler
Same issue for me, last update to the game through Origin and game will not launch. I've been playing it just fine up to the latest update.
EA needs to resolve this ASAP or give me a refund. Class action might wake them up if they don't respond.
- fidstang5 years agoRising Traveler
Yea, not going to disable my anti-virus software because of an update from EA that is preventing us from launching the game. Worked just fine before the latest update, try again.
Also, I have allowed access in Webroot for the game and origin. Worked fine before, works fine with Battlefront 2 and other games I have in Origin.
Maybe escalate this issue for resolution, we paid for a product use that and EA needs to roll back the update if anything until this is figured out.
- MasterBlaster735 years agoRising Traveler@fidstang You will be wasting your time trying to resolve this through EA. I have tried to contact Easy A/V and they do not respond. Webroot will fix it like they did before. If doesn't matter if your other games work or if BF2042 worked before the update. SecureAnywhere is stopping the new version of EAC from launching which stops BF2042 from launching. I will not uninstall My A/V either. I will wait for the fix.
Probably my first post here in years. I'm having the same issue. I've been searching the web for hours and I have tried everything. Including disabling Webroot. That did not fix the problem. I am not going to uninstall Webroot. That is just next level stupidity. I have been using Webroot for 20+ years and I have played a TON of BF (and other games) with no issues.
I will be contacting Webroot as well and I already have a ticket open with EA.
This is beyond stupidity on EA's part to push out a patch that isn't tested beyond a micro-bubble of their internal team.
One thing I noticed is that when I'm in the EasyAnti cheat - inside the folder for my BF2042 install it shows #'s for the games? How the hell am I supposed to know the right one?
Help?
- MasterBlaster735 years agoRising Traveler@inducefear Mine doesn't have any of that. I could be wrong but I think it's the updated certificates. Doesn't matter anyway as the only one that can fix this is Webroot.