Patching Tip, or Don't Be an Idiot Like Me

[Talamarr]

Run WoW like normal people, don't launch it from keyclone. Out of habit I fired up keyclone to start WoW and begin patching and now I'm getting all sorts of errors. Even screwed up my symlink. I have no idea if the two are related but it makes more sense to run it from your base install.

UGH!

Anyone else getting:

The file "\base\signaturefile" could not be opened. If this problem persists, you may be able to solve it by uninstalling and then reinstalling the game. If you are unable to correct this problem, please contact Blizzard Technical Support. (InstallerFile::Open)
To check this installation for problems, click the "Repair" button. The Repair tool can automatically fix many update errors.

I ran the repair tool but still getting this error.

[UPDATE] Quick search seems to suggest running Updater as administrator will fix the issue. Doing that now.

[Hairball]

I would suggest never using a 3rd party application to launch WoW (save for maybe a batch file you wrote yourself).

[daviddoran]

Also another reminder to backup your wow folder before patching, just in case. I lost a lot of my macaroon bars when the last patch came out... Had to redo a lot of work.

[Tehtsuo]

I was using symlinks as well. Same error. It removed all the symlinks on my computer as well. Trying running the Updater with admin rights now to see if it works. I'll post with my results.


:edit: Same problem. Looks like I get to do a complete reinstall. Phwaw.

[aboron]

I keep a symlink to Public\Games on my slow hard drive that point to my ram ssd with all the working copies on it - which, of course, failed to update due to the symlinks. But since the ram drive could lose everything at any time I kept a plain unaltered "Games.real" directory on the slow drive with no symlinking in it for quick reloads. So one point to Acard for inadvertently saving my butt from a complete reinstall.

[Talamarr]

After another failure and more research, here's something to try if you get this error: Go to [WoW Directory]\Data\ and delete Patch.mpq (ok, don't delete it but rename it just in case). Then run the repair.exe utility in the wow root folder. It will tell WoW has a critical error and needs to be repaired. Let the repair run (it may take a little while).

Then try running the game again and let it patch.

That's what I'm trying now and will see how that goes.

[Sajuuk]

I had to redo my symlinks as well.

[Talamarr]

After another failure and more research, here's something to try if you get this error: Go to [WoW Directory]\Data\ and delete Patch.mpq (ok, don't delete it but rename it just in case). Then run the repair.exe utility in the wow root folder. It will tell WoW has a critical error and needs to be repaired. Let the repair run (it may take a little while).

Then try running the game again and let it patch.

That's what I'm trying now and will see how that goes.

This worked for me! WOOT!

If you get that error, give this solution a try before trying to reinstall.

Happy 3.1'ing everyone.

[robgfl23]

always patch just your main copy of wow through the loader. then copy the new loader.exe and wow.exe to your symlinked wow's and everything will go smoothly.

[jvriffel]

Simple enough, after trial and error with each patch I have discovered that it is really easy. Only patch your main folder of WoW. Then copy all folders/files except those that are simlinked into the other installs of WoW. Once this is done you can launch all copies of WoW as usual and only have to patch one copy of WoW. Anytime you launch one of your simlinked installs you are going to have troubles without doing it this way or a reinstall. Just be sure and backup your Interface and WTF folders on a regular basis and always before a patch.

[Yamio]

I learned my lesson after having to reinstall WoW awhile back. I have 5 wow folders on my clone machine (that machine runs 4 wows). One folder is my "main" and it's the one on patch day that I start up and patch. After it's done I redo my symlinks to that one and I'm ready to go. Easy peasy.

[Taliesin]

Since moving to Vista 64, the Blizzard updater has problems finding my WoW folder, since it needs to exist in a public space. The quick answer was to just manually download the patch then update that way. Haven't had any problems since then, even with symlinked folders.

I just symlink Cache, Data, Interface, and Screenshots (not necessary for this one, but personal preference). After patching the main folder, I just copy and paste the files directly under the WoW folder (not subfolders) to all the slave directories. No hiccups so far.

[Slauterhause]

After another failure and more research, here's something to try if you get this error: Go to [WoW Directory]\Data\ and delete Patch.mpq (ok, don't delete it but rename it just in case). Then run the repair.exe utility in the wow root folder. It will tell WoW has a critical error and needs to be repaired. Let the repair run (it may take a little while).

Then try running the game again and let it patch.

That's what I'm trying now and will see how that goes.

This worked for me! WOOT!

If you get that error, give this solution a try before trying to reinstall.

Happy 3.1'ing everyone.Hey thanks Talamarr, worked like a charm.

[sqeaky4100]

always patch just your main copy of wow through the loader. then copy the new loader.exe and wow.exe to your symlinked wow's and everything will go smoothly.This worked, and I didn't have to run any Repair.exe, or any long term things. HEre's it re-written in more plain english.



1) Delete the symlinked folders in your SLAVES FOLDERS. They should delete instantly as they are only re-directories, and don't contain any material themselves.
2) Go into your main folder for WoW and run Launcher.exe... let it update.
3) Symlink everything back up. However you do it.
4) Go into your main folder for WoW and Right-Click and Copy both Launcher.exe and WoW.exe ( they should be like 16mb each or so )
5) Go into each Slaves folder and Right-Click and Paste. When prompted, "Copy + Replace" over the current launcher.exe and Wow.exe



Seems even though you symlinked the new data +interface back up with the updated one. The launcher.exe and wow.exe are new too or something, so they must also be replaced.

[Hachoo]

Since moving to Vista 64, the Blizzard updater has problems finding my WoW folder, since it needs to exist in a public space. The quick answer was to just manually download the patch then update that way. Haven't had any problems since then, even with symlinked folders.

I just symlink Cache, Data, Interface, and Screenshots (not necessary for this one, but personal preference). After patching the main folder, I just copy and paste the files directly under the WoW folder (not subfolders) to all the slave directories. No hiccups so far.The solution to this is to run wow.exe as administrator for the copy you want to be "master". IE if you made a C:\wow1 folder, you'd go into the C:\Wow1 folder, then right click wow.exe and click "Run as Administrator" - this will now tell the windows registry where your WoW copy is. Now you can run the launcher or whatnot and it will find the update location automatically.

[Dotalot]

i have not had any prob's at all (vista 64bit) all patched up and killing time till EU servers come online in 2 hours :whistling:

[Taliesin]

Since moving to Vista 64, the Blizzard updater has problems finding my WoW folder, since it needs to exist in a public space. The quick answer was to just manually download the patch then update that way. Haven't had any problems since then, even with symlinked folders.

I just symlink Cache, Data, Interface, and Screenshots (not necessary for this one, but personal preference). After patching the main folder, I just copy and paste the files directly under the WoW folder (not subfolders) to all the slave directories. No hiccups so far.The solution to this is to run wow.exe as administrator for the copy you want to be "master". IE if you made a C:\wow1 folder, you'd go into the C:\Wow1 folder, then right click wow.exe and click "Run as Administrator" - this will now tell the windows registry where your WoW copy is. Now you can run the launcher or whatnot and it will find the update location automatically.

It's been a while now, so I can't recall if I had tried that already. Next time I need to patch, I'll try to remember to do this again. Honestly, I still prefer patching manually because the Blizz downloader always seems to take me forever even though all the ports are open. 750 MB in just 20 mins from filefront? I don't think I've ever even remotely gotten close to those download speeds from Blizz even in between patch releases.

I also save all the patches in a separate folder for any time I find I need to re-install or want to update my laptop (shared directory) without downloading more than once.

[Dorffo]

always patch just your main copy of wow through the loader. then copy the new loader.exe and wow.exe to your symlinked wow's and everything will go smoothly.double quoted for emphasis ... have hosed my installs mutliple patches in a row when I forget to do this.

[zanthor]

I would suggest never using a 3rd party application to launch WoW (save for maybe a batch file you wrote yourself).Um... I'd go out on a limb and say almost all keyclone users do this... no problems in general - yea, don't try to patch that way.

I know all Innerspace users do this - still don't patch this way.

I think many HKN users do this... again, don't patch this way.

[Leon]

Just went to do the copy & paste thing with the Exe's and that went fine till i tried to open the second account now i get a error

"Unable to Open DBfilesClient\BnnedAddOns.dbc"
the when i go to try a repair it gets about half way and i get asked to please reinstall as there is not enough space to fix all the problems