I just got this issue, Closing Blizzard Update Agent Via Task Manager, while booting the game, solved my issue.
Well, I was getting 395000 yesterday, and am getting a 300016 today. Not sure if that is progress or not.
I closed Battlenet, will try closing it while booting next.
Edit: closed while booting, still getting 300016.
Currently July 2nd and I can not log into the game. It passes authentic but can not retrieve my characters and will give me one of the errors listed (395000/300016).
Help Blizz pleazz
i cannot login also !
im getting 300016 error code. 
and its not my internet provider, 'cuz i can login and play hots normally.
so i was also having this issue, and jumping from EU server, back to the US server helped, how ever, my friend is still unable to get hers working, even with the same method.
Deleting the Diablo III folder in my documents seems to have fixed it?
Was getting 395000
Deleted folder
Launched game, got different error
Relaunched game, now I’m in
Honestly who knows if that’s whats fixed it at this point. If it doesn’t work for you try running 17 more traceroutes lol
1 Like
I managed to get into the game!
Process:
- cmd.exe - netsh advfirewall set allprofiles state off
- Optional: If you’re running pi-hole or something similar, add battle.net to the approved domains.
- Launch diablo 3
- In my case, at this point I made it beyond 395000 and got the 300016 error.
- Alt-tabbed out, cmd.exe - taskkill /im:battle.net.exe /f
- cmd.exe - netsh advfirewall set allprofiles state on
- log into D3.
- Play game
Does this happen again if I close and re-open the game or even reboot my computer?
So far, no. Things are working at this point and appear to continue working without issues.
workarounds dont seem to work, tried to log in directly about 12 times. same 300016 error but it works fine on europe servers… but uhhh don’t live in europe so yea
@kyubii, I had the same problem. You tried killing ALL of the battle.net.exe executables? There should be 4 running.
Have we still only got one response from Blizzard? Seems like there’s plenty of us having the issue, I’m in Australia, characters on America’s and haven’t been able to get on in days tried heaps of options above and still
Nothing …
Code 395000 - So after getting nothing from my support ticket, having already disabled antivirus, firewalls, etc. I was reading through this thread and someone mentioned make sure your firewall is off, I thought, maybe I didn’t turn it off. Well, I did. So, I thought, I’ll turn it back on. So I did, i ran D3 and window pops up to allow it on private/public network, i checked both boxes hit ok and the game started… So, I ENABLED my firewall then ran D3 and allowed it through and it worked. Hope that helps some out there!
Killing all Blizzard related processes except for D3 worked for me as well. Not sure if this will fix it on a recurring basis though as I was only logging in to collect the wings.
64bit game gave me relentless 395000 error codes, even after trying to kill the launcher or launching the game without the client entirely.
Launching my game in 32bit mode allowed the game to (finally) retrieve my character list (after powering through a couple more 300016 errors). Once I was able to load into the game, I tooled around a bit, playing with transmog and whatnot. Exit the game, revert back to 64 bit, and am now able to log in again per normal. Maybe I’m lucky? Hope this helps someone else.
I was told this in a support ticket:
One of the things we have seen resolve this is Logging out, changing the log in region and game region, creating a character there, then logging back out and setting things back to your home region.
I can login to the game if i switch my region to europe and create a new character, but when I log back out and set things back to my home region, it goes back to not working again. Has anyone gotten this work around to work?
I can confirm the workaround worked for me, as well. Thanks for highlighting it.
This worked for me. I had one file in this folder call d3prefs.ini. I just renamed it and I was able to log into the NA region.
Strange since as far as I can tell the settings in this file are graphics settings, and it worked fine when logged into ASIA region
I tried some of the other tricks (changing firewall, killing blizz processes), to no avail.
What finally worked was the following:
- Changed region from Americas to EU.
- Created a character, entered the game, allowed it to grant achievements while I fought just into town.
- Exited and switched region back to Americas and relaunched.
- Let it deny me with the 395000 error.
- Entered my credentials again.
Used the launcher for switching regions and launching the game, each time.
This also worked for me. You are a gentleman and a scholar.
I was going to be very upset if I was unable to play when the season begins today in NA at 5 PM PST!
Windows 10 Firewall was indeed the issue.
D3 was set to only public, enabling private for both D3 entries fixed it.
1 Like
There was only one entry for me, but enabling private fixed it for me as well!