Diablo III 1.0.*

Category: Main > Games > Role Playing Games > Diablo III > 1.0.*

NameDiablo III
License Retail
Votes 35
Wine Version1.7.16
Free Download Official game site.
Maintainers of this version:
Game version that had been officially released on the 15th of May, 2012.
Selected Test Results (selected in 'Test Results' table below)

What works

Installs with (perhaps hangs sometimes just stop and start again the downloading)


Online playing.

Not necessary to do the workarround of dbhelp anymore.


I use this command to run it, if not it will stop when receiving hero list.

"To launch the game you need to run the following command:
setarch i386 -3 -L -B -R wine '/path/to/Diablo III.exe' -launch -opengl"

What does not

What was not tested

Additional Comments

Test Results
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
CurrentUbuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)Apr 15 20141.7.16 Yes Yes Gold Capitan Pistacho 
ShowUbuntu 13.10 "Saucy" amd64 (+ variants like Kubuntu)Feb 02 20141.7.11 Yes Yes Gold Dan Johansen 
ShowUbuntu 13.10 "Saucy" amd64 (+ variants like Kubuntu)Feb 02 20141.7.11 No, but has workaround Yes Gold deathapunu 
ShowUbuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)Feb 01 20141.7.11 Yes No Garbage Capitan Pistacho 
ShowArch Linux x86_64Dec 27 20131.7.9 No Not installable Garbage Keith Minix 

Known bugs
Bug # Description Status Resolution Other apps affected
7991 Test Drive: Unlimited messed up graphics REOPENED View
11674 Dual-core unsupported in WoW and SC2 NEW View
30849 Diablo 3: Hangs on "Authenticating Credentials" REOPENED View
30920 Diablo 3: Random freezes UNCONFIRMED View
30963 Diablo III (downloader): Menu bar entries are keeping the background color UNCONFIRMED View
30964 Diablo III (downloader): Font is flickering in the "Connection Info" menu UNCONFIRMED View
30967 Diablo III: Resolution problems without virtual desktop UNCONFIRMED View
31072 Diablo III: Sound is very quiet UNCONFIRMED View
31262 Diablo III in game mouse cursor Out of sync, hangs in place. UNCONFIRMED View
31839 Mouse jumps to the upper left corner of the screen UNCONFIRMED View
32083 Diablo III: Missing logo on startup NEW View
32084 Diablo III: Crash on changing from fullscreen mode to window mode UNCONFIRMED View
32179 Diablo III: changing keyboard layout to nonlatin makes all letters to be questionmarks UNCONFIRMED View
32212 Mouse cursor not released from Blizzard based games UNCONFIRMED View
33111 Graphical Artifacts in Diablo 3 on AMD Graphics UNCONFIRMED View
33413 Diablo III: Intermittent non-responsive UI elements REOPENED View
33686 Diablo III: Audio cuts out after a while of game play UNCONFIRMED View
35725 Diablo III: Error on installing UNCONFIRMED View

Some Wine Diablo III users have reported suspended accounts

Some Wine Diablo III users have reported that their accounts have been permanently suspended

This issue was originally reported on the forums and various others have reported similar problems (see for more details).  However, many users have not had these problems and Blizzard has officially replied that using Wine should not get you banned:

"Playing the game on Linux, although not officially supported, will not get you banned – cheating will." -- Bashiok

Important info for test results posters
Thank you very much for wishing to spend some time on improving AppDB. I have to warn you that general AppDB policies forbid (a) accepting test results for patched Wine versions and (b) forbid accepting results obtained from PoL-driven Wine installations, only "vanilla" unpatched Wine or Wine that had came by default with your distro are considered to be valid. I'm really sorry for that, but it is the way it currently is. For more details feel free to read recent (as of 16th of May, 2012) discussion on wine-devel mailing list. Aside from the requirements above your test results should comply with some simple rules to be accepted:
  • Please, test an application under fresh clean wineprefix;
  • Include exact specs of the computer you had tested an app on (CPU, GPU, amount of RAM and VRAM) in the "Extra Comments" section of the report;
  • Specify versions of essential software components, most notably: is your system 32bit or 64bit, what is the version of the GPU display driver you use and what is the version of the OS kernel;
  • Include detailed information on the native dll overrides you had to use in order to get the game working. If you had installed dlls yourself - include complete information on the sources of dlls and the exact steps you took to install them.
Thank you in advance!

Getting Diablo III to run best under Wine

General info

As of Wine 1.5.6 Wine is able to both install and run Diablo III.  However, if you are running an older version of Wine (such as the 'stable' 1.4.x branch), then you will need to either upgrade to a newer version of Wine or go through some extra steps each time a patch comes out (see the Historical Information section below).


Q: I have a recent version of Wine (>= 1.5.6) and when I try to install the game the installer seems to be stuck at "0%".
A: Make sure you set your Wine prefix to emulate at least "Win XP". There were reports that best results are achived with version set to "Windows 7" or "Vista".

Q: I'm using a recent version of Wine (>= 1.5.6) and trying to install the game from DVD. Installer seems to be having problems with some files missing.
A: Mount your DVD with "-o unhide" mount option, it should help.

Q: When I start up the game and try to log in into I always get "error 3007".
A: You're on recent release of Ubuntu (or on any other distro affected by the ptrace bug, Bug #30410) or running a 64-bit OS. If you think you're affected by the ptrace bug then you can try executing the following in a terminal before starting Diablo III:
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
If you are running a 64-bit OS then you need to set the game to only use 3 GB of memory, to do this you'll need to modify the launcher to include "setarch i386 -3 " before calling Wine or launch the game from the game's folder in the terminal, like so:
setarch i386 -3 wine Diablo\ III.exe

Q: When I play the game I've got bright red graphical glitches at the places that are expected to be rendered full-black.
A: You had enabled forcing anisotropic filtering and/or texture sharpening in the GPU drivers settings utility. Make sure to turn it off into "let an app control it" state and your problem should be fixed.

Q: I'm using Intel GPU from recent series (HD 2000/3000/4000+). When I try to start the game it fails telling that my GPU lacks required features.
A: Make sure that you're on recent-enough distro (2012+) which contain fresh-enough Mesa (8,1+) and kernel (3.1+). Then make sure to install S3TC texture compression support lib (it might be illegal to do in some countries; how to install it is out of the scope of this FAQ - google for it) and start the game up from terminal like this: "force_s3tc_enable=true wine "

Q: I'm experiencing game crashes/hangs at certain places of the game world (like "Cathedral", e.t.c.).
A: Make sure to update your GPU driver. This problem is known to affect older versions of open source driver for ATI/AMD cards, and older versions of closed-source nVIDIA GPU linux driver. There might be other drivers out there suffering from the same problem we're unaware of, so updating driver won't hurt in any case.

Q: I've got "The application encountered an unexpected error." dialog box right after I start up the game.
A: This is most likely due to using builtin Wine's vcrun2008 DLLs instead of native. Try to install VC++ 2008 Runtime into your prefix, it should help. One of the ways to do it is to use "winetricks" script like that: "winetricks vcrun2008".

Q: I'm on Ubuntu and use Unity desktop environment. When I start the game it loads into a shrunk fullscreen where the Unity bar and universal task bar are still visible.
A: This is the incompatibility between compiz and many other applications which are considered by compiz to use "legacy fullscreen approach". You can workaround it by switching into using Unity 2D or by installing "Compiz Config Settings Manager" application and use "Legacy Fullscreen" support option found in "Workarounds" section.

Q: I'm using video card equipped with ATI/AMD GPU/APU and when I start up the game all I've got is a "black screen" or a "black window".
A: Most likely you had hit a bug in the video card driver. Your best bet would be try to update it to the most recent version. In case you are already using latest driver release (or in case it's hard for you to update video card driver for some reason) you might have some luck workarounding this problem by applying a small registry change to your prefix. What you would want to do is to set "AlwaysOffscreen" key to "enabled" under "HKCU/Software/Wine/Direct3D". You could easily do it with recent enough winetricks by executing "winetricks ao=enabled" for your Diablo III Wine prefix.

Q: I'm using video card equipped with ATI/AMD GPU/APU and the game runs fine but I've got some rendering glitches like "large semi-transparent polygons" or "strange triangle-shaped glitches near light sources".
A: It had been reported that due to some unknown reasons (bugs in driver? Wine doing something wrong?) for people using ATI/AMD GPUs it is required to switch Wine's DirectDraw renderer from using OpenGL into using GDI backend. This could be dobe by applying a small registry trick to your prefix. What you would want to do is to set "DirectDrawRenderer" key to "gdi" under "HKCU/Software/Wine/Direct3D". You could easily do it with winetricks by executing "winetricks ddr=gdi" for your Diablo III Wine prefix. Also switching the game to run in "Windowed Fullscreen" mode instead of simple "Fullscreen" might help.

Q: When I play Diablo III I've got extremely low or unstable FPS. My system is equipped with multi-core CPU (dual core or more).
A: This problem also happen on native OS but there it manifests itself as a micro-stutter (rapid FPS jitter). Under Wine for some people it gets much worse and could easily render the game into nearly unplayable state. If you happen to suffer from this problem you could try changing so called "CPU affinity" for main Diablo III process to only use one or two cores of your multicore CPU. How to do it depends on the linux distro you use. In any case first step would be to start up the game and then Alt+TAB from it and run your favorite terminal emulator. Possible commands to use are: (a) "taskset -cp 0 `pidof Diablo\ III.exe`" or (b) "schedtool -a 0 `pidof Diablo\ III.exe`". Using "0-1" or "0,2" in place of "0" might give better results, depending on the phase of the moon and the amount of luck you have.
Another way to achieve the same effect it is use Wine's "Task Manager". To do it execute "taskmgr" inside the Diablo III Wine prefix prior starting up the game and then Alt+TAB into it from game and use its built-in functionality to change CPU affinity of the "Diablo III.exe" process. You could do it by right-clicking on "Diablo III.exe" list entry at the "Processes" tab, selecting "Set affinity..." and de-checking all assigned CPUs except for "CPU 0". Don't forget to press "OK" button before Alt+TABing back into the game. For some cases it might be better to assign two cores for Diablo III main process, like "CPU 0" and "CPU 1" for "real multicore" CPUs (all multi-core CPUs by AMD up to but excluding AMD FX and later series; Intel multicore CPUs without HyperThreading support) or "CPU 0" and "CPU 2" for "SMT-faked multicore" CPUs (AMD FX and later; all HT-enabled Intel CPUs which are really multicore - i.e. Pentium 4 CPU which seems to be "dual core" isn't really "dual core" thus it doesn't fit into this category). Try experimenting with CPU affinity a little so you could find the value that suits your system best. To check FPS inside the game you could press Ctrl+R on keyboard. FPS counter would be displayed at the top left corner of the game window.

Historical Information

Using an old version of Wine to play Diablo III

To play on older versions of Wine (<1.5.6) you either need to upgrade Wine, patch Wine to support AcceptEx, or copy a working Diablo III install from another PC and run the game with the "-launch" command-line parameter. The process looks like this:

  • Copy a working Diablo III install (either from a recent Wine version or a Windows PC).
  • Open up a terminal and navigate into the folder with the installed game files (it is one where "Diablo III.exe" is located), for example:
    cd ~/".wine/drive_c/Program Files/Diablo III/"
  • Execute the command to run Diablo III without using the launcher:
    wine Diablo\ III.exe -launch
  • Repeat this process whenever a new patch comes out.

Patching an old version of Wine to play Diablo III

As of Wine 1.5.6 the patches submitted by Erich were committed and the launcher no longer requires them.  If you are using a previous version of Wine, 1.5.5 or earlier, please read below. 

To get the D3 installer and launcher to work flawlessly under Wine 1.5.5 and earlier, recompiling Wine with patches listed below is needed. You could do it yourself, or you could use pre-built binaries from third parties (in case you're risky enough to not mind security threat it imposes).  For the moment of the writing of this howto there's known PPA for Ubuntu-like distros which had been reported to provide a version of Wine binaries that had been patched to behave well with D3 installed/launcher. It could be found here: Keep in mind that AppDB maintainers have no idea about what is "inside" that PPA and carry no responsibility about its contents.

Gentoo users might want for follow the FAQ provided by another AppDB user, Thomas Meister. He had shared his approach on how to patch and recompile Wine to be compatible with D3 for gentoo linux here:

For brave souls who feel experienced enough to patch and compile Wine themselves (it's not that hard, really!), here are the links on the patchsets that are recommended to use:

"AcceptEx fix" patchset by Erich Hoover, "third" version (compatible and tested with Wine 1.5.5):

  1. [1/4]
  2. [2/4]
  3. [3/4]
  4. [4/4]

"AcceptEx fix" patchset by Erich Hoover, "second" version (compatible and tested with Wine 1.5.4):

  1. Part 1/3
  2. Part 2/3
  3. Part 3/3

"AcceptEx fix" patchset by Erich Hoover, "older" version (compatible with Wine 1.5.2 and a number or earlier versions, have known problems with 64bit arch; use this one only in case "new" version don't work work you):

  1. - [PATCH 1/4] server: Add completion information to async IO callback (try 2, resend).
  2. - [PATCH 2/4] server: Update stored completion information even after an async IO is queued (resend).
  3. - [PATCH 3/4] ws2_32,ntdll: Update async IO callbacks to include completion information (try 2, resend).
  4. - [PATCH 4/4] ws2_32: Use completion information to send AcceptEx completions (try 2, resend).

Note: after applying any of "AcceptEx" patchsets be sure to run "./tools/make_requests" from the top level of the Wine source directory.

Fix for the D3D error on game video setting change/restart

If you are using an old version of Wine (<1.5.7) and are experiencing an issue where you see the dialog "An error occurred reseting D3D. Click OK to retry" then this patch (taken from Bug #28201) should fix your problem:

  1. modified for 1.4+

HOWTO: Run Diablo III on a 64-bit machine

On systems with more than 4 GB of memory Diablo III sees an unusual amount of memory (from its perspective) due to differences in the memory layout on Windows and Linux.  As a result of this, many aspects of the application will fail to function properly (including the Auction House, chatting, authenticate, and closing the game).  To resolve this problem you need to run the game in particular way to tell Linux to use a Windows-like memory address space:

setarch i386 -3 wine ~/.wine/drive_c/Program\ Files/Diablo\ III/Diablo\ III.exe

Once you have done this the game should function appropriately.


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Game crashing
by Issen on Thursday February 27th 2014, 10:45
I'm using ubuntu 14.04 and wine 1.7.13
But since the update to Trusty, the game keeps crashing with this error :

EE ../../../../../../src/gallium/drivers/r600/r600_state_common.c:750 r600_shader_select - Failed to build shader variant (type=1) -12
radeon: mmap failed, errno: 12
err:d3d:wined3d_debug_callback 0x1dc480: "GL_OUT_OF_MEMORY in glTexSubImage".
err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY (0x505) from glTexSubImage2D @ surface.c / 1706

How can I fix that please ?

[post new] [reply to this]

setarch i386 -3 no longer required?
by William on Thursday February 27th 2014, 0:24
I just ran D3 for about 35-40 minutes without using the "setarch i386 -3" trick. I am running a 64bit OS with 6GB of RAM, and I know that I used to require this trick. It has been about 3-4 months since I played, so I have updated wine and other things (running wine-1.7.0 right now).

Anyone else able to check/test/confirm this?

[post new] [reply to this]

Diablo 3 Connection Problems?
by jack on Sunday January 19th 2014, 14:24
I'm having problems connecting to D3 on 2 of my machines. One is running Fedora 19, the other is running 20.

I'm having what appears to be networking connectivity problems at the following places:

* During the launcher 'Checking for Updates'

* Waiting for 'Retrieving Hero List'

* Changing anything once logged in (characters, banner, etc)

* Logging in

* Conversations "hang" on first npc comment ingame, then convo ends with no further graphical interaction. Whole convo is in chat panel

When running from a terminal, I see the following, especially during the Launcher hang:

err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029
err:wininet:open_http_connection create_netconn failed: 12029

I've opened a case with blizzard and my ISP; both were unhelpful. Something stupid im missing here? Everything else appears to operate fine.

[post new] [reply to this]

Unable to run in new desktop app
by Justin Dray on Friday January 10th 2014, 21:22
I have the new desktop app with wine 1.7.9 and it works quite well as soon as dbghelp is set to disabled (other than news/realm selections not working).

I can open WoW and SC2 without issues, however when I click on the launch button for D3 it greys out for 5-10 seconds and then goes back to normal, but never launches the game.

Has anyone else experienced this? I really want to have the new launcher working before RoS is released.

[post new] [reply to this] App Crashes at Startup
by Brandon Bertelsen on Thursday January 2nd 2014, 22:17
The app kept crashing on me immediately after startup. I was able to get it working after following these steps from the top of this page (

1. Run winecfg. (If you have multiple prefixes, make sure it is the correct prefix) (If using PoL click on Diablo III and click "Configure")
2. In the 'Libraries' tab, type dbghelp into the 'New override for # library' box. (It's not otherwise listed)
3. Click 'Add', then 'Yes' when it asks if you are sure.
4. Click on 'dbghelp' in the 'Existing_overrides' list.
5. Click 'Edit'.
6. Set to 'disabled'.
7. Click 'OK', then 'OK'. Client should now run.

[post new] [reply to this]

Can't connect to Server starting with wine 1.7.9
by Johannes Dewender on Friday December 20th 2013, 22:11
Starting with wine 1.7.9 the "msvcp100 (native then builtin)" dll override is needed.
Otherwise not Connection to the Server can be made when logging in (-> login doesn't work)

See for details on the underlying problem.

[post new] [reply to this]

Diablo 3 and open-source amd drivers
by thathatman on Saturday September 28th 2013, 10:50
I wanted to report that diablo 3 is playable with the amd open-source drivers. It is slightly smoother than fglrx. I do experience graphical glitches in the form of red water.
This is with the playonlinux version of wine on ubuntu 13.04.

[post new] [reply to this]

rubber banding and flickering fix
by Netsrotti on Saturday August 31st 2013, 2:41
I found that setting StrictDrawOrdering string to enabled in regedit solved the rubberbanding and graphics flickering bug in act3 and when opening too many menues. I'm using latest nvidia binary beta driver.
Found the regkey at

[post new] [reply to this]

Can only do 2-3 things, then game hangs "out of sync"
by Hauke on Wednesday July 31st 2013, 8:30
First my specs:

- Kubuntu 13.04 with disabled desktop-effects
- nvidia-driver
- installed Diablo3 in a bottle (with Win32 set and Winver=WinXP) from ground up, but problem also occurs when i start my Windows-installed-Diablo3 with wine.

So the good thing is, i can start Diablo3 and everything seemingly works normally, good fps in menu, i can login with my character etc. I can also enter a game and play normally. Also starting an auction works.

But as soon as i do about two to three things in the menu (for example enter the auction house or switch a hero, or leave a game) the game is non-functional. Auctions cannot be started (although the button is clicked, i then wait for about 30 seconds to get the error). Yet the menu looks normal, it's animated etc. Only not usable.
I can - for example - log in, click "resume game" and play for a while. But as soon as i leave the game, and selecting "change quest" does not do anything, and clicking "resume game" brings up Error 316704

It feels like my gameclient and the server get "out of sync", i still can do stuff, but it has no effect on the game.

I then have to kill Diablo from outside the game (since clicking "Exit Diablo3" does not do anything) and restart wine to do more than one or two things.

Do you guys have any advice what could be the reason for this?

Thanks in advance!

[post new] [reply to this]

Anyone got banned in the last few months?
by vexorian on Saturday June 29th 2013, 17:01
Playing steam games natively reminded me of how much of a compromise it is to have to boot to windows just to play this game. I decided I will not do it anymore. The game itself isn't really worth such annoyances. So I am back to using WINE to play this game. If I get banned, so be it. A good excuse to stop playing this game and avoid buying the expansion.

I noticed there are apparently not any reports of WINE users getting banned ever since the time I got unbanned. I wonder if this is still happening?

[post new] [reply to this]

Patch Required!
by Johan Johnsson on Thursday May 23rd 2013, 11:20
Just wanted to share a problem I had on Manjaro Linux 0.8.5 with Diablo 3.

After my installation when I fired up the game I got an dialog telling me that there was a patch I needed and I could only click accept, then the game quits to the launcher that was telling me that the game was up to date. Fired up the game again to be met with the same dialog.

After much search I found the answer somewhere that a package named "lib32-ldap" worked for someone. So I started to search my package manager for similar file and found a package named "lib32-libldap" and installed it.

And that fixed the problem, now I can play. Hope this is for any use for someone!

Best Regards!

[post new] [reply to this]

Once More UBUNTU is Broken
by Cory on Tuesday April 23rd 2013, 19:31
i was having a hard time getting D3 to work today on Ubuntu 12.10 was hanging up really bad so i ran echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope to turn off ptrace and the game runs now :(

[post new] [reply to this]

Diablo 3 performance on wine is greater, than on Windows
by Alexey on Saturday February 23rd 2013, 12:26
It is a strange thing, but I have greater performance of Diablo 3 in Linux(Ubuntu 12.04)\wine on my laptop with Radeon HD7600M, than on Windows 7.

On linux i have about 10-40 fps, when on windows only 5-20 fps on same graphical settings. Maybe wine do not render some graphics?

[post new] [reply to this]

by Alexey on Saturday February 23rd 2013, 12:21
I have the same problem with graphical artifacts on Radeon HD (fglrx 13.1) and wine. Tried all solutions listed above - nothing helped.

Tried Crossover demo - works ok, but I'm not ready to pay about $60 just to play diablo on linux, while the game itself costs only about $30 in my country.

Is there any other solution (maybe some kind of patches for wine for better radeon support) or anything else?

[post new] [reply to this]

   << Back

Page loaded in 0.20086 seconds.