Guild Wars 2

I logged onto gw2 the other night and it was fine, now I log in today and am greeted with an archive repair yet again!, this started happening not long ago as well but seemed to resolve itself, so it does the repair then I get a error and it crashes and now im stuck with it wanting to download then entire client again?, seriously what the hell is going on with this client, all my other games are fine, im on a monthly data cap with my isp, not all of us have unlimited broadband, I cant be redownloading clients all the time cause they decide to bug the kitten out…. needless to say, I wont be redownloading it.

Others aren’t reporting this. Maybe you have corrupted files and need to do a client repair.

If the GW2.DAT file is sitting on a bad sector of your HD (it’s 21GB, so not impossible), you can have this issue.

Note that repairing the client does NOT download the entire file….just what the server finds is corrupted. You can manually run a reapir (but you might want to do a disk scan first).

Look for the -repair option here: http://wiki.guildwars2.com/wiki/Command_line_arguments

Per above, this is NOT a generic issue as THOUSANDS would be reporting this if it was.

Brother Grimm.5176:

If the GW2.DAT file is sitting on a bad sector of your HD (it’s 21GB, so not impossible), you can have this issue.

Note that repairing the client does NOT download the entire file….just what the server finds is corrupted. You can manually run a reapir (but you might want to do a disk scan first).

Look for the -repair option here: http://wiki.guildwars2.com/wiki/Command_line_arguments

Per above, this is NOT a generic issue as THOUSANDS would be reporting this if it was.

I have seen other threads with this issue, I had checked my disk but I will do so again and yes it at first did a quick download then I went to run the client and it crashed out then when I tried again it started downloading the entire client, I will check the disc again just in case.

Did a drive check everything is 100% fine throws arms up in air never the less I salvaged an older version of the .dat file and did a .dat implant on my mortally wounded client, after a short update it is now working fine again, I also copied the new .dat file incase this happens again