Project Lore

This morning while trying to login (fruitlessly, of course), I ran into a small error that seems to be pretty common. The WoW Launcher would download Patch 3.2, but would then give an error, "Failure to Apply Patch," or "Unable to Apply Patch." After trying the repair utility, a quick search reveals the steps to fix the problem:

• Go to the folder where WoW is installed. I find the easiest way to get there is simply right clicking the shortcut I use to launch WoW and choosing "Open File Location"
• Right Click on Launcher.exe
• Choose Run as Administrator
• If a UAC window pops up, choose continue
• Let the patching commence

I know this issue caused me some frustration during the time we are all waiting for the latest version of WoW to become active, so I hope this helps you out! Anyone else have any issues or solutions for the newest patch?

Click to read more ...

Wow.  What a mess the Echoes of Doom patch has been.  I do not know about the rest of you, but I have had a hell of a time with the latest content patch.  Blizzard Entertainment warned us that the maintenance would be extended, but my main server experienced over 12 hours of down time. Then it was hit with shoddy performance when the realm finally came up.  In fairness, I would rather take the downtime now, than when all the new content from Wrath of the Lich King goes live.  Of course, that is the exact reason Blizzard does these patches ahead of time, to work out the kinks. My server being down was only half the battle though.  I don't think I have mentioned this before, but I actually play World of Warcraft on three separate computers.  Keeping the WoW installations on the myriad of computers I have is difficult enough for common play (no, I don't want to carry around my WoW installation on an external harddrive).  So you can imagine how annoying it is to go through the motions of patching and reinstalling addons on three computers for a major content patch.  Tools like  the BLASC Client can only do so much. My two Windows XP boxes patched up nicely, although I had to transfer the patch from one box to the other because a download was corrupt.  Thankfully, Blizzard's repair tool managed to revert the MMORPG to 2.0.0 rather than having to reinstall everything.  Things went smoothly after that. My Windows Vista 64-bit box has been, and continues to be, a bit more difficult though.  I have the User Access Controls disabled - because they suck - and still get harassed by Blizzard's installer telling me to move the files to a public directory.  I told it to do what it wants and it failed to copy data from the original installation location into the public area.  I figured it was a PEBKAC issue and tried again, this time not moving the files.  Failed again with much the same error, unable to copy data. I then did a whole bunch of dumb things like copied the patch files into the installation folder, ran it as administrator, ran it as administrator while on one foot and ran it as administrator while I played The Witcher.  At this point I was worried about the installation as a whole, thinking that the failures may just cause a chain reaction of destruction.  Double-clicked the repair tool (as admin, while I prayed to Pagan gods) and got reverted to 2.0.0 on the Vista box. It took me awhile, but I finally gave up in frustration and began to download a new copy of the patch.  Hours later, in fact, it ended up being early this morning, it completed and installed correctly.  Looks like I was blaming Vista for another corrupted download.  Sorry Microsoft! Things are up and running on all of my computers now, and I have begun taking a hard look at which specs to select for my Rogue and Priest.  I think I am going to roll with a healer Priest from now until level 80, so that should be different.  How did the conversion to the Wrath of the Lich King's launch screen - which rocks by the way - go for all of you?

Click to read more ...