World of Warcraft 7.3.0 Compatibility - Update Sep 10 2017

Here is the actual pastebin of the compat report https://pastebin.com/d1yWtaeX

I had already disabled the razer synapse software before running the test. I never meant to not include the results but I was just stating that the results point me to being patient and you guys will fix it when you are able to.

Here you go Lax. Diagnostic Report with launcer running and at the player screen..........https://www.zerobin.net/?8f50ff59394883 ... nlt4pqfU4=

So guys who uses Win7. I just installed Win10 and IsBoxer works good on it. Reccomend to do that to everyone.
Lax, you know that but I must say : I love you and your awesome multibox software. Fml but i cant play without it Good job! Keep going. Hope you can make updates more faster next time.

So guys who uses Win7. I just installed Win10 and IsBoxer works good on it. Reccomend to do that to everyone.

I've considered this, but worried my other software may not work with Windows 10. If it comes down to that, I will though. I'm really missing my five feral kitties.

Boom https://pastebin.com/TKeWF0FD Diagnostics report. Win 10, 64 bit.

Your issue is the Razer software described in my post; you need to do what the above poster did

Actually no it isn't I've tried launching the team and single slots with the absolute bare minimum of processes running, that included uninstalling my graphics & audio drivers, and my anti virus. It still doesn't work... Win 10, 64 bit

Updated Diagnostics report running the bare minimum of processes that don't re-open themselves: https://pastebin.com/LXNSDVjP

After the first time I was able to successfully launch the Isoboxer, I returned the settings of the patcher file upload to its original location (removed the check mark for loading the test files).
Iner Space rolled back to the previous version.
 
I also ran into the old problem: "E \ WoW \ WoW-64.exe could not be executed .The process unexpectedly ended."

Only when I returned the check mark to the place, I was able to start the group.

That worked for me. I turned off Razer, launched my character set and turned on Razer, works fine. Easy step until, or rather if, it is ever resolved. All I care about, it's working. I don't care if I have to take an extra step in turning Razer on after I launch. Even if I have to do it each time I launch a new team, it's not that difficult. Don't get me wrong, I won't be angry if you are able to fix it so I don't have to take that extra step, but I'm not concerned about it either. Thanks, lax.

I'm up and running again with the new patches on Windows 10, but I'm back to having the "Wow unable to start up 3D acceleration" problem. My Inner Space configuration is setup for d3d9 and I've even added the SET gxApi "D3D9" setting to the appropriate WTF files. It will work on a single monitor after redoing the windows layout, but fails each time trying to use a windows layout with my second monitor. My monitors are not set up as SLI. Each one runs independently of the other. But, at least I can play again.

Thanks for the hard work Lax. Glad to hear you figured it out.

I'm having some trouble running the Patcher. When I right click on the Inner-Space system tray icon and select "Patcher" from the popup menu it displays the Inner Space Uplink frame, but nothing else. The content area of the Uplink frame is completely empty, and their is no options to select a development build. I am currently running build 6174.

Is there a way to force it to update without using the patcher?

Thanks!

I've tried completely uninstalling / reinstalling / rebooting, everything. The "Patcher" option is doing nothing. The only installer I can find on the website is for the same build I have #6174. Is there any way to force an installation of the hotfix?

Thanks!

[lax]

I'm up and running again with the new patches on Windows 10, but I'm back to having the "Wow unable to start up 3D acceleration" problem. My Inner Space configuration is setup for d3d9 and I've even added the SET gxApi "D3D9" setting to the appropriate WTF files. It will work on a single monitor after redoing the windows layout, but fails each time trying to use a windows layout with my second monitor. My monitors are not set up as SLI. Each one runs independently of the other. But, at least I can play again.

Your Window Layouts may be referencing old names for your monitors. Re-creating any of the affected Window Layouts should correct it for the teams using that layout