Chief.3867

In my case, it's due to arcdps. If the dll is still in the game folder, the game doesn't terminate correctly (it needs to re-launch during updates so it's common then). Since I still want to use arcdps regardless, I'm ending the game from Task Manager>Details (not Processes) whenever the issue arises and reopening it.

Instead of the Task Manager>Processes page, I resolved by by finding and force closing the game from Task Manager > Details (find Gw2-64.exe and End Task).The process does not appear in the Task Manager > Processes page; closing gw2 processes from there don't seem to completely terminate the game. https://imgur.com/a/bMIEpQI I'm consistently able to repro the issue when exiting the game, I think the recent patch may have introduced a bug in the games exit process and it is leaving some orphaned process. If using gw2launchbuddy that needs to close and reopen the game I also consistently get this. So to use gw2launchbuddy, open the taskmanager > details, and keep closing the process after update completes till it launches successfully (otherwise it'll hang waiting)

As a casual, that mostly logs in for a few hours of WvW zerging on scourge, having it deleted from meta is a good incentive to try out other classes I think. But also a good push for me to give the game a bit of a rest.