World of Warcraft

The Old God N'Zoth has been unleashed from his titan wrought prison, and an ancient corruption has taken root across Azeroth, turning friends into foes and trapping warriors' minds in nightmare visions of a hopeless future. As despair and madness consume the land, the heroes of the Horde and the Alliance will need to fight for their sanity—and the fate of their wounded world in this content update.  

ShadowLands is live. Sylvanas and the Jailer in together, to bridge the world of the dead with Azeroth.

Application Details:

Version: 9.1.5
License: Retail
Votes: 231
Latest Rating: Platinum
Latest Wine Version Tested: 7.0-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

Everything that I tested works:

- Starting the game
- Logging in
- Character selection/creation
- Server selection
- Adjusting in-game settings
- Questing and dungeons (70 to 100fps with graphic quality set to 8)
- Raiding (around 40 fps with graphic quality set to 8)
- Most addons (ElvUI, TSM, BigWigs, etc.)
- Auction house

Updates through application

Installation was performed a long time ago with wine, but was not tested specifically with this version

What does not


What was not tested

- In-game Voice Chat

- In-game Shop

Hardware tested


  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

Since several versions, wine staging and dxvk uses PE format for libraries, which requires them to be build with mingw support (obvious for dxvk which does not compiles without it, less obvious for wine which compile fine but does not allow game to run). Enabling mingw involves creating a crossdev environment. i can only recommend to follow gentoo wiki for it ( Once mingw compiler and libraries are fine, you can compile dxvk, and wine with mingw support. With current dxvk, I needed to upgrade my mingw compiler to version 10

I used to have lots of random crash while playing in previous versions: I took the habit of compiling wine with "-march=x86-64" (instead of -march=skylake in my case) which used to fix the issue (not
sure it is still relevant).

I'm running WoW (-d3d11) from a fresh wine prefix with wine 6.12 (staging), dxvk 1.9, nvidia drivers 460.67.

Windows is set to version 10 in winecfg, CSMT is disabled and winetricks is not used at all.


selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowGentoo Linux x86_64Jan 25 20227.0-stagingYes Yes NoPlatinumb0nt4kun 
CurrentGentoo Linux x86_64Jul 18 20216.12-stagingN/A Yes NoPlatinumb0nt4kun 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)May 06 20215.0.5Yes Yes NoPlatinumPablo Lucero 
ShowopenSUSE Leap 15.2Apr 06 20216.5-stagingYes Yes NoPlatinumAlberto 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Feb 05 20216.1-stagingYes No NoGarbageMaia Everett 

Known Bugs

Bug # Description Status Resolution Other apps affected
44210 GNUTLS_CIPHER_CHACHA20_POLY1305 is not supported UNCONFIRMED View
46410 Screen flickering in WoW NEW View
46416 World of Warcraft dx12/vkd3d crashes soon after login (RADV) NEW View
46978 World of Warcraft shows ghost images when turning UNCONFIRMED View
47471 World of Warcraft 8.2.0 freezes when entering New zone Nazjatar (directx 12) NEW View
47731 World of Warcraft BFA Crash with error 132 Memory could not be read. UNCONFIRMED View
49170 WoW (World of Warcraft) shows colored grass and mosaic effects UNCONFIRMED View
49233 World of Wacraft (WoW) slow fps with the dx11 modern renderer UNCONFIRMED View
49423 Added input lag in World of Warcraft and other games UNCONFIRMED View
49497 WoW (World of Warcraft) crashes with multithreaded modern renderer UNCONFIRMED View
49639 World of Warcraft Shadowlands (wow) has a fly screen effect UNCONFIRMED View
49682 World of Warcraft (WoW) Shadowlands Beta with strange "shadows" in DX11Modern&DX12 UNCONFIRMED View
49781 World of Warcraft (WoW) Shadowlands stays black with DX12 UNCONFIRMED View
50614 World of Warcraft Retail (WoW) crashes with 6.1-staging UNCONFIRMED View

Show all bugs


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

NTFS vs ext4
by b0nt4kun on Monday December 13th 2021, 9:43
Hi, I've been running WoW on wine since vanilla. Since I used to need Windows to proceed with updates, WoW was installed on a NTFS partition (was even FAT32 at first). So currently the partition where WoW files are located (as well as Diablo III,, etc.) is mounted with ntfs-3g. I'm not experiencing any specific issue with my setup, however, since I don't even have Windows installed anymore, I was wondering if anyone had experience running WoW on ext4 partition. More specifically, I'm interested to know:
- if there is any issue/side effect from running WoW on ext4 rather than NTFS (a long time ago I saw something about WoW being confused with ext4 permissions);
- if there is any performance difference (loading time for example).
Any feedback would be appreciated :)
RE: NTFS vs ext4
by Pavel R on Wednesday January 19th 2022, 1:48
Never actually tried to run it from NTFS, used to run from ext3/ext4 partitions since 2011 without any issues. Obviously, can't compare performance, but never experienced any issues with it. In general, ext4 is faster than NTFS.
RE: NTFS vs ext4
by b0nt4kun on Tuesday January 25th 2022, 4:29
Thank you for the feedback. I finally took the time to perform the swap from ntfs to ext4. I don't really see any performance difference, but at least no issue neither.

by Hamidreza on Sunday May 16th 2021, 9:56
How can i instal wow??or other apps.plz upload a video to help
by Jon on Wednesday June 30th 2021, 15:45
Sorry, no video but you just install first:
Crashing in 6.1 - 6.6
by spaceman on Saturday April 17th 2021, 10:48
I was getting the crash in 6.5 and after upgrading to 6.6 today, on Debian Buster.
ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception!
The instruction at "0x000000018000396a" referenced memory at "0x000000000000000 0".
The memory could not be "read".

I'm a little embarrassed to report for anyone else who experiences this issue, that I resolved it, in 6.6 by suffixing my commandline with -d3d11. so:
env WINEPREFIX="/full/path/to/ WoW prefix/" wine '/full/path/to/World of Warcraft/_retail_/Wow.exe' -d3d11

This may have fixed my problems with 6.5, but reading a bug report I was waiting for 6.6 which was patched to fix a similar issue.