Last release: June 11, 2023
Download: Gw2Launcher.exe (build 7254)

See the wiki for more information and recent changes. Simply download (64-bit) and place the executable wherever you'd like it.

GW2 will start a new renderer process whenever it's needed and close it when it's no longer used. If GW2 is closed while it's starting the renderer, it's possible for the renderer to remain active with high CPU usage.

Enabling the following option will automatically close any remaining CefHost processes linked to an account when it exits:

Settings > Guild Wars 2 > Browser priority

Note this option will be enabled by default with the priority set to normal (default).

GW2 will try to write to CefHost.exe on launch and on play. Problem is, CefHost.exe is already being used by GW2 when clicking play, resulting in another copy of CEF being created for no reason (it's not even used).

Enabling the following option will prevent it and allow multiple accounts to share the same files:

Settings > Guild Wars 2 > Management > Rename CEF on launch

This is a bug GW2 introduced back when DX11 was implemented. The slower GW2 is to load, the more likely it is to occur. There are a few options to help with this:

Settings > Guild Wars 2 > Process priority while initializing the game: high.
Settings > General > Launching > Timeout: relaunch if character select hasn't loaded within 15~30 seconds.
Settings > General > Launching > Delay until the main window is loaded.

GW2 uses a mutex to prevent multiple instances from being opened at the same time. In addition, GW2 also locks access to Gw2.dat, which prevents other processes from reading it. By killing the mutex and enabling -shareArchive, multiple clients can be launched simultaneously.

When -shareArchive is enabled, GW2 will not be able to modify any files. In order to update the game or modify your settings, the game must be launched normally, which will be handled for you.