Guild Wars 2

I am unable to start the Gw2.exe process. Upon launching, it hangs on the initial update screen with "0 KB (0 KB/S) at the bottom left (this is before the login screen appears). The client just stays there until closed.

When I try to kill the process, it cannot be done. Task Manager returns an error of “Access Denied”. I don’t see how this can happen since I am the administrator on the PC, and have set the Gw2.exe client to run as administrator. Even the Command Prompt (Admin) is unable to kill the process using the Taskkill command.

I tried running the diagnostic version of the file (-diag) but it got hung up on the “Discovering External Address” phase for over 10 minutes until I rebooted.

The biggest problem I’m finding is that every time I reboot, there a 6 Gw2.exe clients running in the background at startup. I don’t know how these processes are even starting in the first place and why I don’t have permission to clear them.

I am currently running Windows 8 and have been running the game trouble free until January 28th when this started happening.

Any help would be greatly appreciated! Thank you.

Additional Update:

I am now unable to even delete the Gw2.exe file from the game folder in Program Files. I get a windows message saying that the file cannot be deleted because it’s in use.

I figure that this is by one of the 6 processes running in the task manager, but how am I supposed to get rid of them if even if a hard reboot is unable to clear them?

Update: Problem Solved!

The culprit in this case was a combination of the Guild Wars 2 client and Windows 8…

Windows 8 has a “feature” called Hybrid startup, where the standard system shutdown turns off all user processes, but leaves system processes running in the kernel. Problem is, when the Gw2 client crashed, it got stuck in the kernel which doesn’t allow any access to disable files.

The solution was to create a manual shortcut to the windows shutdown with the following path extensions:

C:\Windows\System32\shutdown.exe /s /t 0

The 0 in this case is the kernel (where 1 would be the user). This caused a standard full shutdown which cleared out the processes stuck in the kernel.

The launcher is up and running now and I’m able to play again

I hope this ends up helping somebody.