bump... as i heard reinstall doesn't work

---

Q u o t e:

You can try logging onto a different user in Windows, and then try starting up World of Warcraft again.

You can also start World of Warcraft as a different user through these steps:

Right click on the World of Warcraft shortcut.
Select "Run As..."
Click on "The following user:"
Select a different user (like Administrator or Compaq User).
Type in a password if necessary.
Click Ok.

If you don't have a different User Account, you can create one through Control Panel, and then User Accounts. Please put the newly created User Account into the Administrators group.

---

Running WoW as a different user worked for me.

Although it seems like a backwards fix. Also, those instructions appear to be for Vista (?), you have to do it differently in XP (not everyone uses Vista Davidhc).

Anyways, clearly this is a bug in the patch as I have no trojans. Would you guys mind fixing this bug?

F

Edit: Reading through the other posts, I´d like to comment that I didn't have to reinstall or anything. Just ran WoW as a different user.

Found a Solution after all night of trying and trying.
Download SUPERAntiSpyware. Just do a search and you will find the website to get the program.
Do complete system scan. After is done and all the Trojan have been erased your WoW will work normally.
It seems that this Trojan is not found by regular antivirus. I tried Nod32, Norton, MacAfee, and other. And only the SUPERAntiSpyware tool did the trick
GL

Finally able to play.
I tried full scan with Windows Live OneCare. Scan with Trend free online scan. of course nothing came up as i dont 'browse' the web. I ran full chkdsk a few times with no HD problems. my final fix was not only uninstalling & reinstalling. I uninstalled and manually deleted warcraft folder. than defrag, chkdisk, installed wow using WoW-2.0.0-enUS-Installer, installed WoW-BurningCrusade-enUS-Slim-Installer, DL the full 923mb 2.4 patch.

My only question now is, will i eventually crash and go thru this again? I was able to play for over an hour tuesday after servers came up before i crashed with 132 error followed by validation errors. Could my origianl corruption have come from going to the new island? And why so much problems using the repair tool or reinstalling without deleting C:\Program Files\World of Warcraft ???
Remember, I have deleted WTF, Cache, Data & Interface folders before using repair utility.. so it wasn't anything in those folders that kept the repair tool from fixing it.

Anyways try uninstalling, manually delete folder C:\Program Files\World of Warcraft, install the 2.0 warcraft, install BC, than let it DL the 923mb 2.4 patch. I repeat.. delete folder.. that was the only difference for me.

tried all kind of antispyware and intiviruz... i still can't play ... same error.

---

Q u o t e:



Running WoW as a different user worked for me.

Although it seems like a backwards fix. Also, those instructions appear to be for Vista (?), you have to do it differently in XP (not everyone uses Vista Davidhc).

Anyways, clearly this is a bug in the patch as I have no trojans. Would you guys mind fixing this bug?

F

Edit: Reading through the other posts, I´d like to comment that I didn't have to reinstall or anything. Just ran WoW as a different user.

---

It looks like this worked for me as well. Definitely something odd with the patch.

bump

Bump nothing works...

bump

I finally got Warcraft to work again after encountering this issue; I'm posting here in the hopes that it might help others who were in the same boat.

After doing all of Blizzard's recommended courses of action (scanning for viruses/trojans, running the repair utility, and uninstalling and reinstalling the entire game and redownloading the patches), the game still would not work for me, was giving the same version error (21370) that several other people were reporting here.

I tried running it as a different user (on an XP Pro machine), since some people here had reported success with that, but all it did was crash the game. However, something related to it did work:

1.) Make a new user on your computer with administrative privileges. As mentioned above, the account must have a password.

2.) Log off your normal user profile and log on to the computer with your newly-created administrative level account.

3.) Start Warcraft under this new profile. When I did this, I had no problems at all, the game started up without the validation error.

4.) Exit Warcraft, and switch back to your original user. Start Warcraft now. For me, the validation error no longer appeared on my original account once I had successfully logged in as the different user, and I can now play the game error-free on my original user account.

Not sure why launching the game as a different user fixed it for my original user account, but it did. For those of you at the same level of frustration as I was, give it a try. Hope it helps.

I fixed my problem.. I did everything blizzard told me to do but nothing worked... so i went on google searched up *superantispyware* and i downloaded it.. ran my computer through it and it seemed to pick some trojans i didnt have before patch.. i think patch 2.4 gave it.. but yeah.. ran the complete scan and rebooted computer and i was able to play again. hope this works

After my fiance reformatted his hard drive, which failed to fix his problem, making a new admin user did work. He's baffled and furious; self-described as at all points furious.

It is also worth noting that before reformatting the hard drive, we followed all of the directions given by Blizzard for this particular error, including uninstalling and reinstalling WoW twice. Nothing worked.

to reiterate what i wrote in the other thread concerning this problem:

i did EVERYTHING suggested, and I mean everything... besides a reformat. What finally worked was creating a new admin profile in XP. Though now I can ONLY play through that profile and doing the "run as" thing just crashes my WoW. I guess Id rather be able to play it than not at all... so this minor inconvinience is going to be begrudgingly accepted.

I'm going to go out on a limb here and assume everyone has switched to the battle.net account system that uses your email address?

Patch 3.1, I can log in with my wifes non-bnet account and no problems, blank screen so far as it should since the servers aren't up, I log in using my bnet account and poof, this error appears so it's related at least in my case to the battle.net account system.