Hi. I have permanent error 395002 in Diablo III for 4 days on American server.
I am from Kiev, Ukraine. Played 12 years on American server and have a good team there. On April, 3th server crashed down and our group was dropped out from the game. Than server was not working for 15-20 min. When I tried to return I got error 395002 “There was an error loading a hero”.
I found article Error 395002 in Diablo III - Blizzard Support and did following steps:
- Log out of the game then log back in.
- Run the repair tool to repair any damaged game files.
- Switch to another game region and switch back to refresh your game’s cache. >> I had a success to enter European server.
- Delete the Battle.net Tools folder to automatically rebuild outdated or corrupt files.
Also I tried from another computer!
Still have this error.
Than I made a Rollback 2 times. Rollback FAILED 2 times!
I can suggest that there is error in server database and I need help to repair it.
Your Characters are still there. At least they’re showing up in your Armory Profile:
Americas Region
Europe Region
Assuming you’re on a Windows PC
If nothing else works, try rebooting your modem/router.
If that doesn’t work:
- Uninstall the Battle․net App. (Don’t uninstall D3).
- Check C:\Program Files (x86) and delete any Battle․net folders that may still exist.
- Check C:\ProgramData and delete any Battle․net folders that may still exist.
- Restart your computer.
- Reinstall the Battle․net App. You may need to “show” the App where you have D3 installed.
If you still have issues, uninstall D3 and reinstall it. (Do this as a last resort).
After that, I don’t know what else to tell you.
Thanks, Perusoe.
Battle.net already was uninstalled, all folders cleaned up manually, than reinstalled 
Fresh D3 installation was tested too on another computer.
@Alex : Hello,
Have you tried to force the connection to another server pool ?
The “Americas and South East Asia” region has 3 server pools: North America, South America and Australia. Usually, the Battle.Net App will default to the server pool that has a better connection (lower ping times)… In your case, that would probably be the North America server pool. But it is possible for you to force the use of either South America or Australia server pool.
See this screenshot – it shows how to force Battle.Net to use the South America server pool :
On the Battle.Net App, click on the BNet logo in the upper left corner of the App and select Settings. Click on Game Settings and click on Diablo III. Activate the “Additional command line arguments” under Install Location and add the following text in the box:
- for South America server pool : OnlineService.Matchmaking.ServerPool=SA1
- for Australia server pool : OnlineService.Matchmaking.ServerPool=AU1
- for North America server pool : OnlineService.Matchmaking.ServerPool=Default
Check whether the use of these command line arguments for SA or Australia will let you start a game on the America region… the lag will likely be high because of the increased distance for the connection… but hopefully, this is a temporary situation. If you can launch a game, the next test is to delete that command line and check whether it now start in its default configuration.
Good luck !
1 Like
Thanks, interesting idea.
Tried SA1 and AU1… Got Error 395002 everywhere(
Try updating, or rolling back, your video card drivers. Also, set all the in-game video options to the absolute minimum. Maybe try the settings first, since that would be the easiest.
It looks like an American server database error, not video driver.
- I am playing on European server this few days. All works fine there in game (but my team is not there and all my heroes are weak, because I was playing almost ail time at America).
- I have two systems on my PC - Win 7 and Win 10 on different HDDs. And different Diablo 3 folders on each of them. Tried both.
It certainly starting to look that way… if that is the case, you’ll need to contact Blizzard Support so that they can look at your issue and figure out how best to fix it.
I am unsure which region or which service you should be sending your ticket to, however. Your BattleTag indicates that your home region is Europe but you’re having the issue with the America region servers (all 3 of them). It may be best to first contact the America region support.
We had a similar case in May 2024 on the EU French forums. The player had to send 2 (or more !) separate tickets before some Blizzard staff took interest in the issue, replied that the issue could not be fixed by Blizzard Customer Support, but that he was escalating the issue so that someone could look into the account… the problem was resolved a few days later.
You may have to do the same…
There is apparently some monitoring of the forums for technical issues… not sure what they can do, if anything except to report the issue in general. And since you appear to be the only one here with that issue… it may “fall under the radar” so to speak.
Good luck with this !
1 Like
Hi again…
Addendum:
I thought I’d share this post by Blizzard on the Korean Technical Support forum for Error 395002: Code 359002 접속안되에 - Emeril 님의 #2 - 기술 지원 - Diablo 3 Forums
If you use machine translation and convert the links to US… you get:
Hello, this is Emeril from the technical support team.
First, please try all the methods listed below.
https://us.battle.net/support/en/article/000014823
If the problem persists, please submit an inquiry at the path below so we can provide more detailed guidance.
https://us.battle.net/support/en/help/product/diablo3/273/277/solution
thank you
Good luck !
1 Like
97 days went. Error is still here. Re-opened ticket 10+ times. The problem was escalated to Blizzard tech team 3 times. They are still “investigating”. If they do:)
Update August, 4th 2025
It’s been 4 months of permanent error 395002 and the inability to play on the American server.
The Blizzard team’s investigation of the problem has dragged on for an indefinite period of time.
We have a saying: “Hope dies last”…