We are currently in the process of compiling patch 4.3.2 issues and methods to resolve them. Please check the below list for a potential solution to the issue you are troubleshooting and some other tips to avoid patching issues.
-
Only start World of Warcraft with the "Launcher.exe" when you are fully patched and the game is playable.
Most of the errors and anomalies that some users are experiencing are caused by not starting World of Warcraft with the "Launcher.exe" that is found inside the World of Warcraft folder. Using the Launcher is required for proper patching. Renaming/deleting the launcher or using alternative means of starting World of Warcraft may result in corrupted data and large additional downloads of data. If you suspect that your Launcher.exe is modified or deleted, please run the repair tool that is found in your World of Warcraft folder to repair it. -
"Internal Error" during tools patch.
This issue appears to primarily be caused by security programs mistakenly blocking the patching process. First try running the repair tool and running the game in administrator mode to overcome the block. If necessary, we recommend temporarily uninstalling your security software or contacting your security software's tech support for assistance in rectifying the block. Please note that simply "disabling" most security programs will not prevent them from interfering with the patching process. -
Launcher seems stuck at "Connecting to patch services".
Although it may seem stuck, the Launcher is actually downloading a very large file at this point in the process. Please be patient and avoid closing the Launcher as it downloads the data; failure to do so may result in corrupted data and a large additional download. -
Do not manually run the Background Downloader
Running the Background Downloader before the Optimisation process is complete will require you to redownload all of the World of Warcraft data, which is a very large download. Manual use of the Background Downloader should be limited to very specific troubleshooting circumstances. -
Do not start World of Warcraft via WoW.exe.
Bypassing the Launcher by use of WoW.exe before the Optimisation process is complete will result in corrupted data and a lengthy download. WoW.exe is not meant for regular use, and should only be utilized in specific troubleshooting circumstances. -
Addon Manager programs (Curse Client, etc.) can block the Optimisation process
Having an addon manager program installed can cause the optimisation process to stall or error out as programs of this type often block access to some of your WoW files. Try temporarily uninstalling any addon managers until you are fully patched and playable. Please note that these symptoms are the same as those that can be caused by improperly configured security software. -
Launcher closes with "Connection Timed Out" message
We're seeing success resolving this issue with a DNS flush. Please first try Step 1 (IP Release/Renew, Flush DNS) on our Connection Troubleshooting page, and if the message persists, please move on to Step 2 (Power Cycle the Modem and Router). Please note that some security programs may prevent this resolution from working. -
Error 1 Message While Patching
We've seen two different situations with Error 1s with patch 4.3.2. Some of them are specifically caused by a security program called "Net Nanny", and can be resolved with the temporary removal of this third-party software. Unfortunately, for cases not caused by "Net Nanny" the only solution we have at this time is a full uninstall and reinstall (PC and Mac instructions)of the game client. -
"Your game installation is damaged. Please run Repair"
Although this error can be caused by addon manager programs tricking WoW into thinking its files are damaged (see above), it can also be caused by genuine file corruption. If you are not running any addon manager programs, please try the following procedure:
1. Go into the World of Warcraft folder
2. Delete the contents of the "Temp" and "Updates" folders
3. Delete the Launcher.exe
4. Run the Repair.exe and allow the process to complete
5. Run the Background Downloader, but cancel it after about 30 seconds
6. Run the new Launcher.exe (If on Vista or 7, please right-click the Launcher and select "Run as administrator")
7. Allow everything to patch normally -
If All Else Fails
While it's always a step of last resort, if the troubleshooting on this page and on our Technical Support Forums does not resolve your issue, an uninstall and reinstall of your game (PC and Mac instructions) may be required to resolve the issue. We at Blizzard understand first hand (we're gamers afterall) that having to uninstall and reinstall an online game is never an ideal solution, but if all else fails then it is typically the best way to get back into the action. Rest assured that we will continue to investigate alternative troubleshooting techniques to minimize the need for this "final solution". -
Up-to-date information and discussion of Patch 4.3.2 issues can be found on our Technical Support Forums. We greatly encourage posting any unusual patching issues you may encounter on the forums for tracking and investigation.
-
We have a main article for the World of Warcraft Optimisation process.
-
You may also find additional patch troubleshooting useful for your specific situation.
If your issue persists, please consult the Technical Support Forums or contact Billing and Account Services for further troubleshooting. Thank you!
Alonsus
Azuremyst
Blade's Edge
Hellfire
Kilrogg
Any suggestions?
Mazrigos
Nordrassil
Kazzak
Kazzak
Argent Dawn
If anybody else is getting this problem, here's what I did to fix it...
1) run a repair, not sure whether it makes a difference, but it's what I did.
2) Delete the folders that Kapaya stated further down.
3) Delete the folder named 'Update', open up WoW and watch your game patch
Hope this helps guys, and good luck :)
Hellscream
Hellscream
Hellfire
Chamber of Aspects
Kilrogg
kan ikke spille wow siden de der patch er komme
Talnivarr
Battle.net-64.dll
MovieProxy.exe
WoW-64.exe
Trollbane
Sylvanas
http://eu.battle.net/support/en/article/64bit-client-prevents-patching-to-433
If you have a 32-bit version, then I do not know what to do. Have the same problem :(
Shattered Hand
Darksorrow
Kilrogg
Outland
Sylvanas
Shattrath
Grim Batol
Sylvanas
Twilight's Hammer
Sylvanas
Fond this.. but I do not have 64-bit version:S
Darksorrow
Wildhammer
The Sha'tar
The Sha'tar
Stormscale
Wow-64.exe (PC)
MovieProxy.exe (PC)
Battle.net-64.dll (PC)
what should i do ?
Drak'thul
Outland
Boulderfist
Shattered Hand
Wildhammer
Stormscale
Saurfang