Forum Discussion
1,031 Replies
- EA_Aljo1 month ago
Community Manager
Hi there. I merged your message with the already existing thread for this issue. Please try the accepted solution. Thanks!
- MlSZOREX1 month agoSeasoned Newcomer
Hi everyone,
I’m reaching out because I’ve been unable to play Battlefield since the beginning of February due to the Error Code: 1:85009S.I have tried multiple troubleshooting steps found online, but nothing seems to work. Here is a quick summary of my situation:
Duration: The issue started in early February 2026 and has been persistent ever since.
when it happens: strarting game
Steps already taken:
Cleared EA App cache.
Verified integrity of game files.
Flushed DNS and reset network settings.
Disabled all overlays (EA, Steam, Discord).
Added the game to Firewall/Antivirus exceptions.
Despite all of the above, the error persists. It seems like a synchronization or server-side handshake issue, but I’m running out of ideas on how to fix it on my end.
Has anyone else dealt with this for such a long period? Is there a specific port forwarding or account-side fix that I might have missed?
Any help would be greatly appreciated!
- dimkopimko1 month agoRising Novice
Guys. I entered the game without VPN 4 months after the release and now I play without VPN)) this is a victory!!!
- Nuke_Meca1 month agoRising Rookie
EA_Vendcera Your post on Bf6 error code 1:86001S:51002S:57019S, Does not work.. How do i get a real human to help me with the same error code. and to help check if it's my account and linking steam to my ea account is the cause... can a real human please message me so i can get back into the game.. i paid enough for the game, i should be able to play it... thanks...
- EA_Aljo2 months ago
Community Manager
Hi there. Try opening ports as detailed in the instructions here.
- SonsOfUlster2 months agoSeasoned Newcomer
Did anyone get to the bottom of this.
I got the game at Christmas, I started playing it on the UK, now I return home to Spain and it's not working. I am on Xbox series X.
I keep getting error code -
1:86001S:51002S:57019S
Iv looked everywhere online and can't find a way to fix it.
- EA_Aljo2 months ago
Community Manager
Hello. I merged your message with the already existing thread for this issue. Please see the accepted solution for assistance. If that doesn't help, try disabling IPv6. That also has helped others resolve this. Thanks!
- SilentFaith4202 months agoRising Newcomer
I keep getting error code 1:86001S:66003S:4688822970:0B and from what people said it's an authentication issue with players on steam and them having a usb plugged in and removing a usb fixes the problem. Unfortunately, a lot of us dont have that luxury since we have USBs plugged in that are absolutely necessary to use our computers, like keyboards and mice. Plus I dont even have any USBs with files plugged in and I still get this error. It just boots me from games I'm actually enjoying and it's really annoying.
I've NEVER had an authentication error happen from my side. This is always on the side of the company and needs to be addressed immediately. This is immersion breaking and should never be happening to ANYONE.
- Senile_Grandpa2 months agoNew Traveler
Wow, just got a random notification from the buggy EA Forums about this - what a surprise that it's still hasn't been fixed 😂
After waiting years for EA to fix the exact same issue that was plaguing BF1 and BF2042, as soon as I started getting that error I knew what I had to do - got my money back and never looked back. And as someone that has worked both in Game dev and software development for decades I can tell you the issue is 100% on their end and they could fix it within a week if they wanted to. But they don't.
Their management is letting all their hard work go down the drain and you are going to see the same thing happen and there will be 20 people in their servers, to the point that you'll be waiting for a game to start for an hour. Good luck y'all! If you managed to get your money back - great! If not - write a salty review and move on...🤷♂️ - EA_Aljo2 months ago
Community Manager
You can also try disabling IPv6. That has been another solution for others with this issue.