Error 1910, what does it mean?

Could someone pinpoint the origin of this error, because I don’t understand it. It says it is a connection issue. But I tried it in Austria during the open beta and now at home in the netherlands. I tried it wifi and with cable. I tried two routers, which both work perfectly fine for everything else. My average download speed is 70 mps.

So it is not location, router or internet stability as far as I can tell. So maybe it is my laptop which is causing the problem? Though I wonder how that makes it a connection issue?

Does someone have a clue what actually causes the 1910 error, because I am lost.

1 Like

We are all in the same boat and haven’t gotten any support. I feel like I’ve tried everything as well. Time to hold our breath and wait or ask for a refund.

To be fair Blizzard is probably a bit busy, Big launche, so I am sure it is all hands on deck with everything. I am sure it will get sorted in time.

I was just curious is anyone had an idea what causes the error, as I can’t wrap my head around it. Perhaps it is just a silly thing I am not thinking about.

If you happen to figure it out, please let me and everyone else know what to do.

Will do and meanwhile I am hoping someone may be able to provide a clue as to what causes this error. It would really help with solving it.

I found the solution, I had this problem since this night.

I had to reset my PC and all my drives and it worked directly.
I really think that this problem comes from older diablo 4 files from the beta.

So if you can find those files without resetting the pc that should work but I personally couldn’t find them

Hope it’ll solve it for you

I guess I could try and hunt down and delete the Beta files. I’ll try when I get home. If anybody else has success, please post.

1 Like

Do you mean completely reformatting my drives and reinstalling windows? Because that is about to become my last resort.

That seems too extreme. I’m going to make sure I have everything from Beta cleaned up but please let me know what you end up doing. I should be home and trying in about an hour.

So far I’ve tried to manually hunt down the files and I thought I got them all, but apparently not. However what bothers me about it is that I already got the 1910 error during the grand slam in may, so I couldn’t play then either. Since that was really the first time I installed anything from diablo IV, I doubt old files can cause this.

However good news:

It seems the issue has been noticed. :smiley:

Exactly what I wanted to hear… my faith might be renewed!!!

I am in the same boat as you I got the error on first installing Diablo IV during the Server slam last month. Since then I did do a reset on my PC and had to reinstall everything. I was hoping I would be able to install Diablo IV again once it was available earlier this week and be able to play. However, I was met with the same error now. I’m glad that resetting the entire PC worked for some but in my case, it still did not correct this issue.

I even went into Windows Firewall and specifically allowed battle.net and diablo IV through just to make sure it was not blocking something without telling me. I then rebooted my PC and did a scan and repair on the game files. This still resulted in the error 1910.

As a side note, I have also done any and all of the suggestions that have been shared in this post as well as the referenced one to attempt to get Diablo IV working. I look forward to any additional suggestions and/or a patch from Blizzard to address this error.

They claim to have escalated the issue, hopefully a solution will be presented to us soon.

Ok a possible solution is creating a different admin account and using that to start the game. :slight_smile:

As Vegejor stated multiple of us getting this errror are now able to login after creating/using a local admin account on the PC having an issue.

Howdy Guys

This error should now be resolved, if you haven’t tried again recently please do!

The error still occurs. Please provide further options/updates. Thanks!

EDIT: For me the issue occurred through Lutris/Wine-Ge, switching to Steam/Proton somehow enabled me to play the game successfully now. May well be something of a permission or related issue, I wonder why there is no clear explanation for what it means if there is an error code for it.

1 Like

I am still getting the 1910 error when using my original admin account on my PC. I am able to log in when using the newly created ADMIN account though. so this issue seems to still be there. I am happy to provide support with any additional information they request to help get this issue fully resolved though.

I solved the problem with code 1910. To do this, I needed to separately download the client of the beta version of the game and log in to it using my login and password. After that, the current version of the game started without error. In the guide that I used, they claim that with error 1910 there is no token to enter the game. And the token itself is assigned only upon authorization in the beta version.

1 Like

Purchased the game today. It was a fresh install since I didn’t participate in the beta or pre-release. Running into the same issue. Tried all of the suggested fixes short of creating a new admin account since this is a week old install of windows 10.

Got burned on the D3 release due to server issues so I waited this time but now I seem to be getting burned just the same. I’ll definitely be waiting months after release for any new blizzard game. This is just sad considering the price on top of macro transactions.

1 Like