Patch download failure.

#3 - April 30, 2013, 3:20 p.m.

Hi Kopipoki – Do you happen to have any security software currently enabled? This is generally the main cause for patch/installation issues.

#21 - April 30, 2013, 4:36 p.m.

For any of you still experiencing this issue, I would recommend creating a technical support ticket so that we can further investigate this issue. The thread below should detail how to do so:
https://forum-en.guildwars2.com/forum/support/tech/How-to-Submit-a-Technical-Support-Ticket-2/first#post3957

#37 - April 30, 2013, 8:18 p.m.

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!

#45 - May 1, 2013, 3:01 p.m.

Hey everyone. Thank you for following up! For those of you who are continuing to be affected by this issue, you can help us by following the steps below.

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!

#49 - May 2, 2013, 12:29 p.m.

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!

#51 - May 3, 2013, 11:43 a.m.

Kyllaa.1385:

Will this also work for the Mac peeps who were also experiencing this issue?

If it does not, please submit a ticket to the customer support team at https://en.support.guildwars2.com/, including a -log file, if possible.

#62 - May 7, 2013, 1:19 p.m.

MrFayth.3546:

Same exact problem has Gabriel and Wreckreator, "Connection error(s) detected. Retrying” on the 8th remaining file.
Never had a “Connection Error” problem with the launcher before the April 30th update,during that patch i had many “Connection Error” messages appear but it always “reconnected” after a few minutes..this 8th file(of yesterdays patch) is somewhat more stubborn.
I let it sit over night “Reconnecting” and when i woke up it still had the "Connection error(s) detected. Retrying” message,so i restarted the client and its STILL on that 8th file!

Whatever you did to the launcher on the 30th please un-do it!

Hey MrFayth. Thank you for submitting a -log file for review! I’ve been asked to confirm that you did leave the client open for at least 10 minutes (uninterrupted) while trying to download the file. If you would be so kind, could you run the game with the -log flag for at least 10 minutes, then provide us with the new file so we can take another look at the information it provides?

Thanks again!

#66 - May 8, 2013, 1:33 p.m.

Thanks for bearing with us, everyone, and for providing additional information to help the programming team as they work to address the issue. To those who have not already generated a -log file, please take the time to do so and attach it to your post (as this may help to verify the source of the issue, or highlight a separate problem that needs to be investigated).

To everyone experiencing this issue, we would appreciate it if you also took the time to generate and provide us with the following information:

• Network diagnostics, such as those provided from this site: http://measurementlab.net/run-ndt. Once you have obtained this information, please copy/paste this information into a Notepad document or directly into the body of your post. Please be sure to include all of the data, including the ‘details’ and ‘advanced’ output from the tool.
• Your machine specifications. You can gather this information by running the ‘dxdiag’ command, or can append your client shortcut’s target line with the -diag flag (as you did with -log). The -diag command may take a few minutes to complete, but will generate a comprehensive file to send our way.
• A screenshot of the download hang: we would like to see what you see when you get stuck.

These documents will help us immensely as we work towards a fix. Thank you, again, for your patience, and for helping provide this information.