World of Warcraft executable running, but doesn't open

I recently returned to World of Warcraft again, and I’m having an odd issue; the game itself after the first day back requires a constant directory deletion before every launch, or it never fully opens.

As per an article I found, listed here: https:// us. battle. net/ support/en/article/34719, I need to delete the ProgramData\Battle.net\ folder before every launch and then run the executable directly or the .EXE file sits in Task Manager as a sub-process of the launcher (as opposed to becoming its’ own process as per normal) with barely any resource usage and it never actually opens unless I do what that article states (I have left it running for around 30 minutes and it remains this way). Running the executable directly as some other troubleshooting articles have suggested makes no difference and it still occurs.

Screen cap of problem occurring: https:// postimg. cc/PCprNXLP

Once this situationally lengthy process - anywhere from 5 to 15 minutes while the launcher “remembers” the game is installed and does what appears to be a very slow fake update (no actual download or patching) - is done, the game runs fine.

Is there a way to stop this from being necessary every time? I would really appreciate some help with this problem.

(Sorry for the URL spaces; apparently I can’t link things.)

Hey DocPaulie,

This kind of partial-launch issue is usually caused by other software that is conflicting with the game preventing it from running. It’s often caused by anti-virus software that may not be fully updated or configured to allow WoW or Battle.net Agent to run properly. Deleting the folders causes those folders and files to be rebuilt which can clear the issue temporarily.

Here are some things you can try that may help get the game launching properly every time:

Troubleshooting Security Applications

Closing Background Applications

(Updated May 12, 2023)

Initially, it appeared a VPN was the issue. Allowing ‘bnetlauncher.exe’, ‘wow.exe’, and ‘World of Warcraft Launcher.exe’ access thru split tunneling seems to have rectified the problem - or so it did for 2 days. The problem is now back.

Nothing has changed since I added those three .EXE files to the VPN’s split tunneling; but once again World of Warcraft will just sit as a subprocess of the Battle.Net process, with little to no CPU usage (save a burst once an attempted opening occurs), and a ton of disk usage.

Might you please have some other advice?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.