64-bit version of HB and 32-bit WoW problem. Will it ever be released? In near 2014 year 32bit is quite odd. BTW can't run 32-bit version after update using "rename wow-64 method". It runs and it is 5.4.1 but says it is wrong version.
Tried 2 ways. 1) through battle.net starting 32bit version. It started, but says "wrong version or file corrupted". The version is right, and I gone thorough repair already. 2) Starting wow.exe after rename of wow-64.exe. Same problem.
Well, the launcher will launch the 32 bit client now, if you want it to do so(choose launch wow in 32 bit mode" in the launcher menu. However, it seems like I am still getting the error you are talking about, even if I do so.
this no longer works, the game doesnt let you log in unless for the wow-64.exe is in the folder so renaming it or moving it is no longer a option. waiting for HB release to test the HB launcher.
I tried everything I know. It is just corrupted. I think we will have a tiny bit of problem even when HB realese...
Technical Support - Forums - World of Warcraft we are not alone. 32-bit version is just broken somehow.
Looks like HB might have to be recompiled to either detect 64-bit or run in 64-bit itself. Although, I'm looking for solutions.
Sorry but has the new hb been released or have I missed that post ? I am on my iPhone ATM But if your running old hb then it will give you an error of wrong version don't forget. The issues on the blizz forum just seem to be a slight corruption and just need a repair by the looks.
Blue Post: `Hello, Unable to validate game version comes about when the client version mismatches with the server version. As said earlier in this thread, this only affects the 32 bit client. If you're able to run the 64 bit client, please select this as an option and you should be able to get into the game. We've an article on switching between the two here: battle.net/support/article/how-to-toggle-32bit-mode-world-of-warcraft Of course this isn't possible for everyone. If you have to use the 32 bit client, we're looking into this now. It does seem to be happenning to anyone using the 32 bit client (I've reproduced it here) and I'll get back to you after I've tried some things to get it to work.`