Big tools at stuck 3 updating diablo beta statue Jena Presley

Share this post:

With Diablo III PC: Reaper of Souls out on the PC, many gamers still continue to experience persistent crashes, errors, connection and logon issues with Diablo III. Here’s a convenient collection of error codes and messages you may experience during installation, gameplay, and client log in. If you are experiencing any of these errors, please follow the steps provided.

How to Fix Diablo III: Reaper of Souls PC Crashes, Errors, Connection and Logon Issues, Patching

Installation, Setup and Patching issues

  1. “If your installation disc has been ejected, please reinsert and try again. If not, or if you keep seeing this error, log in to Battle.net and install Diablo III Reaper of Souls PC digitally” – If you downloaded the installer digitally, this error indicates that it did not convert the files correctly. This can often be caused by closing the downloader early. Though the downloader may show 100%, please allow some time for it to fully complete. To resolve this issue, log into Battle.net and re-run the downloader.
  2. Error 108 or “An unexpected decryption error occurred” – This can be caused by corrupted, damaged or incomplete installation files. It can often times be caused by closing the downloader early. Though the downloader may show 100%, please allow some time for it to fully complete.
  3. You may be able to fix this by running the downloader and pointing it to the same saved location so that it may scan and download any missing files.
  4. Unable to Initalize Streaming – This error can generally be caused by security software on your computer. During this time, however, it’s possible that the error is caused by the number of people hitting the servers. Please double check your firewall settings and try again.
  5. Updating Setup Files – If you’re stuck on “Updating Setup Files” check to see if the Windows Service for Secondary Logon is enabled. The game requires it and will not run if it’s disabled. To check, open Control Panel > Administrative Tools > Services (or Control Panel > System and Security > Administrative Tools > Services) and scroll down to the Secondary Logon service. Right click it and select properties. Make sure the Startup Type is NOT set to Disabled. Any other setting should be ok, although we’ve seen a couple reports of a user needing to use “automatic.” Be advised that some security programs, such as AVG, may be switching this service off by default.
  6. Error BLZPTS00007 – This indicates that the Agent support program was unable to run. Try waiting a few minutes, then reattempt. If that fails, restart the computer and try the game again. Should the issue persist, uninstall your current copy of the game and download again from the Battle.net Game Downloads page.
  7. Error 3012 and 3014 – Please be sure to uninstall the Beta, and ensure that the Diablo III Reaper of Souls PC Beta folder is deleted.

Connection and Logon issues

  1. Error 33 and 34200 – The service is undergoing maintenance, please try again later. (Please note that Diablo III Reaper of Souls PC will not be available for play until May 15 at 12:01 a.m. PDT.
  2. Error 37 – The server is full. This is likely due to high login traffic. The only solution is to keep trying to log in.
  3. Error 24000 – Once logged in you may run into this error when attempting to start a game. We’re aware and are working to resolve it as quickly as possible.
  4. Error 3004, 3006, 3007, or 300008 – There are a number of possible causes for these errors. We’ve found that one of these suggestions can help.
  5. Error 315300 – Commonly this is cause by incorrect account information when trying to log in. Make sure you’re typing your correct account information and remove any additional spaces added before or after your email address. If the issue persists then check here for further solutions.
  6. Gray login button – You need to use your Battle.net email address as your account name. Your BattleTag is a nickname, not your account name.
  7. No License Attached – Please create a BattleTag for your account. You can do so here.

Gameplay and Crashing issues

  1. Error 12 – Please make sure you choose the correct region when starting the game.
  2. Mouse unresponsive or Invisible – If you use Windows 7 and encounter this try these steps:
    • Right-click on your desktop and select Screen Resolution.
    • Click Make text and other items larger or smaller.
    • Change the size to either Smaller or Medium (Our games are not compatible with the Larger setting).
    • Select Apply.
    • Restart your computer.
  3. Missing Characters – Please check the Server Region Selection under the Login Screen > Options > Account settings page to make sure you are accessing the same region as before. Many times missing characters will be found when looking at the proper region.
  4. Game crashes at launch – We’ve seen many reports of these crashes being caused by overlay programs. Check and see if you have any of the following third party programs running and then either update or uninstall them and retest.
    • Mumble
    • XFire
    • EVGA Precision
    • Airfoil by Rogue Amoeba
    • MSI Afterburner
    • Dxtory
    • RadeonPro
    • Taksi

Diablo III Reaper of Souls PC Patch Looping

  1. Trying to play in a non-US region from a US game client cause what appears to be a patch loop. There is additionally a true patch looping issue caused by running Diablo III Reaper of Souls PC in compatibility mode which we’ve asked users not to do. Creating a new user account will workaround this issue and allow the game to patch. (Running Diablo III Reaper of Souls PC in compatibility mode causes a registry key to change in a fashion that will block attempts to patch. Launching the game in a new user account will reset the key.)
  2. Another cause of true patch looping is if the Diablo III Reaper of Souls PC client is not in its original language. In this case, on the main login screen, before logging in, go to Options > Account > Language Selection and try switching Diablo III Reaper of Souls PC’s language back to its original default.

Share this post: