Patch common issues

(Locked)

Support Forum Agent
This post was created as a quick resource for the most common reported patch issues and solutions. Please keep in mind that this post will be updated as more information becomes available.

Index

Post 2 - Downloading the Patch - http://tinyurl.com/4x8wmgk
Post 3 - Patching Errors and Issues - http://tinyurl.com/3twtlf5
Post 4 - Known Issues and Bugs - http://tinyurl.com/3poaajb
Post 5 - Resources, Patch Mirrors, miscellaneous items - http://tinyurl.com/3b3wkna
Post 6 - Norton & SONAR Patching Issue - http://tinyurl.com/3ro7f8z
Edited by Davidedl on 5/20/2011 7:12 PM PDT
Support Forum Agent
Downloading the patch


1. Launcher cannot obtain patching information.

Please check this thread - http://us.battle.net/wow/en/forum/topic/1020804433


2. Launcher states that it cannot write a registry key of some type.

This error will occur if you are running the Launcher in some form of compatibility mode. Please right-click the Launcher (or shortcut), click Properties, click the Compatibility tab and then uncheck the Compatibility mode box.

It may also occur after either a System Restore is ran or if you installed an older game (Burning Crusade or Wrath) after upgrading to 4.0.0. This process cannot be reverted so you need to uninstall and reinstall the game. Check this thread for more details - http://us.battle.net/wow/en/forum/topic/933154266


3. Launcher and game may have an issue initializing the mfil file.

The launcher will run into this problem if the file is either corrupt, or if another Launcher is blocking it from reading the file. Try going to the task manager (Ctrl+Alt+Del), click on the Processes tab and close any extra Launchers you may see.

There are some reports where antivirus programs, like McAfee, may block the launcher and game from using this file. Try checking your antivirus program.


4. Launcher may not patch

We're seeing reports of this issue happening when a security program, like Comodo, is blocking the Launcher from starting up an alternate version of itself (Launcher.patch.exe) to start the patch download process. Instead, it would pretend there isn't a patch, allow you to click Play and then the game will crash when logging in. Please check your security programs.


5. Launcher cannot connect to the news server, Game gives Failed to Apply Patch error.

This error may happen due to a variety of reasons. The most common ones are listed below:


  • The system's proxy configuration is incorrect. To fix this, go to Internet Explorer -> Tools -> Internet Options -> Connections tab -> LAN Settings. Once you're there, toggle the Automatically Detect Settings checkbox and apply the setting. Try the Launcher or game again.
  • Internet Explorer is set to not connect. Go to Internet Explorer -> File, then uncheck Work Offline. Try the Launcher or game again.
  • An internet security program is blocking the game files, or is set on a disabled/expired state. Please re-enable it and check the Programs section. If it is expired, you may want to uninstall it and use an alternative program. http://us.battle.net/support/en/article/computer-security
  • There are some reports where security program features like AVG's Linkscanner may prevent downloads from happening. Try temporarily disabling these features as a temporary workaround
Edited by Dankorii on 12/29/2011 4:47 PM PST
Support Forum Agent
Patching


1. Failed to apply patch message appears when clicking the Restart button.

Check the previous post. :)


**************************************************************************************************


2. The patcher is waiting for files to close.

This issue happens if one or more of your game files are open. Windows locks it so you can't overwrite it. You need to close them first before the patcher can continue. Try hitting Control+Alt+Delete on your computer. Make sure none of these are running in the Processes tab:

WoW.exe
Launcher.exe
BackgroundDownloader.exe
Repair.exe
WowError.exe


If any of those are running, try ending the task. The patch should continue afterward.


**************************************************************************************************


3. You may receive a message saying
"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.""


This error happens when a System Restore or a backup program restored some old files on the game and it gets confused. You can try reverting the game to fix this problem. To revert the game, go to your World of Warcraft\Data\ folder and delete the patch.MPQ file. If you have patch-2.MPQ and patch-3.MPQ, delete those as well. Go back to the World of Warcraft folder and run the repair utility. Once it's done, you'll have to repatch back to the current version and hopefully that will clear up any version mismatches. If that does not work, you will have to remove every World of Warcraft folder and files and then reinstall the game. For best results, install it in a different location.


**************************************************************************************************


4. You may receive a message saying something about
PC-HDFiles\____________
The patch "pc-game-hdfiles\WowError.exe" could not be applied. (CRC mismatch: expected 0xec8a47a2, actual 0x9e5111c7.) 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. (BNUpdate::PTCApply)
To check this installation for problems, click the "Repair" button. The Repair tool can automatically fix many update errors.
The file "\enUS-hdfiles\Data\enUS\realmlist.wtf" 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)
The patch "pc-game-hdfiles\msvcr80.dll" could not be applied. (Invalid source file size: expected 626688, actual 632656.) 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. (BNUpdate::PTCApply)


This error happens when a System Restore or a backup program restored some old files on the game and it gets confused. You can try reverting the game to fix this problem. To revert the game, go to your World of Warcraft\Data\ folder and delete the patch.MPQ file. If you have patch-2.MPQ and patch-3.MPQ, delete those as well. Go back to the World of Warcraft folder and run the repair utility. Once it's done, you'll have to repatch back to the current version and hopefully that will clear up any version mismatches. If that does not work, you will have to remove every World of Warcraft folder and files and then reinstall the game. For best results, install it in a different location.


**************************************************************************************************


5. You may receive an error saying that you do not have enough hard drive space.

On Windows Vista and 7, your World of Warcraft folder may not have the proper permission for the patch to work on. To get around this, right-click either the Launcher or the patch file itself and then select Run as administrator.


**************************************************************************************************


6. You may receive a naming error while patching, such as this one:

The file "C:\Program Files\World of Warcraft\Wow.exe.temp" could not be renamed to "C:\Program Files\World of Warcraft\Wow.exe". 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. (ConflictManager::ResolveConflicts/2)
The file "C:\Program Files\World of Warcraft\Wow.exe.temp" could not be deleted. (ConflictManager::UncreateObjects)
To check this installation for problems, click the "Repair" button. The Repair tool can automatically fix many update errors.


It seems that an antivirus software blocking the patch from working with the files. Try updating its definition files or try to temporarily turn it off for patching. You could also try patching in Safe Mode with Networking - http://us.blizzard.com/support/article.xml?articleId=21148

If it is not caused by antivirus software, then it is permissions-related. Make sure you are on the administrative account for the computer, and if you are on Vista or 7 that you are right-clicking the shortcut and choosing "run as admin"


**************************************************************************************************


7. Another copy of the Blizzard Downloader is already downloading that file to that location.

Try restarting the computer.


**************************************************************************************************


8. You receive the following error while patching:
Wow.exe cannot be found


This issue will happen if your system registry does not have the location to your World of Warcraft folder. Just run the Launcher to have it update the registry. If you have very strict permission settings, you may need to right-click it and run it as one of your administrator accounts.


**************************************************************************************************


9. You receive the following error while patching:
Blizzard Updater failed with an internal error.


Try patching in Safemode with Networking: http://us.blizzard.com/support/article.xml?articleId=21148


**************************************************************************************************


10. You are prompted for the Cataclysm disc while patching

This could be caused by Security Software or Permissions preventing files from being written, or it could be caused by file corruption.


**************************************************************************************************


11. You receive the following error while patching:
Could not initialize storage. You may not have permission to write to the destination path.


This is caused by permissions issues. Make sure that you are on the admin account and are running the game as administrator.


**************************************************************************************************


11. You receive the following error while patching:
Updating Failed


This is caused by lack of permissions or by an antivirus false-positive. Try temporarily disabling your antivirus or checking that it is not quarantining files.


**************************************************************************************************


11. You receive the following error while patching:
Updater Connection Timeout


This is caused by security software blocking the patch, generally due to a false-positive. Try temporarily disabling your security software.


**************************************************************************************************


12. You receive the following error while patching:
The patch "base\World\wmo\Northrend\Dalaran\ND_Dalaran_063.wmo" could not be applied. (MD5 mismatch: expected 0x4CC906DA1072975B26D9887AC4CD9AB1, actual 0xF6C000A7BA7631FDB1E6B0837E78969A.)(PTCApply_BSDiff failed.) If this problem persists, please contact Blizzard Technical Support. (BNUpdate::PTCApply)


This is caused by file corruption. Try repairing.

If you have a Dell XPS 630i then the problem is that the system you have has a known instability problem and I would recommend that you take a look at Datth's post here and try the solution he offers: <a href="http://forums.worldofwarcraft.com/thread.html?topicId=21730644547&sid=1&pageNo=4#77" target="_new">http://forums.worldofwarcraft.com/thread.html?topicId=21730644547&sid=1&pageNo=4#77</a>


**************************************************************************************************


13. You receive the following error while patching:
The file "C:\Users\Public\Games\World of Warcraft\Data\enUS\backup-enUS.MPQ : Launcher.exe" could not be written. If this problem persists, please contact Blizzard Technical Support. (MPQTarget::Write/SFileWriteFile)


This is typically caused by file corruption. Try running the repair.


**************************************************************************************************


14. You receive the following error while patching:
The file "C:\Program Files\World of Warcraft\Data\enUS\Interface\Cinematics\Logo_1024.avi.temp" could not be created. If this problem persists, please contact Blizzard Technical Support. (InstallerFile::Create)


This is a permissions issue preventing files from being written. Make sure you are on the administrative account and that you are running as administrator if you are on Vista or 7.


**************************************************************************************************

15. You ran out of hard drive space or it's getting very low

The 3.3.0 to 4.0.0 migration takes a lot of hard drive space in order to process your old game files into the new ones. A duplicate is made so that if the patch fails, you will still have your old files to fall back on. Unfortunately, this requires you to have double the size of your World of Warcraft folder available as free space on your hard drive. If you cannot get enough free space, please uninstall the game and use the streaming installer to directly install the 4.0 client - https://us.battle.net/account/management/download/


**************************************************************************************************


16. An I/O error has occurred. (4)

We're getting reports of this happening on systems that are blocking the Blizzard Downloader. Please configure your security software to allow the specific downloader (either Launcher, Backgrounddownloader.exe or WoW-x.x.x.x-4.0.0.12911-Updater.exe) access to the internet. If that doesn't work, try this:


Selective Startup:
For Windows XP/ME users:

Click Start and select Run, then type "msconfig" and click OK.
In the General tab:

- Choose Selective Startup
- Disable (uncheck) Load startup items
- Click Services, then check the Hide all Microsoft services,
- Disable the non-Microsoft services
- Click OK and Reboot

For Windows Vista users:
Click Start, All Programs, Accessories and select Run, then type "msconfig" and click OK.
In the General tab:

- Choose Selective Startup
- Disable (uncheck) Load startup items
- Click Services, then check the Hide all Microsoft services,
- Disable the non-Microsoft services
- Click OK and Reboot

Please keep in mind that this will disable all security programs. Please re-enable these after you're done patching.
Edited by Dankorii on 12/29/2011 5:00 PM PST
Support Forum Agent
Known Issues/Bugs

Please check the 4.0 Known Issues thread for a listing of a majority of the known issues - http://us.battle.net/wow/en/forum/topic/933034369


Low framerates

We're seeing an increasing amount of reports where low framerates are coming from old addons and settings. Please remove them, even if they show up on your favorite download site as being "updated" and start fresh.

If you're using an ASUS brand video card and have installed the Gaming OSD software, this has been dropping framerates to very low numbers.

There are other reports where the NVIDIA nView software may contribute to low framerates. Try removing nView.


Crashes and display oddities

1. Some Intel Integrated video cards may crash to an IGFX crash, or may encounter a blue screen.

If this happens to you, try updating your drivers first. If that doesn't fix it, open the World of Warcraft\WTF\config.wtf file in Wordpad and add the following line:

SET fixedfunction "1"

Save the file and try the game again.


2. Users of the unsupported Unichrome IGP may have odd visuals or freezes.

Open the World of Warcraft\WTF\config.wtf file in Wordpad and add the following line:

SET fixedfunction "1"

Save the file and try the game again.


3. Error 1 reported by the Launcher

This is a generic error message that the World of Warcraft Launcher displays when it fails to start up.

Example:
This application has encountered a critical error:
ERROR #1 (0x13370001) Fatal Exception
Program: D:\Program Files\World of Warcraft\Launcher.exe
The instruction at "0x004439A4" referenced memory at "0x051EFC94".
The memory could not be read.

Please follow the steps below:

The Launcher is closely tied to Internet Explorer settings. Ensure all Windows Updates have been done, including Service Packs and Internet Explorer updates (specifically, Internet Explorer 8).

Windows XP: Be sure you have all the available updates from: http://windowsupdate.microsoft.com/

Windows Vista/7: Click on the Windows/Start button and enter "Windows Update" into the search field. When that window opens, click Install Updates.

Check LAN Settings by opening Internet Explorer (other browsers will not work for this step). Go to Tools, then Internet Options. On the Connections tab, click "LAN settings" and make sure all options in that window are unchecked.

The Launcher has multiple Flash images that load when it starts up. Older versions of Flash Player can interfere with the Launcher loading properly. Ensure all Adobe Flash updates have been done.

If you are unsure which version of Flash Player you have installed, download the latest version at http://www.adobe.com/

On rare occasions malware or viruses can interfere with the Launcher, because they frequently target web browsers like Internet Explorer. The Launcher relies on Internet Explorers settings, and if those settings become corrupted the Launcher can fail to start up.

Make sure you get the latest updates from your malware and anti-virus manufacturers, then scan your system. For additional information and links to some anti-virus software please visit our Computer Security page:

http://us.blizzard.com/support/article.xml?locale=en_US&articleId=30794

Try uninstalling the game then deleting the entire install folder from the hard drive. Once you have done this, reinstall the game and try it again. Re-establishing the data files this way can resolve general this error in many cases.



4. Error 132 by the game, referenced at 0x12C

This error seems to happen if you try to log onto the game using the 4.0.0 client. We need you to update to 4.0.1 before logging in. Some security software, such as Comodo, were reported by others to have blocked the update functionality from happening.


5 Your launcher may not be able to connect. If starting the game, you'll be greeted with this error:
This application has encountered a critical error:

ERROR #134 (0x85100086) Fatal Condition
Program: C:\Users\Public\Games\World of Warcraft\WoW.exe

Failed to open archive Data/wow-update-13164.MPQ. Missing or corrupted data.


This will happen when a security program blocks both the launcher and the game from connecting to the streaming file servers. Please check your security programs.
Edited by Dankorii on 12/29/2011 5:07 PM PST
Support Forum Agent
Resources

Game patch mirror links

We have mirror patches up to the 4.0.1a patch. We do not have 4.0.3 at this time. Please check this link for patches - http://us.blizzard.com/support/article.xml?locale=en_US&articleId=21079

If you need the full 4.0 install client, please get it from https://us.battle.net/account/management/download/


Tools patch

There are no tools patch mirrors at this time.
Edited by Dankorii on 12/29/2011 5:07 PM PST
Support Forum Agent
Norton & SONAR Patching Issues

Originally Posted by WoW Forum MVP Ressie


Link to the original thread: http://us.battle.net/wow/en/forum/topic/2416206742

UPDATE:
Norton's telling users to run LiveUpdate to receive their fix for this issue.


Hi everyone.

We see many users have been experiencing issues downloading the tools patch this morning (which would then allow them to download 4.1), however SONAR is flagging it and blocking the download.

Essentially, you'll want to temporarily disable SONAR to patch, then re-enable it.

SONAR doesn't work off of known malware, etc, but instead works off of the number of users who have downloaded the file.

The patch just came out, SONAR recognizes that few people (with Norton) have downloaded the file, so it blocks it.

I'm running the corporate edition of what you're running, and nothing flagged for me, installed nicely with no blips.

It is safe. I guarantee it. :)
Edited by Davidedl on 5/20/2011 7:09 PM PDT
This topic is locked.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]