View Full Version : The patch broke my ISBoxer
Hksix
12-11-2019, 08:58 PM
Ever since the patch has come I have not been able to log in through ISBoxer. When I launch my WoW team in ISBoxer I get the following error message:
https://www.dual-boxing.com/attachment.php?attachmentid=2270&stc=1
Then battle.net proceeds to launch, which then gives me the following error:
https://www.dual-boxing.com/attachment.php?attachmentid=2271&stc=1
At that point I am stuck and cannot proceed.
None of these errors are present when I simply launch battle.net and log into WoW as a solo player would. Both WoW classic and battle.net are updated. Anyone know how to fix this?
Carca
12-11-2019, 09:08 PM
Hi I have exactly the same issue.
I've read the .exe thread as well and tried to update both my Inner Space and ISBoxer. They appear to be fully updated.
My Inner space is build 6651 and my ISBoxer is updated and saved to Inner space.
I still can't launch my classic teams and get the same results as the OP.
Any ideas?
Ughmahedhurtz
12-11-2019, 09:15 PM
Can you use the WoW Classic Client that points at the renamed wowclassic.exe instead? It's what I use and it worked last night.
Hksix
12-11-2019, 09:23 PM
Hi I have exactly the same issue.
I've read the .exe thread as well and tried to update both my Inner Space and ISBoxer. They appear to be fully updated.
My Inner space is build 6651 and my ISBoxer is updated and saved to Inner space.
I still can't launch my classic teams and get the same results as the OP.
Any ideas?
Ok I went on the ISBoxer discord and they were able to help me through this. My problem was that innerspace wasn't the latest build. It might not be necessary but I uninstalled innerspace and ran the command "%programdata%\Lavish Software\utils\lavishbuild" install innerspace live "1.16 build 6651" from my run box (win+r)
Then I went to each of my character profiles in ISBoxer and updated the game path to WoW Classic. From there it worked fine.
Airborne
12-12-2019, 12:34 AM
Ok I went on the ISBoxer discord and they were able to help me through this. My problem was that innerspace wasn't the latest build. It might not be necessary but I uninstalled innerspace and ran the command "%programdata%\Lavish Software\utils\lavishbuild" install innerspace live "1.16 build 6651" from my run box (win+r)
Then I went to each of my character profiles in ISBoxer and updated the game path to WoW Classic. From there it worked fine.
I had this problem before the latest patch, the problem wasn't that ISBoxer wasn't updated (although that will help with the exe name change), it's the game path on each character, it reset on all characters for some reason and ended up being confusing since I could launch the game profile that I assumed they were set to but not the character set.
Carca
12-13-2019, 11:04 AM
After trying for a while to resolve this I have uninstalled Inner Space then reinstalled it and ISBoxer from the Lavish website then started all my teams and settings again from scratch.
Maybe if i was a bit more computer adept I could have not lost all my settings. I had about 25 team configurations spread between classic and retail plus all the other little tweaks like formation hotkeys etc. But to be honest I am just happy to be back in the game!
One classic team now - I'll slowly build them back up as I feel the need.
vBulletin® v4.2.2, Copyright ©2000-2025, Jelsoft Enterprises Ltd.