Why Do I Have To Do This Again?

Is it my fault that when I installed the game and launched, it was being a “know-it-all” and chose to use “The Americas” region/server when I created my character? If you want your game to be customer friendly, it should ask the player which servers they want to play because chances are, they’d be too excited to actually think about it.

Do I have to go through the forums every time a patch comes out and the game doesn’t patch on its own? The patches before had no problems. So what’s the problem Blizzard?! I had to search a bit on the forums to find the solution!! Players get frustrated if they have to do something like this, you know. Not all players would know that the game will decided which server they’d be playing for the first time.


The following is a re-post from the Diablo III forum in Battle.Net. Thank you Barthus for posting this! The steps are easy enough to follow and I didn’t encounter any problem. But people shouldn’t have to go through this. Sheesh!


This may apply to you if this is how your game/launcher is behaving:

On login you get a message saying “A New patch for Diablo III is available” and it also says that your game will be closed and the patch will be applied. The game closes, the Launcher comes up saying “Game is up to date” and no patch is applied.

Basically, the “new patch” message means your Diablo III.exe or battle.net.dll does not match the version accepted by the server. If different regions are at different versions, you need to set your patch_url to get updates meant for the region you play in.

If you play in Europe or Asia, change the patch_url accordingly and follow the steps under “Reverting the client to the correct version”.

———- Change the patch_url by editing the .agent.db file.

This is how you can set your client to get updates whenever they’re released in the Americas region: (Shouldn’t be needed if you use a client meant for the region you play in.)

Before you start, make a backup copy of the original .agent.db file. (to restore in case something goes wrong)

1. Go in your Diablo III folder.
2. Open the .agent.db file on WordPad.(This file may be hidden and please, do not delete this file)
3. find the “patch_url” line and change its value to:
http://enUS.patch.battle.net:1119/patch4. Save and close the file.

5. Now go in the Battle.net folder:
Win 7/8/Vista
C:\ProgramData\Battle.netWindows XP
C:\Document and settings\All Users\Application Data\Battle.net(ProgramData and Application Data are hidden folders.)

6. Once inside the Battle.net folder, select and delete the Agent folder. (don’t skip this step)

7. Start the Launcher.

Now, if the issue was the launcher not patching the Diablo III client because it was using a different patch_url, your client should be patched and you should be good to go. However, if you play in a region that’s behind your client’s version, you need to revert your client to the previous version.

———- Reverting the Client to the correct version. (Set the patch_url before doing this)

“An unexpected error occurred while trying to install” (Unable to reach final version)

The above message is the error you get when your diablo3 client version is ahead of the patch_url set, if that happens, this is how you should proceed.

1. Delete the Updates folder. (Diablo III\Updates)
2. Delete the Diablo III.mfil file
3. Delete all files named d3-update-10235 in the Data_D3 folder. Delete only the ones added in the most recent build, 10235. Go in “Data_D3\PC\MPQs” and look inside base, LOCALE, Win, OSX and Cache folders.
4. Replace your Diablo III.exe with an older version if the file (Must be older than 9991. And backup the original file, just in case)
5. Run Diablo III Launcher to repatch the game.

LOCALE = Your game’s locale (enUS, enGB, frFR, deDE, etc)

If you need a Diablo III.exe for step 4, you could download this one:
http://www.gamefront.com/files/21864092/Diablo_III_exe_1_0_0_8370_zipThis file was extracted — by me — from base-Win.mpq using MPQEditor, and if you don’t want to download this file, you could do the same. (Just google MPQEditor)

———- patch_url list. 🙂 (You might need one of these if you don’t play in the Americas region)

Korea (Asia)
Taiwan (Asia)

If the regions are at different versions but changing the patch_url doesn’t help:

1. Your client version may be ahead of the region you play in. If that’s the case, just follow the steps under “Reverting the Client to the correct version.” (It’s on the original post)
2. It’s also important to check — in-game — if your client is set to log on to the correct region.
3. Make sure you followed the instructions correctly.

———- Some other stuff…

An error that a lot of people are going to get:
ERROR: The file C:\Program files (x86)\DiabloIII\Updates\d3-0-10057-Win-final.MPQ appears to be corrupt. You may need to download this file again.
In this case, just delete the Updates folder to re-download the MPQ patch. (Diablo III\Updates)


If you see a big “Install” button, close and reopen the launcher. If that doesn’t work try deleting the Updates folder. (This is being caused by a bug)


How to Repair Diablo III:

If you messed up and believe your Diablo III Install is broken, there’s no need to re-download the entire game. You should be able to repair your Diablo III install by following the instructions on this post: http://us.battle.net/d3/en/forum/topic/5271498956#4


One comment on “Why Do I Have To Do This Again?

  1. SEA countries that log on to US region are, by intention, late to get the patch. This is not really a shortcoming on Blizzard’s part. What the forum post suggests is for those who don’t want to wait. Thus you have to pay that price.

    However, the intended delay is not without fault. If US servers are already updated to the latest patch and SEA players logging on still have the old game version, then the game goes into a loop. It sees that the server is at the new version, so it prompts to download the patch. Yet the patch can’t be downloaded yet beacuse it is not yet available for SEA players. Then you get the Windows error that the Diablo 3 executable stopped working properly.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s