Having difficulty running IS Boxer with WoW

It seems that I cannot get my WoW client to run in 32 bit for some reason, with or without IS Boxer

http://privatepaste.com/59859a1367

Here is the paste with just the launcher running prior to selecting 32-bit

http://privatepaste.com/e9c32d1e0c

And here is the paste with wow 32 running. It places WoW in the process try but does not launch the game

http://privatepaste.com/6f867511a9

[Ualaa]

There is/was an issue with Warcraft, which isn't IS Boxer specific.

If you delete your 64-bit version, that should force the game to use the 32-bit version.
At any point in the future, you can delete the 32-bit version too, and then run the launcher to have both files patched back in.
Not sure if renaming (or moving the 64-bit version) is the same.

There were a few recent posts about this, both here and on the multiboxing.com forum.

[lax]

Definitely some programs you can try shutting down to narrow this down.

Start by shutting down Mumble (or at minimum disable its in-game overlay features) and Teamviewer.

Code:

66. mumble-g15-helper - Process ID: 4180 (F:\Program Files (x86)\Mumble\mumble-g15-helper.exe)
67. mumble - Process ID: 8308 (F:\Program Files (x86)\Mumble\mumble.exe)
109. TeamViewer - Process ID: 2824 (C:\Program Files (x86)\TeamViewer\Version8\TeamViewer.exe)
110. TeamViewer_Service - Process ID: 3180 (C:\Program Files (x86)\TeamViewer\Version8\TeamViewer_Service.exe)
113. tv_w32 - Process ID: 4280 (C:\Program Files (x86)\TeamViewer\Version8\tv_w32.exe)
114. tv_x64 - Process ID: 4292

If that doesn't solve it, check for a driver update for your ATI/AMD video card. http://support.amd.com/en-us/download

The Lucidlogix Virtu MVP (dual GPU) could be causing a problem; if this is not updated by the ATI/AMD driver update, try specifically going to the Lucidlogix site -- http://www.lucidlogix.com/driverdownloads-mvp.shtml; they also have a free upgrade to Virtu MVP 2.0 Pro http://www.lucidlogix.com/free_upgrade.shtml

cfosspeed is another potential culprit.

Lastly, if none of that helps, I would try uninstalling AVG to see if that's it. If it is, then it's likely that a certain feature could be disabled and still use AVG (e.g. the "Secure search" could be it)

Code:

9. avgcfgex - Process ID: 8532 (F:\Program Files (x86)\AVG\AVG2013\avgcfgex.exe)
10. avgcsrva - Process ID: 4348
11. avgcsrva - Process ID: 548
12. avgemca - Process ID: 3536
13. avgfws - Process ID: 2136 (F:\Program Files (x86)\AVG\AVG2013\avgfws.exe)
14. avgidsagent - Process ID: 2412 (F:\Program Files (x86)\AVG\AVG2013\avgidsagent.exe)
15. avgnsa - Process ID: 3436
16. avgrsa - Process ID: 500
17. avgui - Process ID: 4784 (F:\Program Files (x86)\AVG\AVG2013\avgui.exe)
18. avgwdsvc - Process ID: 2784 (F:\Program Files (x86)\AVG\AVG2013\avgwdsvc.exe)
58. loggingserver - Process ID: 3392 (C:\Program Files (x86)\Common Files\AVG Secure Search\vToolbarUpdater\17.1.3\loggingserver.exe)
112. ToolbarUpdater - Process ID: 3264 (C:\Program Files (x86)\Common Files\AVG Secure Search\vToolbarUpdater\17.1.3\ToolbarUpdater.exe)
115. vprot - Process ID: 5020 (C:\Program Files (x86)\AVG SafeGuard toolbar\vprot.exe)

[lax]

There is/was an issue with Warcraft, which isn't IS Boxer specific.

If you delete your 64-bit version, that should force the game to use the 32-bit version.
At any point in the future, you can delete the 32-bit version too, and then run the launcher to have both files patched back in.
Not sure if renaming (or moving the 64-bit version) is the same.

There were a few recent posts about this, both here and on the multiboxing.com forum.

The game will typically try to launch wow-64 when you run wow.exe directly, but the latest Inner Space update should block that. If using the launcher, and the launcher tries to launch wow-64, it should also pop up a message to use the 32-bit version instead (at which point the user might be inclined to look for the setting in the launcher). Deleting wow-64 should not be needed anymore with ISBoxer.

UPDATE: 64-bit client support is now available, and wow-64 is NOT blocked by the latest Inner Space update: http://isboxer.com/forum/viewtopic.php?f=22&t=5450

Almost got it working it starts WoW but then I get "Battle.net Update Agent has Stopped Working" and the game crashes

[lax]

Almost got it working it starts WoW but then I get "Battle.net Update Agent has Stopped Working" and the game crashes

Do you have Inner Space launching the WoW launcher? or WoW.exe? You can have it just launch wow.exe

The wow launcher. I'll try just wow

Still crashes

When I run WOW.exe i have no problem starting the game. If I let ISBoxer do it it launches the WoW launcher even though I have it set to run wow.exe

[lax]

If I let ISBoxer do it it launches the WoW launcher even though I have it set to run wow.exe

I'd say you don't have ISBoxer successfully set to run wow.exe then.

In the top left pane under Characters, select each Character and check the "Game" and "Game Profile" drop-down boxes. This should be set to whatever Game and Game Profile you have configured in Inner Space to launch wow.exe directly. If it's launching the launcher, then the selected Game and Game Profile are not set to launch wow.exe directly.

Ok I did that. Windows starts Wow.exe and then it shuts down after about a minute. Nothing shows on the screen it only shows up on the process tab of task manager.