Diablo III

From PCGamingWiki, the wiki about fixing PC games
This page may require cleanup to meet basic quality standards. You can help by modifying the article. The discussion page may contain useful suggestions.
Diablo III
Diablo III cover
Blizzard Entertainment
Release dates
Windows May 15, 2012
OS X May 15, 2012
Diablo 1996
Diablo II 2000
Diablo III 2012

Key points

The Auction House was closed on March 18, 2014.[1]
Requires a constant internet connection for all game modes.

General information

Official game website
Official expansion website
Official community website
Official forums
General known issues list
Diablo Wiki - A wiki for everything Diablo related
/r/diablo Subreddit
D3Head - A comprehensive item, skill and quest database from the makers of Wowhead for World of Warcraft


Source DRM Notes Keys OS
Official website
All versions unlock a digital download on Battle.net.
All versions require a Battle.net account and a constant internet connection for all game modes.

Downloadable content (DLC) and expansions

Some regions have in-game micro-transactions (not listed below).[2]
Name Notes
Diablo III: Reaper of Souls Can be bought from the Battle.net store.

Version differences[edit]

Starter Edition[edit]

The Diablo III Starter Edition provides players the ability to try out a limited demo version of Diablo III.

The Starter Edition has a number of restrictions:

  • Act I up to the Skeleton King is available
  • Level 13 cap
  • Matchmaking available only with other Starter Edition players
  • Global Play is not available. Players attempting to connect to Diablo III Starter Edition in a region other than their Battle.net Account's home region will receive Error 12.

Matchmaking of Starter Edition is only possible with other players of the Starter Edition, and not the full accounts. This includes public matching and private invitations. Counterintuively, this means that Starter Edition players will not be able to play with players with full Diablo III accounts.[3]

Game data[edit]

Configuration file(s) location[edit]

System Location
Windows %USERPROFILE%\Documents\Diablo III\D3Prefs.txt
OS X ~/Library/Application Support/Blizzard/Diablo III/D3Prefs.txt
Save games are stored on the Battle.net servers.

Video settings[edit]

Graphics option Option WSGF Notes
Widescreen resolution
Change display mode to "Windowed (Fullscreen)" in-game.
Change display mode to "Windowed (Fullscreen)" in-game.
4K Ultra HD
Borderless fullscreen windowed
Change display mode to "Windowed (Fullscreen)" in-game.
Anisotropic filtering (AF)
Anti-aliasing (AA)
Vertical sync (Vsync)
60 FPS
120+ FPS
True frame rate is capped at 60 FPS.[4][5] Even if frame rate counters indicate the game is running at more than 60 FPS, all visuals (including camera movement) will only update at a maximum of 60 FPS.

Input settings[edit]

Audio settings[edit]

Audio options Native Notes
Separate volume controls
Master, SFX, voice, ambience, music
Surround sound
4.0-7.1, ProLogic
Available for cinematic and quest dialogues.
Closed captions
Mute on focus lost
Can be toggled in options menu.


Language UI Audio CC Notes
US, EU, and SEA
Brazilian Portuguese
AL and EU
Traditional Chinese
Simplified Chinese


Multiplayer types

Type Native Players Notes
Local play
Console versions only.
LAN play
Online play
4 Co-op

Connection types

Type Native Notes
Direct IP


Protocol Port(s) and/or port range(s)
TCP (outbound) 80, 1119, 6881-6999
UDP (outbound) 1119, 6120, 6881-6999

Issues unresolved[edit]

Window Unresponsive[edit]

Game client window becomes unresponsive when a dialog box is opened in the background.

Issues fixed[edit]

Video Card Not Supported[edit]

Unsupported video card error.
Unsupported video card error.
Demo version of Swiftshader, on Intel G41.
Demo version of Swiftshader, on Intel G41.

You may receive the error message:

We have detected that your video card is not supported by Diablo III.

Diablo III will block certain systems running the game if it does not detect a certain spec of video card. However, it is possible to force the game to run on any video card (even if it does not meet the minimum specification of the game).[6]

This fix has been acknowledged by Blizzard, but comes with its own warning from Omrakos:

...if you decide to do this and have terrible performance as expected, please do not contact us reporting it. We know the unsupported cards aren't going to perform well and there's nothing we'll be able to do to remedy it.[7]

Method 1 - Press Escape[edit]

Method 1 - Press Escape
  1. Pressing Esc instead of cancel will make one's computer attempt to load the client.
Pressing cancel will load up a list of unsupported video cards on Blizzard's website.

Method 2 - Edit D3Prefs.txt[edit]

Method 2 - Edit D3Prefs.txt
  1. Edit %USERPROFILE%\Documents\Diablo III\D3Prefs.txt
  2. Change HardwareClass "0" to HardwareClass "1"
  3. Change DisableTrilinearFiltering "0" to DisableTrilinearFiltering "1"
  4. Save your changes.

Method 3 - Swiftshader[edit]

Method - Swiftshader

Using the program Swiftshader can successfully load the game even on extremely low powered machines. For example, the game can be run on integrated graphics as low powered as the Intel G41, albeit at extremely low frame rate.[8]

High DPI Setting[edit]

Disable DPI scaling settings.
Disable DPI scaling settings.

By default, it appears as if Diablo III has a number of issues with high or custom DPI settings in Windows.

This can result in:

  • Mouse cursor not being moveable whilst in fullscreen mode.
  • Mouse being imprecise on the screen.
  • Taskbar showing over the game window.
High DPI Setting fix
This can be fixed by following these steps:[9]
  1. Right-click on the Diablo III shortcut (or Diablo III.exe) and go to the 'Compatibility' tab.
  2. Select, 'Disable display scaling on high DPI settings'.

Login Errors[edit]

These messages may appear when trying to log in.

Error 12[edit]

This means that no license is attached to the Battle.net account, a problem with many users in Asia. Check this thread for more information.

Error 37[edit]

This message means that the login servers are at full capacity. Official advice is to try logging in later when the servers are less busy.[10]

Error 37
However, it is possible to bypass Error 37 using this trick


  1. Enter password.
  2. press Enter.
  3. Press cancel before anything happens.
  4. Log back in straight away.
This might be considered an exploit of the way that the client is reporting Error 37 to indicate that servers are too busy. However, this does not seem to have any particular consequences, except that Blizzard's servers will be busy.

Error 75[edit]

Error 75 means that Blizzard servers are down. Check Diablo III Server Status page for updates.

Can't Move Mouse In Fullscreen[edit]

Disable DPI scaling settings.
Disable DPI scaling settings.

This is most likely caused by high or custom DPI settings in Windows.

Method 1 - Compatibility[edit]

Method 1 - Compatibility

This can be fixed by following these steps:[12]

  1. Right-click on the Diablo III shortcut (or Diablo III.exe) and go to the 'Compatibility' tab.
  2. Select, 'Disable display scaling on high DPI settings'.

Method 2 - Edit D3Prefs.txt To Windowed[edit]

Method - Edit D3Prefs.txt To Windowed
If one is stuck in fullscreen mode, one can change the D3Prefs.txt settings to force a windowed mode.
  1. Open %USERPROFILE%\Documents\Diablo III\D3Prefs.txt
  2. Make sure that this line is adjusted:
  3. DisplayModeWindowMode "0" to DisplayModeWindowMode "1"

No Diablo III License Attached[edit]

Method - No Diablo III License Attached

This error message may appear:

|This Battle.net account does not have a Diablo III License attached to it.
  • A possible fix is to correctly set the region within the game settings, within the Options > Account > Server Region settings.[13]


Running programs that put an overlay over Diablo III (such as Mumble and MSI Afterburner) can cause Diablo III to crash. Use these overlays at your own risk.[14]

Problems with Steam overlay[edit]

Problems with Steam overlay
  • Add DiabloIII.exe with the + Add a game on the bottom left
  • Right click Diablo III in the library and choose Properties
  • Add -launch to the end of the target.
  • If the game doesn't launch correctly, make sure the Battle.net Launcher application is already running before starting the game from Steam.

Cinematics not playing or are missing from cinematics menu[edit]

Cinematics not playing or are missing from cinematics menu

1. Edit %USERPROFILE%\Documents\Diablo III\D3Prefs.txt

2. find the PlayedCutscene lines, and edit them to read as follows:

PlayedCutscene0 "15"

PlayedCutscene1 "15"

PlayedCutscene2 "15"

PlayedCutscene3 "15" 3. Save and exit the file, and try again.[15]

Installation Issues[edit]

Change Client Language[edit]

Update 8 June 2012: Blizzard appear to have restricted client language switching.[16] Errors 81, 82 or 84 displays: "The client does not match the accounts native language. Please, use the game native client." There is no known fix as of yet, as Blizzard controls the language restrictions from their servers.

Language change menu.
Language change menu.

Client language files can be adjusted from the options menu. Once the change is applied, a patch of approximately 3 GB is downloaded. Client language cannot be changed back until this download reaches the 'playable' state, and one re-enters the client to change the language option again.[17]

Available languages are:

  • English (United States)
  • Spanish (Latin American)
  • Korean
  • Chinese (Traditional)
  • German
  • Spanish
  • French
  • Italian
  • Polish

"Updating game files" Issue[edit]

Some players are reporting the game getting stuck at installation in the "Updating game files" part.

Method 1 - Disable Anti-Virus Software[edit]
Method - Disable Anti-Virus Software
  1. Turn off your anti-virus software and firewall.
  2. Loading the setup file again.
  3. Running the launcher as administrator.
Method 2 - Connect Using Different Network Adapter[edit]
Method - Connect Using Different Network Adapter

The Blizzard Agent may be attempting to connect over the wrong network adaptor. The following steps may resolve your issue:

  1. Open the Control Panel.
  2. Select "View network status and tasks".
  3. Select "Change adapter settings".
  4. Right click on each adapter and select "Disable". Leave your primary adapter (the one that provides your internet connection) enabled. You should now have only one enabled adapter.
  5. Check that you are still connected to the internet.
  6. Go to %PROGRAMDATA% and delete the Battle.net folder (if it exists).
  7. Retry the installer/launcher.
Method 3 - Delete/Modify Agent Files[edit]
Method - Delete/Modify Agent Files
  1. Go to %PROGRAMDATA%\Battle.net\Agent\
  2. Delete Agent.exe.
  3. Edit Agent.db.
  4. Change p2penable : true to p2penable : false

Installation Stuck At 10%[edit]

If the user has any connections configured in "Dial-up and Virtual Private Network settings" and they're set to "Dial whenever a network connection is not present," the install won't proceed past 10%.[18]

Installation Not Doing Anything[edit]

If the installation has yet to do anything you might need to make sure your secondary logon has been enabled. Do so by going through - Control Panel/Administrative Tools/Services, right click Secondary Logon and proceed to enable it by setting the start up type to automatic.

Low frame rate (OS X)[edit]

Low Frame Rate
  1. Using settings in the D3Prefs.txt mentioned below one can achieve a reasonable frame rate on e.g. the MacBook Pro Mid 2010 with the Nvidia 330M.
  2. Open the D3Prefs.txt and set the following to options to 1:
  • DisableTrilinearFiltering
  • HardwareClass

Can't ⌘ + Tab (OS X)[edit]

Check that you haven't enabled Caps Lock as that disables +Tab , although +M still functions correctly.

System requirements[edit]

Minimum Recommended
Operating system (OS) XP Vista, 7, 8, 8.1
Processor (CPU) Intel Pentium D 2.8 GHz
AMD Athlon 64 X2 4400+
Intel Core 2 Duo 2.4 GHz
AMD Athlon 64 X2 5600+ 2.8 GHz
System memory (RAM) 2 GB 4 GB
Hard disk drive (HDD) 25 GB
Video card (GPU) Nvidia GeForce 7800 GT
ATI Radeon X1950 Pro
Nvidia GeForce GTX 260
ATI Radeon HD 4870
Minimum Recommended
Operating system (OS) 10.8.x 10.9
Processor (CPU) Intel Core 2 Duo Intel Core i3
System memory (RAM) 4 GB
Hard disk drive (HDD) 25 GB
Video card (GPU) Nvidia GeForce 8600M GT
ATI Radeon HD 2600 Pro
Nvidia GeForce GT 330M
ATI Radeon HD 5670
The game does not support FileVault and FileVault 2 on OS X


  1. Auction House FAQ Updated - Diablo III
  2. Patch 2.2.0 Features and Data Mining - Forums - Diablo III
  3. http://us.battle.net/d3/en/forum/topic/5150755817
  4. 60 FPS cap still there and more - Forums - Diablo III
  5. VSync still limiting to 60fps on 120hz monitors - Forums - Diablo III
  6. https://www.reddit.com/r/gaming/comments/tn8la/im_going_to_die/c4o2ada
  7. http://us.battle.net/d3/en/forum/topic/4903520596
  8. Tested by Andytizer.
  9. Fix by Andytizer.
  10. http://eu.battle.net/d3/en/forum/topic/4064636470
  11. https://www.reddit.com/r/Diablo/comments/tnxw1/trick_for_logging_in/
  12. Fix by Andytizer.
  13. http://www.gamefromscratch.com/post/2012/05/15/Picked-up-Diablo-3%E2%80%A6.aspx
  14. http://us.battle.net/d3/en/forum/topic/4916972036
  15. http://eu.battle.net/d3/en/forum/topic/4784318688?page=1#10
  16. http://us.battle.net/d3/en/forum/topic/5578597286?page=1
  17. http://gaming.stackexchange.com/questions/66164/can-i-change-the-language-the-game-client-uses
  18. http://us.battle.net/d3/en/forum/topic/4916972036