Well, from your diagnostics I can see that you don't have either ISBoxer or Inner Space running as Administrator. If you're doing that on purpose you might be restricting it. Assuming you're not and you just have told Windows not to bother you with UAC prompts, you can right click Inner Space and select Run as Administrator. This might help.
If not, probably "nothing happens" due to a crash that is not popping up an error box.
The crash may already be solved in the development build of Inner Space. You can try that -- right click Inner Space, select Patcher, tick "Download development (test) patches" and then close and restart Inner Space to let it patch up.
If it still occurs even with the development build of Inner Space, then I would use Explorer (as in Windows/File, not Internet Explorer) to go to
%LOCALAPPDATA%\CrashDumps (for me that goes to C:\Users\<username>\AppData\Local\CrashDumps), and you may find a .dmp file with the name of the exe that crashed, from the time of your crash. So in my case I have several wow.exe.#####.dmp files that correspond to some recent crashes when I was working on some issues like yours. Send me (email to
lax@lavishsoft.com will work) a wow.exe.<numbers>.dmp file, from an attempted launch with the development build of Inner Space, and I can have a look for clues.
Posted: Sat Aug 04, 2018 9:32 am