Patch 2.0.5 Issues
by Chris Miller 
Jan 14th 2007 at 10:25AM
Apparently patch 2.0.5 came out overnight last night or early this morning. A lot of users are getting an "Unable to validate game version" error (pictured above) along with a myriad of other connection problems. The official forums are also down, or so slow as to be effectively down. I'm going to guess that perhaps your game version is fine and this will sort itself out in the next few hours as the patch gets distributed.
Thanks to everyone for submitting this as a topic suggestion, there's too many of you to credit directly.
UPDATE 10:54 from the in-game Breaking News:
"The 2.0.5 client-side patch has caused issues with our authentication system. These issues can cause players to be suddenly disconnected from the game, as well as prevent them from logging in to the game. We are working to resolve this issue as soon as possible and will provide you with updates as soon as they are available."
UPDATE 11:30
The realms are accessible, or at least mine is. The forums are also back online and usable.
Reader Comments (Page 1 of 2)
Cal Jan 14th 2007 12:38PM
I also had problems downloading the patch, anyone eles?
Gist Jan 14th 2007 12:47PM
So, what does 2.0.5 bring to the party, and should we expect 2.0.6 tomorrow, and 2.0.7 the day after that?
Barista Jan 14th 2007 11:33AM
Just glad I has SOME source of information. Not being able to hit wow forums isn't helpful. Virus scan just in case. lol
D-5 Jan 14th 2007 11:33AM
I'm still on patch 2.0.4 and I'm getting this error.
BTW, I'm a university computer science student, so while many must be seething at Blizzard right now, I feel for the team that mis-handled the code that caused this error. This is the type of thing that would get you fired (Not properly testing before sending out your code).
Alwyzbkillin Jan 14th 2007 11:33AM
I am getting Disconnected from Server when I login. I have checked the forums before they went down and a tonne of people are experiencing the same issue.. Hopeuflly they fix this.. I know alot of people are being put out.
CTDeLude Jan 14th 2007 11:40AM
Yea, when I saw that this morning I though I had been hacked or something...
Good to see it's something Blizz side.
Zerbe Jan 14th 2007 11:50AM
I was able to get the patch from a mirror site, but now Im getting the same error that everyone else that patched it getting, the dread "connecting->authenticating->disconnected from server".
BlizzardHasTerribleQA Jan 14th 2007 11:49AM
Wow, you know you're in trouble if a college CS kid is telling you that your code sucks. But welcome to the real world.
While it's highly desirable for companies to fire people for releasing crap, that just does NOT happen. If it did, Blizzard would've had to fire their entire development and QA staff -- this is not the first time they screw stuff up! I think the only other MMORPG company that has screwed up more is SOE but SOE had a few years head start!
For you QA people out there! Get a freaking clue! I can count the number of useful QA people that I've had over my 10+ years in the industry on one hand (and I still would be able to even I lose a couple of fingers!)
Remil Jan 14th 2007 12:17PM
GG
That's what you get for patching on a Saturday night with drunken devs....
Jeff Jan 14th 2007 11:57AM
I'd like to know if there are any users who are able to log on now with 2.0.5 or if it's just a large number.
Nick Jan 14th 2007 5:15PM
Did I miss Blizzard getting bought out by Sony overnight. Their recent string of PR blunders reminds me a ton of my favorite Japaneese target.
Charlie Jan 14th 2007 12:09PM
Didn't download the patch, but after many attempts and was able to get in. About five minutes ago.
D-5 Jan 14th 2007 12:20PM
I've done QA for EA and Ubisoft and I would like to think I did a competent job. I think the problem with QA is the ones companies find have a hard time communicating with thier supervisor/boss/whatever which leads to. I'm not judging others, but I've talked briefly to other QA people and usually the only thing I get out of them is "The game will be fun when released" and "It sucks having to play the same level over and over again".
Of course, this is something different. It's a silly login error that should have been caught by whoever was testing this. In my experiences with QA, you repeatedly test sometime until you "break" the code/game. Seems like Blizzard's QA just decided to login once and began having fun.
Zerbe Jan 14th 2007 12:41PM
There is a good patch mirror here:
http://a.wirebrain.de/wow/
Kirke Jan 14th 2007 12:48PM
Apparently if you got up early and installed the 2.0.5 patch you will not be able to log on. However if you did not get the 2.0.5 patch and still have 2.0.4 then you can now log on. The only solution at this point for people with the 2.0.5 patch is to re-install WoW.
Jeff Jan 14th 2007 12:52PM
Most people who didn't download 2.0.5 can log in. They're currently working on a fix for the instant disconnect issue for those with 2.0.5.
According to Drysc "The issue experienced was due to an extremely large amount of players attempting to download the patch, which was being served directly instead of through the Blizzard downloader, which was crippling our services including the authentication system."
James Jan 17th 2007 9:35AM
@ Number 5:
You must be a real pleasure to work for. Patient, understanding, realistic. Are you hiring?
And yes, Blizzard has released crap. Its just all crap, the whole thing. And, there you are though, paying 15$ bucks for crap. If you're so unhappy, cancel your account. Actually, wait, you appear to be in the business. Write a detailed letter to Blizzard detailing how they might improve their operation, because they really need help dealing with their 8 million unhappy subscribers.
Oh, and #3, its touching that you think QA errors get you fired. I know that Microsoft fired hundreds of people over Windows XP because of the security issues and bug problems. Oh, and lets not forget Internet Explorer, or MS Office. Or game manufacturers that have to release patches for buggy games post-release. Did you know too that Bill Gates kills a kitten every time a new security flaw is found in Windows XP? Did you also know that none of this is true? Software companies do QA/QC, miss stuff, releases a patch, and the world goes on. Firings don't happen much, because thankfully, people are a bit more understanding than you and #5. Ya'll should start your own company.
Moorkin Jan 14th 2007 8:35PM
FYI I use the WoW-head client to upload data from inspects and my own character data. It normally runs when I play wow, but I got this error message so I closed it. WoW ran fine then.
monkeyhouse Jan 14th 2007 5:35PM
The worst thing of all this was the official advice on the forums (when i got there).
Blizzard basically said that everyone who got that error had a Trojan and had to get a new virus checker and had to clean their system! Now i am a software professional and my system is pretty secure and this was unbelievable news to me! And i can imagine the panic it spread!
in this day and age you DO NOT throw about the word virus and trojan lightly and whoever did that at Blizzard should be hung for being so irresponsible.
Surprisingly, it turns out to be their problem all the time - seems to be the usually Blizzard support line. Forget about Sony, they are taking a page straight out of Microsofts Tech Support training guide!
RollsMyEyes Jan 14th 2007 7:59PM
In preparation for BC, I will...
1. Make sure to log my main toons off in inns.
2. Buy the expansion
3. Do not install the expansion but only upgrade my accounts via the web interface and hope that will allow my 60th toons to get rested xp.
4. Turn off the computers; go out and have fun with my friends for two to three weeks.
** after two weeks of heavy drinking **
5. Check the forums to see if the dust has settled
6. Then and only then, will I attempt to play WoW again.
All the while, I expect the following:
1. My 60th toons will collect rested xp in their respective inns.
2. ALL of the servers will be in a constant state of instability, unplayability (is that a word??), and general disarray.
3. Plenty of players will be whining about how they can't play the game.
4. Blizzard will post multitudes of apologies, asking of patience, refunds of lost playtime, and the usual sitting on their useless behinds and the scratching of their collectively empty heads as they muddle through yet another patch. Except, this one is a biggie (it's their first expansion!)
While all of this chaos is going on, I'll be drinking beer and getting trashed knowing that I don't have to deal with any of this crap!
Let's see if I'm right: The degree of ineptitude of the Blizzard staff during the first 100 hours post expansion will rival the cluelessness of the Democrats' first 100 hours in power!