Diablo III

Current version of the game

Application Details:

Version: Current
License: Retail
Votes: 35
Latest Rating: Gold
Latest Wine Version Tested: 2.19-staging

Maintainers: About Maintainership

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

the hole game works fine same for the bnet launcher

sound works

seems all working fine

What does not

the grafik cards does work slowly with high resolution


What was not tested


Hardware tested


  • GPU:
  • Driver:

Additional Comments

start battlenet install the game and start Diablo3 RoS works without problems tested under Diablo 3 RoS v. 2.3.033567

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Oct 29 20172.19-stagingYes Yes YesGoldJan Bradávka 
ShowArch Linux x86_64Oct 07 20172.18-stagingYes Yes YesGoldMaciej Stanczew 
ShowDebian 9 (Stretch)Jul 23 20172.0.2N/A Yes GoldDaniel 
ShowArch LinuxMay 05 20172.7Yes Yes PlatinumSigz 
ShowLinux Mint 18.1Feb 06 20172.0Yes Yes GoldDawid Data 

Known Bugs

Bug # Description Status Resolution Other apps affected
11674 Dual-core unsupported in WoW and SC2 STAGED View
30849 Diablo 3: Hangs on "Authenticating Credentials" REOPENED View
30920 Diablo 3: Random freezes UNCONFIRMED View
30967 Diablo III: Resolution problems without virtual desktop UNCONFIRMED View
30993 diablo 3 d3d device error 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
33111 Graphical Artifacts in Diablo 3 on AMD Graphics RESOLVED NOTOURBUG View
35990 keyboard becomes unresponsive in blizzard games UNCONFIRMED View
44032 Diablo 3 2.6.1: Mouse-downs register as mouse clicks UNCONFIRMED View

Show all bugs

HowTo / Notes

[OBSOLETE] Workarounds

Below workarounds should not be needed anymore to run the game. If you find that they are still required, please post it in the comments.

1. How to run the game on 64-bit systems

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 chatting, authenticating, 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 '<path to Diablo III.exe or Launcher.exe>'

2. How to fix audio with PulseAudio

Edit /etc/pulse/daemon.conf and add

default-fragment-size-msec = 5

After that the volume was really low and it appears that pulse volumes bars per application. so just clicking on the sound Icon, tools icon and going to Applications tab allowed me to adjust the volume of the game.

Tested on Alllen and Heath Zed 10FX USB sound card.


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

i think i stumbled on a another fix.
by Paul Cornett on Wednesday December 27th 2017, 15:28
can someone verify: I was having occasional mouse freezing in gnome. The mouse would click but not move. The suggested fix was to remove libinput and replace with evdev. I did that and it solved my mouse issue. I just tried in d3 and the problem seems to have gone away. running the lastest 2.21-staging. Now i dont know if there was a fix to wine-staging or the replacement of libinput.
RE: i think i stumbled on a another fix. RE: mouse click not staying down.
by Paul Cornett on Wednesday December 27th 2017, 15:29
crap... put it in wrong spot
How to work around mouse-downs-register-as-mouse-clicks problem
by Steve Soule on Tuesday November 28th 2017, 15:51
For me, in order to stop the mouse-downs-register-as-mouse-clicks problem in Diablo 3 2.6.1 with wine-staging 2.21, I had to recompile wine with the right patch. I'll attempt to explain how to do this here.

Step 1: Compile (build) wine. Instructions are here: Make sure you build wine 2.21 and not some development version. You can get wine 2.21 source with git, or you can get it here:

Step 2: Download wine-staging 2.21 source. You can get it with git, or you can get it here:

Step 3: Apply the patch "kernel32-SetFileCompletionNotificationModes" from wine-staging using
./ DESTDIR=../../wine-source kernel32-SetFileCompletionNotificationModes
replacing "../../wine-source" with the path to your wine-2.21 source. Note that you have to be in the wine-staging "patches" directory when executing

Step 4: Rebuild wine (both configure and make).

Of the four above steps, the most difficult and painful, by far, is the first step, because you need to install lots of development stuff on your computer in order for wine to compile. But you ought to be able to complete all four of the above steps in half an hour or so, assuming you don't get lost.

Hopefully, the patch "kernel32-SetFileCompletionNotificationModes" will start being included in non-staging wine soon so that we don't have to do all this in order to play Diablo 3.
by Matthias on Saturday November 25th 2017, 9:29
Thanks for your hints.
I used the unlimeted backgroudn and foreground FPS and the single Core command.
It seems to work so far.
Single click problems did not solve this way. In Addition I closed the app. Did not work neither.
Thanks for the hints
mouse control after changing from xp to 7 or higher
by Paul Cornett on Friday November 10th 2017, 15:16
i am getting a bug that my char just stops moving when holding down button. Didnt have this issue prior to 2.6.1 of D3. I have gotten around the problem by using setarch and forcing 32bit and enabling virtual desktop in winecfg. Can someone confirm that they have the same issue? Running 2.20 staging.
RE: mouse control after changing from xp to 7 or higher
by Paul Cornett on Friday November 10th 2017, 15:19
i should add it just stops at the last place i clicked instead of following the mouse.
RE: mouse control after changing from xp to 7 or higher
by Maciej Stanczew on Saturday November 11th 2017, 7:40
I did not experencie the problem you describe – my character correctly follows the mouse when it's held down. I'm running also on Wine Staging 2.20, with a 64-bit Win 7 prefix. I did however encounter the problem described in bug #31262, when I had Lock Cursor option enabled; I am now launching D3 without virtual desktop, in Windowed Fullscreen mode, and with Lock Cursor disabled, and I have no problems with mouse cursor.
Maybe your issue is somehow related to display settings – what is your video configuration in D3?
RE: mouse control after changing from xp to 7 or higher
by Paul Cornett on Saturday November 11th 2017, 8:11
3840x2160@60. I been using fullscreen, but will try the window and see if i can reproduce.
RE: mouse control after changing from xp to 7 or higher
by Paul Cornett on Saturday November 11th 2017, 8:17
i just tested with window (fullscreen) and it works much better. Never thought of using that. Thanks for the tip.
RE: mouse control after changing from xp to 7 or higher
by H-J. Stumm on Saturday November 11th 2017, 13:39
can confirm that on 2.20 and patch 2.6.1 on full screen i will test it in window mode too
RE: mouse control after changing from xp to 7 or higher
by Steve Soule on Monday November 13th 2017, 17:11
I am also seeing this problem. Diablo 3 usually (but not every time) acts like I've clicked when I'm actually holding the mouse button down. I tried fullscreen, windowed, and windowed-fullscreen, and that didn't have any effect. I tried configuring wine with and without a virtual desktop, and that had no effect. I'm running wine-staging 2.20 with Diablo 3
RE: mouse control after changing from xp to 7 or higher
by Paul Cornett on Monday November 13th 2017, 17:13
try using setarch also. I had to use that with the virtual desktop and windows (full)
RE: mouse control after changing from xp to 7 or higher
by Steve Soule on Monday November 13th 2017, 17:24
Okay, I've now tried all 16 settings combinations, and seen the problem on all 16 combinations. The combinations are: both with and without "setarch i386 -3"; with and without wine set to use a virtual desktop; Diablo 3 set to fullscreen, windowed, or windowed-fullscreen mode; and, for windowed-fullscreen mode, both with and without Diablo 3's lock-cursor-to-window option.
RE: mouse control after changing from xp to 7 or higher
by Steve Soule on Tuesday November 21st 2017, 3:09
After a great deal of work, I've found a workaround for this problem that works for me. The culprit seems to be the patch "server-send_hardware_message", one of the 440 patches that are part of wine-staging 2.20 and not part of wine 2.20. With wine recompiled without this patch, the problem disappears: my mouse-button holds register as mouse-button holds, not clicks. I also found that the only patches needed to make Blizzard app and Diablo 3 work with wine 2.20 are the patches "kernel32-SetFileCompletionNotificationModes" and its prerequisite "ntdll-FileNameInformation", and not the 438 other patches in wine-staging 2.20.
Single Core only
by Rob Walker on Wednesday November 1st 2017, 23:14
Ive installed it and it works for 32bit but the launcher is very very slow. It seems that it only uses one of my six cpu cores.
in the D3 Forums i found a workaround with a Program (UnparkCPU) that forces windows to use all cores but this doesnt work in wine(or at least i dont know how)

tried to install it on 64, but launcher doenst start after installation.
tried wine 2.20 and 2.18 but the launcher crashes after 1 second (debug shows some wierd stack overflow)
Changes to removed XP support?
by Jen on Wednesday August 16th 2017, 17:30
RE: Changes to removed XP support?
by Caine on Wednesday August 23rd 2017, 7:07
uho, it means no directx 9 support anymore, and since directx 11 is not up to par yet (it works, but in the single digit fps)
RE: Changes to removed XP support?
by Jen on Wednesday August 23rd 2017, 8:44
I've been trying the PTR, and the past two patches, everything's been fine. They still list a lot of older video cards for recommended hardware (but have Windows 7 as the lowest version of windows), so I'm thinking dx9 isn't going away.
RE: Changes to removed XP support?
by Serenity Moral on Thursday October 26th 2017, 9:39
I didn't try the PTR, i tried the live patch. Since XP support is droped the game doesn't start anymore in 32 bit mode.
a) winecfg set to WinXP/2003 : Error msg at start is "Winvers not supported anymore" use at least win7
b) winecfg set to Win7 and above ... the game does nothing, not even the logo on startup.
c) 64bit game still doesn't run smooth. it is VERY slow but it is starting.
RE: Changes to removed XP support?
by Jen on Thursday October 26th 2017, 9:56
Huh. Are you using staging? I've got things set to Windows 7, and am using 32-bit fine. (This was the same day the patch launched.)
RE: Changes to removed XP support?
by Jen on Thursday October 26th 2017, 10:21
I'm set to Windows 10, sorry. And I'm using a 64-bit wineprefix, but running 32-bit Diablo III. I'm currently using wine-staging 2.17. (Been too lazy to upgrade to 2.19.)
RE: Changes to removed XP support?
by Serenity Moral on Friday October 27th 2017, 13:54
i habe a 64bit prefix too and use 2.19 staging, tried 2.17 before, the game was running perfectly until i got the patch.
I tried win7 - win10. When i start the game (from bnet or directly) the game seems to start, i'll get a process running (can seet is in the ps-list) but on the monitor it does nothing (not even the logo)
RE: Changes to removed XP support?
by Maciej Stanczew on Friday October 27th 2017, 15:16
Have you maybe tried with a clean wineprefix? I'm also using 64-bit prefix on 2.19 staging with win7, and I have no problem running the game (although, like you said, the logo is not displayed – just after a couple of seconds the game launches).
If it still doesn't work, is there maybe something interesting in the logs when you start the game directly? Or, do you have any dll overrides set (none should be needed for Diablo III)?
RE: Changes to removed XP support?
by Serenity Moral on Saturday October 28th 2017, 9:42
Sure, i tried a new 64bit wineprefix too but my blizzard games are not installed in wine. i took them directly from my win7 partition. The games are all in their own subdirs on this mountpoint.

As i could find out - the problem itself was hosted by the nvidia driver from the debian sid tree, as i updated this driver the last time i got also some bad performance in worldofwarcraft too. so i removed every sid package depending the nvidia driver and downloaded the latest original one from the nvidia website. after the install everything is running fine now as before the patch.

thx 4 help
RE: Changes to removed XP support?
by Rob Walker on Wednesday November 1st 2017, 23:02
could you explain how you did install that on 64?
im trying it but it wont work.
When you are having issues with closing necromancer promotion
by Caine on Tuesday July 4th 2017, 10:54
Found out the trick is to reinstall IE8 (and maybe dotnet4.5 , 4.6 .. )

But was getting weird errors with winetricks. Found out, the version I had of winetricks was too old.
I am using Ubuntu , so I replaced the winetricks in /usr/bin with the one from :

then I did a : winetricks --force ie8 , and it worked.

took me awhile to figure that one out :)
Code 7
by Nelson on Monday July 3rd 2017, 14:30
finally got Diablo 3 RoS to install and show up properly at the login screen for the game, however all attempts to log in give me the message "There was a problem logging in. (Code 7)". anyone happen to come across this here and was able to get past it?

also I'm not able to log into at all through the Blizzard App client... is this normal?
can't close necromancer promotion
by HeroRobb on Monday July 3rd 2017, 2:36
Windows 10 Wine 2.11 staging 32 bit
Linux Mint 18.1

Diablo has been working fine for me, but I've never been able to see much of the stuff on the app which didn't bother me. Now that the necromancer is out, there is a promotional splash page on diablo 3's section of, which covers the play button. The problem is that the X in the top right corner used to close the promotion does not appear. I've tried clicking where it should be, messing with some settings, but I really don't know what to do here.
black screen
by Nelson on Sunday July 2nd 2017, 12:56
using wine-2.8 and winetricks-20170614 on Slackware64 14.2, while also having installed corefonts, ie8, and vcrun2015 along with adding d3dcompiler_47 in winecfg. install went fine, however when I start the game I can hear the music playing however my screen is black. any suggestions? running nvidia 375.39 binary drivers as well.
RE: black screen
by Nelson on Monday July 3rd 2017, 10:42
this is what shows in terminal

err:d3d:wined3d_debug_callback 0xa8cae60: "GL_INVALID_OPERATION error generated. Source and destination dimensions must be identical with the current filtering modes.".

any suggestions??
Check wine for Blizzard App
by Martin Ruso on Saturday July 1st 2017, 14:14
I've had quite some trouble installing the game and getting it to work. After figuring it out, I've noticed all is already well documented in Wine under Blizzard App. Don't forget to look there.
After resolving all, mainly vcruntime140 and installing lib32-libldap, lib32-gnutls, everything works like charm :) great gameplay and performance. Enjoy.