Game crashes at launch

Hello, ISBoxer newbie here. I'm trying to get everything work to do a simple 2 account multibox. To setup ISboxer and Inner Space, I followed this guide: http://isboxer.com/wiki/WoW:Quicker_Start_Guide. Everything seems to be setup correctly, however two undesired things are happening.

1. Every time I launch my character set, Inner Space opens WoW directly (no launcher, see #2) and then a second or two later opens my second WoW window. That's as far as it gets. WoW crashes here, sometimes right away and sometimes not until I try to type in my password. I often get error #132, access issues, and I sometimes get no error message at all. I have tried setting my character set to launch using WoW-64.exe directly, using the provided WoW Default profile, using the WoW launcher, as well as switching between DX11 and DX9 in WoW's settings and their respective profiles in ISBoxer. The crash seems to be the same regardless of how it's launching WoW. Does it make a difference that my in-game settings are to Windowed (Fullscreen)? I've put my diagnostic report up here: http://pastebin.com/5MV6R7gw. I also made sure I have the boxed checked to run 64-bit Inner Space, and it seems to be running that version.

2. I can't get ISBoxer to launch WoW using the launcher for the life of me. It simply refuses and goes straight into launching WoW-64.exe it seems. I've looked at this http://isboxer.com/wiki/HOWTO:Autologin_through_Battle.net as well as watched a related Youtube video. I've got an Inner Space game profile setup for the launcher, but it isn't making a difference.

Let me know if any other info is needed.
Thank you for any help you can provide!

[bob]

There have been a bunch of people with login issues with WoW recently, because of server issues (Blizzard were reporting DDoS attacks), so that may explain part of the problem. I'm fairly sure these have been resolved now, but there may be the odd intermittent issue remaining.
You might try a Scan and Repair from Battle.Net just in case something went wonky with the last patch.

You have a bunch of process showing as hooking your game. It would be best to try without these running (or the applications causing these to hook into your game). Anything with an Overlay has a good chance of being problematic.

Code:

40. c:\program files (x86)\razer\ingameengine\64bit\rzdspsrv.dll [1.0.12.8578] [Razer, Inc.] [RddUm remote process overlay module]
42. c:\program files (x86)\razer\ingameengine\64bit\RazerHook64.dll [1.0.0.1] [Razer Inc.] [RazerHook]
50. C:\Program Files (x86)\TeamViewer\tv_x64.dll [11.0.64630.0] [TeamViewer GmbH] [TeamViewer 11]
93. \\?\C:\Users\Matt\AppData\Roaming\discord\0.0.295\modules\discord_overlay\1\overlay.x64.dll
95. \\?\C:\Users\Matt\AppData\Roaming\discord\0.0.295\modules\discord_overlay\1\libcef.x64.dll

Other than that, the process is fairly standard.
Shutdown non-essential processes/ background applications, uninstall AV/Antispyware (these things can't be truly disabled), and it should eventually work. Cry about what was causing the problem because it is very essential. Move on (and maybe put the other stuff back).

As for using the Launcher. Inner Space should have several standard profiles that it configures for WoW (if it managed to locate it originally - if you have to add it manually then it wont have all these).
World of Warcraft Default Profile -> this one uses the World of Warcraft Launcher.exe
World of Warcraft dx9 32bit -> this one uses the wow.exe
World of Warcraft dx11 32bit -> this one uses the wow.exe
World of Warcraft dx9 64bit -> this one uses the wow-64.exe
World of Warcraft dx11 64bit -> this one uses the wow-64.exe

There is no real need for you to try and change any of these. Behind the scenes, even if you select the 32bit options, Inner Space knows that WoW has a 64bit executable, and depending on the setting of the Inner Space configuration, it may switch to use the 64bit executable anyway. This is controlled by the "Use same-bit game clients if possible" option, which you can find by right clicking the Inner Space icon in the system tray and selecting Configuration.
Worth noting that this option is there to resolve an annoyance with Windows 10 where WoW 32bit didn't like working very well with Inner Space 64bit, and vice versa, so if you want to go to 32bit, you are better off unselecting the "Use 64-bit Inner Space uplink" option, and then Exiting Inner Space (right click the system tray icon, select Exit), and starting it up again.

Thanks for the quick reply! I repaired my game files using the Battle.net launcher, it did say it needed a small update. I then completely reinstalled the launcher and disabled Razer and Discord's overlays. I did a quick reboot after that and all seems to be working great now!

Thanks again for your help.