"unexpected error"

It's not BUT I did like Darkstar42 wrote and it launches.

the strange thing is - i change d3.exe to launcher exe for only 1 account and that fixes other 3 accounts as well.

I have this same problem since new patch.

How did you change the launcher (launch location?) like darkstar42? I can't seem to find where it can be changed. Only ADD a game and can't do Diablo 3 again.

I have this same problem since new patch.

How did you change the launcher (launch location?) like darkstar42? I can't seem to find where it can be changed. Only ADD a game and can't do Diablo 3 again.

Right click innerspace. click configuration. innerspace configuration window should pop up.

go to game configuration, select diablo 3 then remove game red tab.

close it

right click innerspace to re-add diablo 3. and point it to where it is.

That did it!! Thanks a million Darkstar!!! No wonder I couldn't find it, the games don't show until you hit the drop down to delete them.
You are the man!

[lax]

Ahh, no wonder I couldn't reproduce this issue with the current build, it only happens if you point it to the game client without using the -launch parameter. I'll take care of that tomorrow, thanks guys.

FYI: You either want to point it at the Launcher exe, or if you point it at Diablo III.exe directly, you need to put "-launch" in the Parameters box (with no quotes!) and this will skip the D3 launcher.

Same issue again, Innerstpace updated on start and ow i get the errror again. is there a way to roll back last patch?

[lax]

Inner Space build 5838 fixes the remaining "Unexpected error" issue. This build is now live, and you should be fine to simply restart Inner Space to patch it up to 5838 and go back to playing.


If you continue to have an "Unexpected error" which just pops up a Diablo 3 error reporter with a box to enter in what you did to make it break, as it turns out there is useful information in your Diablo 3 install folder:
C:\Program Files (x86)\Diablo III\InspectorReporter\ReportedBugs
This will have folders inside, by date and time, e.g. "2013-05-16 10.54.30" is for one I had this morning while testing. Within this folder, I found "D3Debug.txt" and this contained the information necessary for me to correct the bug. There is also an App-0.dmp file in the folder, which can also be sent to me via e-mail for new issues like this.

I'm going to lock THIS thread as of now, so anyone with an "Unexpected error" with Inner Space build 5838 or later, please begin a NEW THREAD or provide me D3Debug.txt and/or send App-0.dmp to lax@lavishsoft.com