Cant get wow running in 32 bit

[botmaster3000]

[22:11:44.858 N] Honorbuddy v2.5.9775.726 started.
[22:11:46.686 N] Logging in...
[22:11:49.385 N] We couldn't find a proper WoW to attach. There are 64bit WoW processes running and Honorbuddy only works with 32bit version.

Please use the Launcher in Honorbuddy folder to launch the game and Honorbuddy.


This is what the Log say.. But I've tried using the launcher but since I don't even have a 32 bit wow version in my WoW folder anymore I can't really get anything done using the launcher. I used to have a 32 bit wow.exe in my wow folder but It's gone now.. I bought a 3 day trial Honorbuddy version and I'm afraid it's going to expire even before I get it to work -.- Please help!

 

[huffwin]

Go into the folder where wow is installed at look for the launcher with wow64 and add a _ in the name and just click on the different wow icon there and it will run in 32 bit if you need help pm me here or add my skype at huffwin ill help you out getting it running

 

[Cisem]

Choice 1
Use Honorbuddy Launcher

Choice 2 (The best option)

1. Go to the installations folder of World of Warcraft.
2. Select the file Wow.exe And create a new shortcut to it. Then put the shortcut on your desktop.
3. Go to your desktop, and select your new shortcut. Then click properties on it.
4. Click on ?Shortcut? tab.
5. In the field ?Target? put in this: "Crogram Files (x86)World of WarcraftWow.exe" -noautolaunch64bit -noautolaunch64bit -launch -uid wow_engb

 

[botmaster3000]

I appreciate it Cisem but having quite a probleme to find where it is u want me to go cause I don't have english version of windows haha but I'm trying ^^

 

[botmaster3000]

NVM I did understand what U told me to do now.. but it doesn't work Cesim. It says something like this The name specified is invalid. "C: Program Files (x86) World of WarcraftWow.exe, Make sure the path and filename are correct. (MY translation from swedish) ^^

 

[botmaster3000]

And I cannot use the HB launcher... since I dont have a working 32bit exe for wow.. I used to have one I think but it just randomly disappeard.

 

[Grim32]

You need a \. Okay. Find the link you use to start WoW. Right click -> Properties ->Find target / Open File Location. Look For WOW64 and call it something different like wow64.old

-Grim

 

[eddielemon22]

im having the same problem. ive tried renaming ive tried using a hardlink but nothing. wow just pops up and says its performing initial setup but freezes everything was working before 5.4.7

 

[DX123]

You have to launch it directly.

1) Move or rename the 64-bit one (wow-64.exe or something)
2) Run wow.exe (not their launcher, battle.net or anything like that)

That is how I did it (running windows 7 64bit). I had to do it that way, without HB's launcher, because for some reason I have to set wow.exe to "high priority" in order for it not to stutter. HB's launcher takes control of wow.exe and won't let me promote the priority.

DX123

 

[toliman]

for some reason I have to set wow.exe to "high priority" in order for it not to stutter. HB's launcher takes control of wow.exe and won't let me promote the priority.

if you want it scripted, you can edit a separate task using wmic. this does work better in windows 8 than 7, for reasons i can only speculate are ... it's windows.

normally, you'd use

Start /high Wow.exe

, or

Start /abovenormal Wow.exe

but in cases where you use a relogger, or a SVN updater script, and you're not running WoW, or you want it to load normally, and then boost it up,

wmic process where name="wow.exe" CALL setpriority "high priority"

you can also use this to elevate Honorbuddy.exe to "above normal" but it won't change much in terms of resources.
if it doesn't like "high priority", use the number 128, realtime is 256, idle is 64, above normal is 32768, normal is 32.

don't use realtime, high priority may also prevent wow from working properly because it won't share resources with other apps, like HB, or antivirus apps, etc and you'll get IO issues and other problems with apps that are sensitive to shared resources.
your experience will vary.

you can also close any leftover commands using

wmic process where name="cmd.exe" delete

use sparingly. wmic can also shut down or reboot a PC, even remotely.

depending on your PC, wmic may require having elevated permissions, which can be fixed by launching the script with higher permissions, test first.

and i'd wait a few seconds for the wow or HB process to launch in a script, which you can do with

ping -n 20 localhost >nul 2>&1

where -n 20 is 19 seconds paused. you can change this to 'time in seconds' + 1 if you want a shorter or longer pause.

 

[Misc]

Can someone post a picture on how it should look like? I am so confused

 

[cjh034]

Simple fix. Go to your WoW folder. Simply delete these three files...

Battle.net-64.dll
MovieP roxy.exe
WoW-64.exe

Presto! You're back in business.

 

[toliman]

Simple fix. Go to your WoW folder. Simply delete these three files...

Battle.net-64.dll
MovieP roxy.exe
WoW-64.exe

Presto! You're back in business.

the problem is, when the game is patched, those files will be repopulated.

If you use the new Battle.Net beta client, you can set it to launch 32-bit WoW, which saves a lot of effort.
If you use a relogger, you'll have to use the shortcut commands in the relogger settings or it won't load the 32 bit version.

that said, renaming the wow-64.exe is pretty simple,

you can also create a dummy wow-64.exe using mklink, so if the launcher tries to open the 64 bit, it will actually be opening the link, which points to the 32 bit version instead (called a symlink or soft link) .
saves having to edit the shortcut data, but again, when the game patches, you'll have to remake the link.

this should also let you use a relogger as normal again.

cd "c:\Program Files\World of Warcraft\"
move Wow-64.exe abc.bak
mklink Wow-64.exe Wow.exe

 

[amputations]

Its very simple!

Open WoW launcher, choose options and check "Start WoW in 32-bit mode".

Done!