I am experiencing this same issue. I was not even able to play during the Server slam due to a similar issue. I have done all the same steps FreePlay did as well as did a scan and repair on the game and removed all files I could find referring to Diablo IV from my machine and reinstalled the game.
We have escalated this 1910 error to our team for investigation, which is currently underway. Until we have more information to share, I do recommend the following troubleshooting:
Reset Windows Firewall following the drop-down steps Here. Ensure any personal anti-virus is fully set up to exclude the Battle.net and Diablo IV folders as well.
Disable all startup programs to help rule out any third-party software conflicts following the steps Here.
Shut down the PC. Power Cycle the home network’s modem and router to refresh the connection to all devices on the network and to the Internet Service Provider. Steps on how to do this can be found Here.
Once the network is back online, turn back on the PC and retest.
Thank you for the response to this Zuvykree. I will go through these steps now and report back what happens.
I walked through the steps outlined in your response and rebooted my PC afterward. However, I am still being met with the 1910 error once I launch Diablo IV.
Thank you very much for the update. I would like to add that I very much doubt this is a ‘true’ connection error. I tried it in two countries, both with wlan and wifi and my friend can connect from the same connection on his pc.
I suspect something on my laptop causes the error to appear, but that is just my suspicion.
Ok that is interesting, I will try that tonight. But that would suggest it is something to do with settings, rather than a connection or software issue.
UPDATE!! I was also able to login fine after creating another admin account on my Windows 11 PC. I will link this post and the other one to my support ticket in hopes they can use what weve tried to find a more permanent fix.
Interesting. I wonder if just running things as admin would also work. I’ll go home and try that as well. That is an interesting work around. Seems like that indicates some weird permissions thing in the background is the issue.