Blue Tracker
World of Warcraft Blue Posts
Diablo II: Resurrected Blue Posts
Diablo III Blue Posts
Hearthstone Blue Posts
Overwatch Blue Posts
Heroes of the Storm Blue Posts
Diablo IV Blue Posts
BlizzCon Blue Posts
Warcraft Rumble Blue Posts

Ticket continually being marked as Duplicate (Patcher Hard lock)

Forum Avatar
Eldon.6591
#1 - Oct. 31, 2012, 2:14 p.m.
Blizzard Post

I’ve been having odd issues with the new launcher since Beta. The launcher will hard lock my computer. I can normally get into the game, as the hard lock happens randomly, and I will often be into the game before it occurs. I have to use the -nopatchUI option for large patches though. The old launcher didn’t have this problem, and it never occurs if patcher UI isn’t up.

I made a ticket about this some time ago. Ticket 121002-000538. This ticket was closed. I recently made a new ticket about it (since I am unable to add to or modify the old ticket), New ticket is 121031-002067. The new ticket has been marked as a duplicate ticket twice. Now, while it IS technically a duplicate, how should I go about getting this issue worked on?

Forum Avatar
Gaile Gray
#5 - Nov. 1, 2012, 2:39 p.m.
Blizzard Post
Eldon.6591:

Just wanted to update this. The root cause of my ticket being marked as a duplicate was a ticket I had on a unrelated issue. I totally understand the desire to work one issue at a time. That being said, I would like to give support a well deserved Kudos.

It can be really difficult working support for a game like this. I see lots of venom being tossed at them. While we all get frustrated (myself included) it quickly becomes obvious that they are working quite hard to resolve things as fast as possible. I created a ticket this morning, and they were able to get me back into the game in time to get my Halloween achievements. I work with computers every day, and offer complicated support to people on all manner of issues, and they were still able to have me try something I had not thought of.

While I’m still having the launcher issues, I’m sure that it’s some oddity with my machine and the way GW2 works. As such, I can’t blame them, and I’m sure that support will assist me as best as they can with the massive workload and time constraints that they have. For that, even if this issue never is fully resolved, I thank them.

It’s really kind of you to post this. I will share it with the team — your understanding and patience are greatly appreciated!