Category: Main Games Role Playing Games Diablo II Lord of Destruction 1.x

Diablo II

Retail expansion and all updates.

  • Post results for the Downloader "here"

Application Details:

Version: Lord of Destruction 1.x
License: Retail
Votes: Marked as obsolete
Latest Rating: Platinum
Latest Wine Version Tested: 7.0

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

Everything works fine. Without any problem.

Completed game on normal difficulty in single player without any crash neither issue.

Also played multiplayer on local network.

100% works.

What does not


What was not tested

Multiplayer on

Hardware tested


  • GPU:
  • Driver:

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Feb 05 20227.0Yes Yes NoPlatinumJeff D. Hanson 
ShowDebian GNU/Linux 12.x "Bookworm" x86_64Nov 18 20216.0.2Yes Yes NoPlatinumSigfrodi 
ShowManjaro Linux 20.1Sep 15 20205.16Yes Yes NoPlatinumRagnar 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Oct 08 20205.0.2Yes Yes NoPlatinuman anonymous user 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Sep 10 20205.0.2Yes Yes YesBronzeno 

Known Bugs

Bug # Description Status Resolution Other apps affected
14456 Diablo II hangs when it loses focus REOPENED View
20362 Diablo II: X11 mouse pointer shows over fullscreen window NEW View

Show all bugs

HowTo / Notes


Copy Protection Final Word

Patch 1.12 from Blizzard disables the CD check.

If you ever get "Please insert disc", this is NOT a problem with detecting the CD. The protection system is probably still built into the game even though the CD check itself is disabled. Make sure you use version 1.12 or later. If you get this problem after having this version installed, you are likely suffering from a buggy video driver as this is the only known (and proven possible) cause at this point.

DO NOT USE NOCD PATCHES - They are pointless, and won't fix the real problem.

HOWTO: Blizzard Downloader

for wine versions 1.12 and earlier:

you need a native mshtml.dll and wininet.dll from ie6sp1 in ~/.wine/drive_c/system32

dont forget to set them as native in winecfg

Easy installation: digital download

If you own a legitimate copy of Diablo II, you can register it on with the serial key, and get a link to an installer (about 1.4GB).

This installer has less issues than the CD version, and is the recommended way to install Diablo II.  It works flawlessly (Platinum) from begining to end.

ALT+CLICK combination

Window managers often have the alt key bound to certain features, especially the alt-click. This is not a wine bug. If you have problems with the alt key in any way do not report it. Fix your window manager. I'm not going to list steps for every one because there are too many possibilites. Figure out yourself or ask in a help forum (here is okay... but be warned all I use is TWM). If you are desperate, turn off window manager managed windows in winecfg.


Go into KDE Control Center, expand Desktop, click window behavior, then click window actions tab. You can turn off the alt-combos. If you want to make window specific settings, click on window specific settings under window behavior on the side.


The option to change the key binding is in System Menu -> Preferences Menu -> Windows.

HOWTO play without mounting a CD

�As of 1.12, it is possible to play without using a CD.

The following is an excerpt from the patch changelog:�

For users that originally performed a "Full Installation" and wish to run without the CD, all ".mpq" files should be copied from the Diablo 2 CDs to the Diablo 2 directory. Most users will only need to copy D2Music.mpq from the Diablo 2 Play CD and/or D2xMusic.mpq from the Lord of Destruction CD.

Anyone who did not perform a "Full Installation" will need to  re-install from CD again to ultimate�ly play without the CD. In this case, a "Full Installation" is required, followed by file copy step noted above.

How-to fix delay in sound

If your game is suffering from a slight delay in sound, then try following these steps:

  1. Open the Wine Configuration Application (Configure Wine)
  2. Click the "Add application..." button
  3. Browse to your Diablo II folder (usually Program Files/Diablo II)
  4. Click Diablo II.exe, and then Open
  5. Select Diablo II.exe from the list: it should turn blue
  6. Go to the Audio tab (it can take a while to load)
  7. Untick ALSA and tick OSS, and you're ready to go!
Installation using the CDs

Running Diablo 2 under Wine

by Jesse Allen the3dfxdude at gmail com

minor updates by Jasmine Iwanek

Last updated 2008-07-11 - wine-1.0.0/1.1.1

Before you get started

This HOWTO only lists information specific to this app. Please keep comments and test reports brief. Please don't post copies of wine logs here! If you have trouble, see other ways of getting help.

Wine+Diablo 2 Status

Generally perfect for Linux users since wine 0.9.12. FreeBSD kernel 6.2 might work, but copy protection will likely be broken.

Minimum Requirements

  • winecfg: A drive letter for your cdrom, and running as Win2k, XP or later.
  • Support for 640x480 and 800x600 video modes.
  • Correct network configuration for online play.
  • A REAL COPY OF THE GAME -- The game probably won't work right if you don't have a real copy.

Recommended Requirements

  • Wine 0.9.20 or later
  • Linux kernel 2.6.17+ OR FreeBSD 6.2
  • Video card and driver that supports hardware based acceleration with OpenGL.

**Bad Versions**

It's recommended to not use these versions of software because they break the game's copy protection:

  • Linux vanilla x86 kernel: 2.6.9, 2.6.10
  • Linux vanilla x86-64 kernel: 2.6.9-2.6.15
  • Linux kernel versions less than 2.6
  • Wine built with GCC 4.0.0-4.0.2
  • Native msvcrt.dll
  • Fedora core 6 modified linux kernel, unless updated to 2.6.18-1.2784.fc6 or later.
  • FreeBSD
  • Incorrectly installed video drivers

Additionally, FreeBSD kernels less than 6.2 might not work with current versions of wine at all.

Installing the Game

Launch winecfg to perform the following tasks:

  • Make sure the Windows version for Diablo 2 is NT 4.0, 2000, XP, or 2003 for correct copy protection support. Diablo 2 supports Win NT 4.0 or later.
  • Create a drive letter for your cdrom if you have not already. For each cdrom drive letter, click advanced, and set the drive type from automatic to cdrom.

It helps to add a device node symlink, so do the following. If your cd-rom drive letter in winecfg is d: and the corresponding device node to your mount point is /dev/hdc then run the following command:
$ ln -s /dev/hdc ~/.wine/dosdevices/d\:\:
Note, you *must* have two colons! You can tell what your device node is in /etc/fstab or viewing your boot-log.

For running the multi-disk install, it helps to run the install using the drive letter and to not switch your shell to the cdrom's path. For example:
~/.wine/drive_c$ wine "D:\setup.exe" (where D: is the assigned letter of your CD drive).
If you run while having a current working directory of /mnt/cdrom, for example, then you will lock the drive and you won't be able to eject the disk.

If during the game's install the progress bar stops, the game is probably prompting you for the next disc, but the dialog is under the installer's window. For full install, the order is Install Disc, Play Disc, then Cinematics Disc. Just swap discs and hit enter when the progress stops.

Running and Playing Diablo 2

Do not use the '-opengl' switch to run the game. Blizzard never completed OpenGL support so they removed it, but left the switch in. All you see when you run it is a badly initialized DDraw mode.

If you use the window option "-w", the game will drop to ddraw mode no matter what.

Do not use virtual desktop with the game! It's not designed to be windowed like that! It still thinks it's full-screen!

If you have missing in-game speech, animation, videos, or crashes between acts, these problems are typically from using a modified executable. Install your game properly.

Multiplayer Setup

Make sure you have the correct ports open. Open outbound and inbound, TCP and UDP, port 6112 and 4000. More on Network Ports

If you are going to play a direct TCP/IP game and the game tells you that it could not detect a valid address, make sure about things:

  1. Have a valid internet addressible IP address for internet play or proper NAT forwarding.
  2. Have a hostname other than localhost.
  3. In /etc/hosts, have a valid hostname of your computer listed with your current IP address you want to use and do not have your hostname listed with Do not have "localhost" listed first either.
Window losing focus

When running the game in Windowed mode (-w switch), if the DIablo II window loses focus, the game freezes. To unfreeze the game press Alt+Enter. So far this has been tested in:

  • Ubuntu "Hardy" 8.04.1 with Gnome
HOWTO fix the 'patch archive is corrupt' issue

I order to correct this issue Wine must run Diablo II from inside Diablo's installation directory.  Here is an example:

  1. Run a terminal
  2. Type:  cd ~/.wine/drive_c/Program\ Files/Diablo\ II/
  3. Type:  wine ./Game.exe


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

Seriously works?
by Maciej M on Sunday October 25th 2020, 6:49
Hello, can you please confirm that in 2020 with newest version of Diablo 2 LOD you can log in to

Very important, if you can post screenshot of server select window it would be great.
RE: Seriously works?
by post-box2000 on Sunday October 25th 2020, 17:01
Yes, it works on wine 5.19 and 5.20 (it was broken long ago by anti-cheat system)
RE: Seriously works?
by Maciej M on Monday October 26th 2020, 6:54
Hmm, maybe with 5.19 and 5.20 it does work but just a second ago i removed wine stable 5.0 and installed wine development wine-5.5 (Ubuntu 5.5-3ubuntu1) on my linux mint 20 iinstallation as that is what we have in repository. Same results - it freezes on login screen.

Here is the output:
0045:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c250 "loader.c: loader_section" wait timed out in thread 0045, blocked by 0043, retrying (60 sec)
002d:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c250 "loader.c: loader_section" wait timed out in thread 002d, blocked by 0043, retrying (60 sec)
003b:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c250 "loader.c: loader_section" wait timed out in thread 003b, blocked by 0043, retrying (60 sec)
0045:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c250 "loader.c: loader_section" wait timed out in thread 0045, blocked by 0043, retrying (60 sec)
002d:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c250 "loader.c: loader_section" wait timed out in thread 002d, blocked by 0043, retrying (60 sec)