PDA

View Full Version : How to patch



schlange
01-09-2008, 05:19 PM
I just logged my accounts in and they downloaed the patch but failed at the install of the patch because it could not write to the uninstall file.

[code:1] The file "C:\Program Files (x86)\Common Files\Blizzard Entertainment\World of Warcraft\Uninstall.xml" could not be renamed to "C:\Program Files (x86)\Common Files\Blizzard Entertainment\World of Warcraft\Uninstall.xml.Trash". (ConflictManager::ResolveConflicts/3)

To check this installation for problems, click the "Repair" button. The Repair tool can automatically fix many update errors.
[/code:1]

It successfully patched the main install, however it failed on every single one of the clone copies. Noob question here, but how do I patch the clone copies?

marvein
01-09-2008, 05:23 PM
copy the patch.exe file into each respective directory and then tell it to update ONE at a time, had the issue last night. I never got an error just they would not do anything until the other was finished.

keyclone
01-09-2008, 05:29 PM
if you are using maximizer each time you run, you must remember to run 'launcher.exe' after every update so you can get the downloaded patch.

and yes, if you are using multi directories, you'll have to do it for each...

schlange
01-09-2008, 05:37 PM
Ok I just ran the laucher.exe from one clone wow directory
I just logged in via wow.exe from the same clone directory
It just downloaded the patch and applied it

I just got the same error

The patch.exe file cannot be found anywhere in the directory either for some reason now.

schlange
01-09-2008, 05:39 PM
Now I get this error after running launcher.exe

[code:1] This update does not need to be applied. It requires version 2.3.0.7561 of "WoW.exe", but you already have version 2.3.2.7741.
[/code:1]

Blokus
01-09-2008, 05:58 PM
Now I get this error after running launcher.exe

[code:1] This update does not need to be applied. It requires version 2.3.0.7561 of "WoW.exe", but you already have version 2.3.2.7741.
[/code:1]

I got that message last night (and have gotten it before). What I've found that works is to rename my main WOW directory to (whatever) and then rename the clone directory to the original main directory name and then run launcher.exe from that directory to apply the update. Then I rename the directories back the way they were.

schlange
01-09-2008, 06:03 PM
Now I get this error after running launcher.exe

[code:1] This update does not need to be applied. It requires version 2.3.0.7561 of "WoW.exe", but you already have version 2.3.2.7741.
[/code:1]

I got that message last night (and have gotten it before). What I've found that works is to rename my main WOW directory to (whatever) and then rename the clone directory to the original main directory name and then run launcher.exe from that directory to apply the update. Then I rename the directories back the way they were.

I tried the Repair utility and that did not work.

So I tried your advice. The laucher worked fine and then it says it needs to restart to apply the patch and then I get a WOW critical error and a crash. It asks me to send it to Blizzard.....not sure what happened but it is all screwed up now.

schlange
01-09-2008, 06:12 PM
I am just going to copy 5 new instances from my main directory and recreate the clone directories.

Hopefully the next patch will go easier for me. :oops:

marvein
01-09-2008, 06:22 PM
I am just going to copy 5 new instances from my main directory and recreate the clone directories.

Hopefully the next patch will go easier for me. :oops:

make sure ot backup your macros and keybidnings before you overwrite them ;)

Otlecs
01-10-2008, 07:25 AM
I had the same problem when I tried to take a shortcut with the last "big" patch. I just left my launchers broken and launch wow.exe directly instead.

I also resolved not to try short-cuts any more, and now just sit through the patch process for every individual installation of WoW across all machines :)

Phate
01-10-2008, 07:58 AM
Mine acted kind of bizarrely. The launcher didn't update the copy of WoW in it's directory, but after running all 3, all 3 updated properly. Very strange, especially since my installs are on different physical drives.

Wilbur
01-10-2008, 08:46 AM
I think this is because you haven't added extra registry keys for the extra WoWs.

Try doing that and see if it works.

schlange
01-10-2008, 10:28 AM
I think this is because you haven't added extra registry keys for the extra WoWs.

Try doing that and see if it works.

I would love to, if you can provide instructions :P

Wilbur
01-10-2008, 10:42 AM
erm...

Not sat at a PC with WoW installed right now :-(

marvein
01-10-2008, 12:15 PM
I think this is because you haven't added extra registry keys for the extra WoWs.

Try doing that and see if it works.

I dont have any either and the only issue I ran into was I could not do them all at once, no errors or anything though.

schlange
01-23-2008, 12:29 PM
Update errors AGAIN.


The file "C:\Program Files (x86)\Common Files\Blizzard Entertainment\World of Warcraft\Uninstall.xml" could not be renamed to "C:\Program Files (x86)\Common Files\Blizzard Entertainment\World of Warcraft\Uninstall.xml.Trash". (ConflictManager::ResolveConflicts/3) To check this installation for problems, click the "Repair" button. The Repair tool can automatically fix many update errors.

I ran the launcher from each WOW and I get the error again that it cannot patch the file.

This is after I had to reinstall. Do you all reinstall after every patch? I cannot figure out why I get errors.

Maybe someone can provide the directions on manually updating the registery keys so I can do that.

Lost Ninja
01-23-2008, 01:16 PM
After 2.3 I had most of the above issues, coupled with a computer that wouldn't do an exact copy eg when I copied a working WoW install it wouldn't run (crashed with errors). And I couldn't get the main install to patch...

I deleted (not un-installed) everything (with careful backups), reinstalled and applied all the patches (cunningly saved), since then I haven't had any issues. I manually copy the patch file (not the downloader) into each installation directory and run it, that gives no errors. If anything I think the issues were caused by too many conflicting registry entries rather than not enough. The error about not being able to write the un-install log is AFAIK due to the patcher looking for WoW in one place but WoW being somewhere else.

-silencer-
01-23-2008, 01:29 PM
I haven't ever had a problem patching multiple copies of WoW.. so here's my full process starting from a clean (no WoW installed) machine:
- Install WoW & TBC. (C:\Program Files/World of Warcraft)
- Run WoW to download all patches up to current version.
- Copy WoW Maximizer.exe & .ini to main WoW folder.
- Make a copy of that WoW folder for each login on my other drive (I like my macros/add-ons separate). (D:\WoW2, D:\WoW3, etc)
- Edit Maximizer.ini in each of the WoW folders for the correct window resolution and screen offset location.
- Make a Multilog.bat script to load up my 5 instances of WoW, using these lines:
"start C:\Program Files\World of Warcraft\Maximizer.exe"
"ping 127.0.0.1 -n 6"
"start D:\WoW2\Maximizer.exe"
"ping 127.0.0.1 -n 6"
etc..
This will pause about 6 seconds after loading each instance of WoW - enough time to bring up the login screen and position it correctly on my monitors.
- Use Multilog.bat until next Tuesday - patches are coming.
- Load just my main copy of WoW to login and retrieve patch (if any available). Download & patch that install of WoW.
- Using Win Explorer, manually copy new patch files from the main folder to all other WoW install folders. Check the version or date of the files to see which are new.
- Individually load up each of the other WoW installs by loading WoW.exe in each install. Go through the patching process for each one. It should be much faster since you've already got the patch downloaded and copied to the local directory. Exit each WoW install when it is finished.
- Use Multilog.bat to play WoW again.