Forum Discussion

Elwoodg1's avatar
Elwoodg1
Seasoned Newcomer
1 day ago
Solved

Getting error 85008S and 85011S when trying to launch BF6 on a PC

I am having the issue from my PC and getting errors 85008S and 85011S repeatedly.  I have attempted the repair procedure for the game.  Cleared the game cache.  I have removed and re-installed the game.  Changed my EA password. Did the "netsh winsock reset" and rebooted.  Changed to a different DNS server.  Tested with my regular internet connection and from a VPN connection.  None of these steps actually work to correct the issue.  I am currently doing the repair process again now.

These errors indicate a connectivity problem of some sort.  Is there any way I can actually test my connection to BF6?  I believe I have a good internet connection.  I am getting 23ms response time for a continuous ping stream going to an address on the internet so it does not appear to be my network.

  • I fixed it.  For testing I forced all my traffic to use my VPN connection.  I disabled that and the game now loads with no error.  When enabled I get the errors.

4 Replies

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    6 hours ago

    Elwoodg1​ 

    Thanks for coming back to post the steps that helped you here. Appreciated. EA_Barry.

  • Elwoodg1's avatar
    Elwoodg1
    Seasoned Newcomer
    22 hours ago

    I fixed it.  For testing I forced all my traffic to use my VPN connection.  I disabled that and the game now loads with no error.  When enabled I get the errors.

  • Elwoodg1's avatar
    Elwoodg1
    Seasoned Newcomer
    23 hours ago

    I reviewed the thread you referenced yesterday and attempted the recommended steps before starting this thread.  Just to make sure nothing changed I just performed the steps again, netsh winsock reset, and rebooted the computer.  That did not correct the issue.  I still got the same two error codes.

    Is there a way to actually test the connectivity to see if there is an issue?  Are there any logs that might indicate where the problem lies?