Correct way to launch 32 bit client

[izastic]

1. Create a shortcut to Wow.exe
2. Right click the shortcut and select properties
3. In the Target box add -noautolaunch64bit after "\Wow.exe"

See image below

[TheQt]

You could also delete wow-64.exe, making it never launch 64bit ^^

[izastic]

Well like the title says, this is the correct way without destroying files.

For example, I use one installation folder. I bot in 32bit and play in 64bit.

How would I play in 64bit in the same installation folder if I delete the file? Go ahead smart guy explain that.

And renaming a file every time I want to play in not an acceptable answer.

[Banzure]

http://www.ownedcore.com/forums/worl...d-of-64-a.html ([How to] Force WoW Launcher to load wow 32 bit instead of 64)
This works just as well, amazed that you missed that thread.

[izastic]

Once again. That method is destroying your files.

Learn to read.

You can not play in 64bit mode if you rename the file and force it to launch 32bit all the time.

[PhillisPG]

I made a video representation of this method for our Shadow Bot users. Perhaps it will be helpful for those who do not like to read/follow instructions.

[Xcesiuss]

Once again. That method is destroying your files.

Learn to read.

You can not play in 64bit mode if you rename the file and force it to launch 32bit all the time.

Hello there,

My method is for people who is using the new battle net launcher and can't be assed typing in the auth key every single time.

Good solution though for those who like to play in 64bit mode.

[Tare69]

Not working on me. Every time it starts launcher (even link is from wow.exe) and -noautolaunch64bit is put to it. Also if I go setup to change launch 32bit it wants to start US wow, not EU. Is there some secret file in computer why this is not worked (I know that run once file in config directory).?

[front243]

Go to your World of Warcraft/WTF folder. Edit config.wtf.

Change:

SET launchThirtyTwoBitClient "1"

(Make sure it is set to "1")

[wizfor]

You could also delete wow-64.exe, making it never launch 64bit ^^

battle.net app client will detect that something is amis and fix the misnamed wow64 executable.. not a good solution