While there are many of us enjoying the splendor that the 64-bit
WoW client brings us, the upcoming patch 4.3.3 (which is likely to hit this week) will break this client. The 32-bit client will still work, however, and for the time being, everyone will need to use that.
We do not know how long it will be until a new, functioning client will be released.
Furthermore, if you are running the 64-bit client, according to Blizzard you need to delete the following files in order for the patch to work properly:
-
Wow-64.exe (PC)
-
MovieProxy.exe (PC)
-
Battle.net-64.dll (PC)
-
World of Warcraft-64.app (Mac)
More information on this issue is
available on the support website. If all of this discussion sounds like an alien language to you,
check out our brief explainer.
And of course, when a new 64-bit client appears, we'll let you know right away.
Tags: 64-bit, 64-bit-wow, breaking, patch-4.3.3, patch-4.3.3-64-bit, wow-64-bit, wow-patch-4.3.3, wow-patch-4.3.3-64-bit
Filed under: News items
Reader Comments (Page 1 of 3)
ravenpoe8 Feb 27th 2012 9:16AM
Ah the price of progress. Will be worth it in the end though.
Revynn Feb 27th 2012 9:19AM
Maybe I'm just overtired, but I find this . . . Kinda hilarious.
Flarebear Feb 27th 2012 9:19AM
It doesn't make much sense for them to release a new client, then break it right afterwards. :(
wowsitemail Feb 27th 2012 9:35AM
They didn't release it. They've been pretty clear that it's out there for testing and if you choose to use it you'll probably run into things like this.
Buran Feb 27th 2012 9:25AM
Disappointing. I guess it's back to manually flipping the Large Address Aware bit with every patch so that this application finally uses more than 2GB of the 12GB of RAM installed in my modern 64-bit system.
bluespacecow Feb 27th 2012 12:10PM
Client's built with the LAA flag turned on by default now.
Has been for a while actually.
ChaseHammerJ Feb 27th 2012 9:25AM
:P I ordered a new computer and one reason was to play WoW on max settings and use the 64bit client...I suppose that dream is busted.
paragorillabear Feb 27th 2012 10:35AM
Ditto (except I built it instead of ordering it).
*le sigh*
ChaseHammerJ Feb 27th 2012 11:23AM
well i built is just had someone else assemble it lol I could do it but it only cost me $20 for someone else to so why not.
bluespacecow Feb 27th 2012 12:13PM
Why ?
For every build that's come out on the 4.3.3 PTR there's been a 64 bit client build as well.
This support article means absolutely nothing for the future of the 64 bit client.
If the patch went live right now it wouldn't take Blizzard that long to put up a new 64 bit client. Baring unforeseen circumstances possibly in the area of a few hours.
Rédßèárd Feb 27th 2012 9:29AM
I don't know, maybe its me..... but I haven't noticed any performance improvement with the 64bit client. I'm not home with the PC now, so I can't speak to it's exact specs but its a Win 7, 8GB RAM at least 2.8 processor with a higher end Radeon video card and yet it only performs as well as when I used the 32bit ver.
Perry Feb 27th 2012 9:46AM
As your RAM goes higher than 8gb, you'll notice more of an improvement. Of course, using some sort of CrossFireX for graphics (where you link 2 or more graphics cards will also give you a lot of improvement. The other thing I noticed is when I run WoW off of my clunky 2TB HDD, it still loads a lot slower than if I were to run it off of my 128gb Solid State Disk. Now is a great time to pick up a SSD, the prices are low, and storage is way up!
Como Feb 27th 2012 9:52AM
@ perry
As far as I know direct x addresses the memory management for the video driver and that is always running in 64bit mode on a 64bit system. I think this only affects system memory.
Drakkenfyre Feb 27th 2012 10:46AM
Perry, no offense, but you notice it loads alot slower on your hard drive than your SSD? No shit? It's a SSD. It's a hundred times faster than your hard drive. 64-bit or not, it's still going to be faster than a hard drive.
Ez Feb 27th 2012 11:14PM
Why do you all mess with Perry? He's a youngster for crying out loud! You all think your crap doesn't stink but i got news for you!
Perry Feb 28th 2012 1:01AM
@Como: I was suggesting that two graphics cards might give him better results than one, but thanks for the info :)
@Drakkenfyre: I was trying to say it in a nice manner. Ofc I know that SSD is much faster (not 100x faster, though)
@Ez: thx, but how do you know how old I am?
Edge00 Feb 27th 2012 9:29AM
Booooooooooooooooooooooo
Como Feb 27th 2012 9:42AM
This is stupid, first wow has no need of a 64bit client, more likely it is slowing down the program rather then speed it up unless you are using a ton of add-ons.
Second it's 2012 how is blizzard still having difficulty supporting a 64bit client.... Blizzard I knew ye well and then activision came up and ruined you.
Unexplained Bacon Feb 27th 2012 9:58AM
This is a fairly lamesauce comment. As has been stated before, and I am sure will be stated again, this was a beta 64-bit client. If you chose to be an early adopter you shouldve known issues could possibly arise. Blizzard isn't having trouble supporting it. They haven't even formally released it yet.
And btw, there are any number of popular programs that don't have 64 bit clients yet, despite it being 2012. It's pretty harsh to single out Blizzard.
Just my 2 copper.
Como Feb 27th 2012 10:04AM
I understand it's beta, that doesn't mean that a beta should be released when it's going to completely break the game, that's what internal testing is for.
My point was more about how it's stupid at all that blizzard is wasting time on a 64 bit client and that wasn't clear but the reason most programs don't have a native 64 bit runtime is not because it's difficult to support, it's because it's slower for most of the programs and is actually a performance loss. WoW doesn't need a 64 bit client, it needs to stop hemoraging customers like it just got out of a fight with ony ;) They aren't leaving because of lack of support for 64 bit, it's because there is very little new content, and has been less and less since BC. (cata to be fair had a ton of content, but much of it was for lower then 80's so that is what it is)