Guild Wars 2

64-bit Guild Wars 2 client officially released May 17, 2016. This is the ideal client to be using and should be considered the default client.

Application Details:

Version: 64-bit Client
License: Retail
Votes: 1
Latest Rating: Garbage
Latest Wine Version Tested: 6.0-rc1

Maintainers: About Maintainership

Link Play For Free Link Guild Wars 2 Wiki 64-bit Client Information Link 64-bit Client FAQ Forum Post Free Download Guild Wars 2 64-bit Setup Executable

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 perfectly.

What does not


What was not tested


Hardware tested


  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

Ubuntu 18.04.1 LTS (EM64T)
Gnome 3.28.2
Intel Core i5-8400 2.8GHz 6GB
16GB G.Skill Ripjaws V DDR4-2400 PC4-19200
GeForce GTX 1060 6GB (using proprietary NVIDIA 390 driver)
1920 x 1080 full-screen (HDMI)
Wine 3.0.1-Ubuntu (set as Windows 7)
GW2 runs at ~42 FPS using Xfinity @ 10MB/sec down. & 6MB/sec up.
GW2 graphics at high settings
GW2 client/updates took ~6-8 hours to download @ 2MB/sec
GW2 launcher icon opens the game just like in Windows/Mac

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowFedora 33 x86_64Dec 31 20206.0-rc1Yes Yes NoGarbagephre4k 
ShowArch Linux x86_64May 20 20205.8-stagingYes Yes YesGoldSinan Ozan 
ShowSlackware64 -currentMar 17 20205.4Yes Yes NoSilverdjango 
ShowArch Linux x86_64Aug 07 20194.13Yes Yes NoBronzeSinan Ozan 
ShowArch Linux x86_64May 06 20194.7-stagingYes Yes YesGoldYudha 

Known Bugs

Bug # Description Status Resolution Other apps affected
32010 Guild Wars 2 updater uses always 100% of a CPU core UNCONFIRMED View
32152 Guild Wars 2: Missing sound and game crashes on time adjusting UNCONFIRMED View
40299 Guild Wars 2: Graphic shows through the ground UNCONFIRMED View
40300 Guild Wars 2: Mouse gets temporary invisible on the Launcher UNCONFIRMED View
40843 Guild Wars 2: Game crashes on uninstalling UNCONFIRMED View
41962 Guild Wars 2: Mouse acts if raw input is broken if The Forest is opened in window mode UNCONFIRMED View
42145 Guild Wars 2 crashes on some configurations UNCONFIRMED View
45453 Guild Wars 2: Launcher crashes with assertion "jobThreads && (jobThreads <= hardwareThreads)" CLOSED FIXED View
50140 "Guild Wars 2 Launcher" over time consumes all available memory CLOSED FIXED View

Show open bugs

HowTo / Notes

Game Data Updating and Integrity Checking/Repair

You can fully download all of the game data and any future updates required for Guild Wars 2 by appending -image as a command-line argument to the Guild Wars 2 executable (Gw2-64.exe or Gw2.exe). An example can be found below:

WINEPREFIX=~/'Wine Prefixes/Guild Wars 2' wine 'Gw2.exe' -image

You can also check the integrity of the game data archive by appending -repair as a command-line argument (this can take longer than 5-10 minutes to complete):

WINEPREFIX=~/'Wine Prefixes/Guild Wars 2' wine 'Gw2-64.exe' -repair

For quick guidelines:

  • For initial installations, -image is recommended so you don't have to worry about streaming data during gameplay
  • If you've had your Gw2.dat for a while, it's a good idea to run -repair on it every now and then after updates
  • If you've had to hard-shutdown your computer while GW2 was running, running -repair is highly recommended


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

by Lambda on Sunday January 24th 2021, 14:53
I'm seeing a similar behaviour since about 17.1.2021 - I'm on wine 6.0.1 (staging) (Fedora package wine-6.0-1.fc33.x86_64 ) and get similar lockups with the message close to it in the log:

0120:err:sync:RtlpWaitForCriticalSection section 000000014218F170 "?" wait timed out in thread 0120, blocked by 0000, retrying (60 sec)

GPU is AMD Radeon RX 560 (as discrete GPU in a laptop).
Wine-Staging 6 rc5 freeze
by Bart Vaes on Thursday January 7th 2021, 15:58
As the subject says: using Wine-Staging 6.0-rc5 I suddenly get periodic screen freezes that last 3-4 sec or so.
I'm using OpenSUSE Leap 15.2 and for some reason the Wine packages are very old (latest=5.0, a year old but works flawless actually).
I get this output:

bart-at-localhost:~> mesa_glthread=true WINEDEBUG=fixme-all wine64 start /unix "$HOME/Games/Guild Wars 2/Gw2-64.exe"
bart-at-localhost:~> ATTENTION: default value of option mesa_glthread overridden by environment.
Native Direct3D 9 v0.7.0.368-release is active.
For more information visit
mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
fixme:d3d9nine:D3DPERF_GetStatus (void) : stub
0140:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work.
fixme:d3d9nine:DRIPresentGroup_GetMultiheadCount (0x2077ba0), stub!
fixme:d3d9nine:D3DPERF_GetStatus (void) : stub
0140:err:sync:RtlpWaitForCriticalSection section 0000000142153340 "?" wait timed out in thread 0140, blocked by 0254, retrying (60 sec)
0254:err:sync:RtlpWaitForCriticalSection section 0000000142153000 "?" wait timed out in thread 0254, blocked by 0000, retrying (60 sec)
0124:err:sync:RtlpWaitForCriticalSection section 000000014218DEF0 "?" wait timed out in thread 0124, blocked by 0000, retrying (60 sec)

The last 3 lines get repeated and causes the freeze.

CPU: AMD FX-6300
VID: AMD Radeon RX 550
wine-staging 5.20 causes the launcher to fill all the memory until the system runs out of memory
by Artemis3 on Saturday November 7th 2020, 0:07
Running with Gentoo, 64 bit profile. Until wine-staging 5.19 all is good. With 5.20, the launcher fills up all your memory causing the dreaded Out Of Memory condition. Downgrading back to 5.19 cures the issue.
by Bruno Oliveira on Friday July 17th 2020, 10:37
I have installed with lutris and everything works just fine.

by Jimy cooper on Wednesday May 13th 2020, 3:20
why can't i install the 5.4 expansion?
4.10 and the Trading post
by Jen on Thursday June 13th 2019, 23:36
I've tried both 4.10 and 4.10-staging, and every time I try accessing the trading post, I get "net::ERR_FAILED". Anyone else getting this? I didn't get it with 4.9-staging.
BUG: Black Screen
by Ricardo Rodrigues on Wednesday June 20th 2018, 21:55

Posting a Bug Report is a pain, so a comment will have to do.

I get a Black Screen when entering the game (after logging in) and this is because I changed the scale in xrandr.

Steps to reproduce:

1. Change scale: xrandr --output DP-2 --scale 0.75x0.75
2. Start the game.
3. Black screen, but game is responsive.

A lot of message errors will appear saying: X11DRV_ChangeDisplaySettingsEx No matching mode found 1440x1620x32 @0! (XRandR 1.2)

Current Solution: HACK

1. Create a script to start the game.
2. Before the command to start, scale back: xrandr --output DP-2 --scale 1x1
3. After the command to start, scale: xrandr --output DP-2 --scale 0.75x0.75
4. Start the game (no black screen)
RE: BUG: Black Screen
by Bruno Oliveira on Friday July 17th 2020, 10:44
you actually don't need a script.
you can create a .xprofile $HOME and /etc/xprofile

content of my xprofile:

xrandr --output HDMI-A-1 --panning 1920x1080 --scale 1.406x1.406
xrandr --dpi 141

The game works just fine for me ;)
by Jeffrey Jensen on Tuesday March 6th 2018, 17:56
Is this confirmed working in Gentoo Stable? I'm having issues getting it launched currently. Haven't messed with it too much yet
Guild Wars 2
by Frank on Monday January 1st 2018, 22:55
I found that this game works perfectly with older versions of wine too, it's all good (from 2.0 and upwards), I'm using Debian Stretch. I worked away all the error messages in the debug output and it works great. I even use the nvidia optimum, all good. Only i found that by switching to Wayland, that the mouse error (that the mouse stops at a certain point which prevents you from looking 360 degrees in 1 move) from long ago is back. In X I don't have this.
RE: Guild Wars 2
by Bruno Oliveira on Thursday November 12th 2020, 13:19
Works flawlessly with proton as well.
This should be PLATINUM!