Patch Updater stuck 1 file. 0.00 kb/s

#1 - April 30, 2013, 1:07 p.m.
Blizzard Post

The title,

I tried relaunching it and it slowly drops from 1.00 kb/s to zero while making no progress. Leaving it will eventually cause it to error out and retry.

#18 - April 30, 2013, 8:16 p.m.
Blizzard Post

Hello everyone!

If you are currently unable to patch the final file, try restarting the client and allowing it to run for at least 10 minutes. At this point, the backup system should kick in and push the final file through to your system; if you receive the “Connection failure…retrying” message, don’t worry: this is the backup measure, and should download the last file after a few minutes.

If you continue to have trouble downloading the file, please contact support at https://en.support.guildwars2.com/.

Thank you for your patience!

#22 - May 1, 2013, 3 p.m.
Blizzard Post

Hey everyone. Thank you for following up!

First off, I would not recommend re-downloading the client just yet, as it is not likely to help the current situation unless there is a different problem preventing you from accessing the game. Instead, please try the following:

  1. Make sure you’ve created a shortcut to your Gw2.exe client.
  2. Open the shortcut properties (by right-clicking the icon and selecting ‘Properties’)
  3. In the target line, type -log so that your target looks something like this: C:\Games\Gw2\gw2.exe -log
  4. Hit ‘Ok,’ then run the client.
  5. (Assuming you are blocked when trying to download the last file) let the client run for about ten minutes, then close the client.
  6. In your Documents\Guild Wars 2 folder, you should now have a text file called ‘Gw2.log’. Please attach this file to a response, or send the file with a support ticket to customer support.

Please send us this information as soon as possible, as it will be of great aid to the programming team as they identify the root cause of the issue.

Thank you for your patience in the interim!

#26 - May 2, 2013, 12:29 p.m.
Blizzard Post

Hey everyone! I’m happy to say that the programming team was able to implement a fix for this issue with last night’s build (thank you Katody for providing us with your log information so quickly!).

If you have not already done so, take the time to re-launch your client and allow it to run for at least ten minutes. It should eventually return the “connection failure…retrying” message. At this point, let it sit for another few minutes as the backup mechanism kicks in and downloads the missing file.

If you are still unable to patch the final file after giving the client time to re-connect, please take the time to generate a -log file and either post it here or submit a ticket to support.

Thanks, again, for your patience, and good hunting!