Some specific crash solutions below. Please see my previous post for how to identify your issue.
Failed to extract file.
This means one of the binary files needed for the patch failed to be created, and usually means they are in use. First, ensure the game isn’t running. If it is, close it, wait a few seconds, and try again. If you still fail with the same error, check for a lingering “CoherentUI_Host.exe” process:
1. Ensure the game client is closed again.
2. Press Ctrl+Shift+Escape to open up the task manager.
3. On the Processes tab (labelled Details in Windows 8 and 8.1), see if you have an entry that says “CoherentUI_Host.exe” in the “Image Name” column.
4. For each of those entries, click the entry to select it, and click the button near the bottom labelled “End Process”. Click “End process” if a confirmation window pops up.
5. Attempt to start the game.
If you still fail with the same error in the crash details, something else must be using the files. The easiest way to fix it if you get this far is to simply reboot your computer. If all of that fails, and you still experience the exact same problem: Try deleting the “bin” folder inside the game client’s folder (usually “C:\Program Files\Guild Wars 2”).
Edit: Apparently the steam client is also really good at keeping files open. Closing that may help.
Failed to load Coherent DLL: 0×1
This means that the DLL file may be broken. It might be due to a hardware error, a full hard drive, or some other error. The easiest way to attempt to solve this is to ensure you have some space free on your hard drive (50 MB at the absolute minimum, preferably at least 100 MB), and then deleting the bin folder that is inside your Guild Wars 2 folder. It should be re-created the next time you start the game. If that does not help, please contact customer support so we may collect some information on your hardware.
Unable to create ‘…’ (Where ‘…’ is a file name)
This means the game is unable to create the files needed to run it. There is unfortunately not much we can do at this point. Something is preventing us from creating the files we need, and nothing we could do would appear to solve that (including running as administrator). The most common cause is anti-virus software. As a test, you could try to white-list the game’s executable in your anti-virus, or even the game’s folder. Or even temporarily disable it while starting the game the first time. Please see your anti-virus manual for how to do that.
Timed out while creating browser view
This is an error that seems to just happen occasionally, and not all the time. Please correct me if you are seeing otherwise. If this happens to you, please follow the instructions at the bottom of my previous post, to send dump files to customer support. These dumps will help us track down the cause of your issue.
Timed out while creating browser context
The most common cause of this seems to be anti-virus software blocking the executable we use to display both the launcher and the black lion trading post. Note that this does not necessarily mean the anti-virus thinks it has found a virus, but it is somehow preventing the communication between the two processes. This is a known issue, and we are working to ensure it doesn’t happen. The only short-term solution is to white-list the executable in your anti-virus. As for how to do that, you will have to refer to the documentation of whatever anti-virus solution you may be using. To find the executable you need to white-list:
1. Navigate to the Guild Wars 2 folder (usually “C:\Program Files\Guild Wars 2”).
2. In this folder, find the folder named “bin” and navigate into it.
3. In this folder, you should find a file named “CoherentUI_Host.exe”. That is the file you should white-list.
4. You may also have to white-list “CoherentUI.dll” in the same folder, depending on your anti-virus. This doesn’t appear to be necessary for most cases however.
As per the previous crash, we would very much like to see dumps from this crash. Especially so if white-listing the process does not help. Please refer to the instructions at the bottom of my previous post.
m_system != NULL
The details for this crash is pretty much identical to the previous one. Please see the crash above.