![]() EXEs have been given split tunneling access to my VPN (which one would think they should not require), and the AV / firewall are set to allow them free passage. Once in a while, the game will run instantly, as intended at most, 15 seconds pass before the character select screen is up - this indicates that it is not a hardware limitation, as it is fully capable of running properly although it rarely doesĪt no point has anything on this PC changed before, during this issue (including my previous now-closed post), or as I post this the three WoW-related. Least often, the game will fail to ever break off from being a sub-process of the launcher, repeating the above behavior of minimal CPU usage and high-ish disk usage, but never actually opens i have left this for as long as 2 full hours with no change, at which time I simply kill the sub-process (retrying after this always results in the previous situation) EXE is running (non-zombie / does not show “Not Responding”) within Task Manager, but it drops to less than 1% CPU usage with fairly high disk usage where it will sit for an unrealistic amount of time before finally breaking away from being a sub-process of the launcher to its’ own process as the window opens ![]() Most often, the game will take anywhere from 15 - 40 minutes to launch the. When clicking “Play” in Blizzard launcher, one of three things randomly happens: I had posted about this about a month ago, but it was closed without additional response or resolution so I am trying again.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |