Diablo III 2.x.x (No RoS)

Category: Main > Games > Role Playing Games > Diablo III > 2.x.x (No RoS)

NameDiablo III
Version2.x.x (No RoS)
License Retail
Votes 31
Wine Version1.7.31
Free Download Official game site.
Maintainers of this version:
Game version that had been officially released on the 15th of May, 2012.  This is for people without the Reaper of Souls Expansion. 
Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results (selected in 'Test Results' table below)

What works

What does not

What was not tested

Additional Comments

Works great, but you will likely need to use this command to launch it:

setarch i386 -3 wine "/path/to/diablo-3/Diablo III.exe"
Test Results
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
CurrentArch Linux x86_64Nov 23 20141.7.31 Yes Yes Gold Zachary Hill 
ShowUbuntu 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 
ShowLinux Mint 15 "Olivia" x86_64Oct 12 20131.7.3 Yes Yes Platinum N3oTraX 
ShowUbuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)Aug 25 20131.6 Yes Yes Gold Corben 

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
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 CLOSED ABANDONED View
33111 Graphical Artifacts in Diablo 3 on AMD Graphics UNCONFIRMED View
33413 Diablo III: Intermittent non-responsive UI elements CLOSED ABANDONED View
33686 Diablo III: Audio cuts out after a while of game play UNCONFIRMED View
35990 keyboard becomes unresponsive in blizzard games UNCONFIRMED View
37984 Diablo 3: Video card missing required features 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!

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.


1. How to run the game

you execute the launcher with the following command:

 setarch i386 -3 wine 'c:\program files\\ launcher.exe

fixes many freeze and network issues.

 2. how do I 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.

 thanks to this wonderful community we've got the game working great! :)

keep up the good work! 

Information and bugs

 Sreen Resolutions: 

Linux gentoo amd64, with nvidia-drivers official -  NVIDIA Corporation GF119 [GeForce GT 520] - 800x600 resolution

Linux gentoo amd64, with nvidia-drivers official - NVIDIA Corporation GK104 [GeForce GTX 680] (rev a1) - 1280x800


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

Black/White screen launcher
by Artem on Monday March 23rd 2015, 14:27
I have tried every possible existing solution from every forum for last week.

The easiest way for me was:
1. Install Diablo 3 in virtualbox/vmware virtual machine
2. Copy Diablo III folder to your .wine/drive_c
3. Run Diablo without 'Launcher' (-launch option for Diablo III.exe)

E.g.: setarch i386 -3 -L -B -R wine Diablo\ III/Diablo\ III.exe -launch

'Diablo\ III/Diablo\ III.exe' - revise with path to your Diablo III.exe

Hope this will save time for somebody :)

[post new] [reply to this]

Clean up
by Guy Fleming on Monday August 25th 2014, 20:06
I am currently cleaning up the Diablo 3 game site. So if you see a verison removed that shouldn't be removed, simply re add the results, please provide if your using override dlls, archset, and OS. I do not care what version of wine you use. Email me as well when re adding.

[post new] [reply to this]

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]

  • RE: by Guy Fleming on Tuesday August 26th 2014, 8:59

   << Back

Page loaded in 0.04205 seconds.