Battlefield 6 Wont Launch — EAAntiCheatService and 0xC0000005 Error

Season 2 did not fix the problem, but I found out something ridiculous... Try adding a local account to windows and see if the game launches. I am not kidding when I say that was my fix. I speculate that Javelin does not like the Admin privileges of my default account

Count_Dooku19​ Did you ever find a solution to this? I've ran into this issue today and have tried everything. Just wanted an update, thanks! 

I also have this problem, I last played a week and a half ago, then mid last week there was a small ~280MB patch and since then I haven't been able to launch the game. I cannot for the life of me find my way through the support portal to the point where I can log a support request.

I'd like to add some details about my troubleshooting process in case it helps someone else. One day, BF6 suddenly stopped launching. There was no error message at all — after the loading screen finished, it would simply return to the EA app.

I highly recommend checking the Windows Event Viewer logs before trying random fixes. If you're seeing the same error shown in Screenshot 1, I first tried uninstalling and reinstalling EA Javelin Anticheat in multiple ways, including:

Uninstalling it and letting BF6 automatically reinstall it on startup.

Downloading the installer from EA and running it as Administrator.

In my case, neither of those steps fixed the issue.

The important clue in the Event Viewer was:

Faulting module name: C:\Windows\System32\msvcp140.dll, base: 0x7FFC85A70000

That suggested the problem was related to the Microsoft Visual C++ runtime rather than the anti-cheat itself.

Eventually, I found a Reddit post that recommended installing the latest Microsoft Visual C++ Redistributable (VC++ Redist). After downloading and installing the latest version, the game launched normally again.

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

https://www.reddit.com/r/Battlefield6/comments/1o3epj3/solution_if_the_game_silently_crashes_after_the/

Hopefully this helps someone else. Thanks again for pointing me in the right direction!

Guys, I just solved this problem in a really stupid way. I tried everything—CMD, BIOS, tweaking every possible setting—but for days, the game would just launch to a black screen and then shut down without an error message. WELL, I have an AMD graphics card; I have no idea what the hell happened since I hadn't changed anything, but I just switched the game setting to "Quality Preset," and it launched normally. I'm really happy, but I also feel like an idiot.

Sorry for the late reply, haven't opened the forums in a long time. I did not find a solution, but the game did "magically" work for me. At around early/midway through season 3, I just randomly decided to try launching the game and was surprised it worked. From then and to this day, I've had no issues. 

It could be that I've done something to make it work, but honestly, I can't recall doing anything that would have fixed it. Did your game work before at a certain point? Because mine didn't work from launch until season 3, and I'm 100% sure the issue was the EA Anti Cheat. 

I'm getting the same error.  Was able to play Wednesday - shut down for the night, came back yesterday (thursday Sept. 2nd) and got this error and tried all the tghings I read and what AI said and I get this in the logs

"ExitType: 0xA447588E598D404B"

"Failed retrieving service path.

It's like it can't find it's own EAAntiCheat.sys file or whatever, but I also read that the file is kept secure by the anti chat software

I have downlaoded the installer frrom EA's website, no luck

I have this isue with Batgtlefield 6.  Was able to play since launch with no isues until now.

Tested with the most recent preview Windows 11 update just in case, didn't work so I rolled back.

All files are clean - no corruptions

GPT partition (no dual boot)

Secure Boot Enabled

UEFI boot

CSM disabled

TPM 2.0 with it's updated firmware

NOTHING IS WORKING!

I ran into this problem after the release of Season 5; I resolved it by reinstalling the Microsoft Visual C++ Runtime (the latest Visual C++ Redistributable package).