When a frozen client update isn't a frozen client update

[Walsingham]

Good evening!

Having toyed on and off with this over some amount of time, I just recently gave it another shot on a newly Win7'd machine. All appears to be pretty positive in terms of progress save for the client update freezing at the same spot on multiple login attempts.

The client updater box reads "Version cannot be determined", and the New Version is "50". The path is standard default.

Progress of the patch goes fairly well up to the point where it wants to download m..... Wait! I need to change the title of this thread (so done).

It seems to be moving again. After what appeared to be a freeze of nearly 15 minutes!

I don't know if there are known "hitches" in the process of downloading/updating the client, but there are at least a pair of files that seem (at least on my system) to take a while to negotiate. I'm in what appears to be the second big hitch, a file for which the destination + name are too long to properly communicate (net7config.exe - 1,724,636/1995,77etc).

So, the question now has become "are the hitches in the client update known, or is it just me?" If this is at all an issue that the clarification can assist in the smoothing out process of delivering the app, great. If not, please do feel free to delete this thread (or command me to). Thanks!

[Slayerman]

Ive not heard of this happenin to anyone else...

Not sure what could be the issue I'm afraid. Does sound like something local as no one else is having the problem

[Walsingham]

Believe me, I can accept that! I do a fine job of sabotaging my own gaming experience.

Thanks for the observation. I'll try to work around it.