Weighing in on this
- Up to date drivers (Unlikely this is an issue)
- tried forcing dx11 in launch arguments (didn’t work)
The only thing that works for me is letting scan and repair get above 10%, cancelling and clicking play
The other threads that they have closed .they have said that they acknowledge the problem and are aware .
aware after 2 days?..
Hello. To help us keep track of the various solutions shared so far and ensure the discussion stays in one place, please continue the conversation in the Technical Support forum by replying in this thread (Game not launching). Rest assured that this issue is not being ignored. Thank you!
And it’s back… game’s not launching today for me.
Yday it was okay, today nope.
Funny, it was just as I decided to pick it up again and focus on my rogue :')
1 Like
What works for me is to launch the PTR client first, which launches just fine. Then close it and launch the Live client.
As I think has already been mentioned, I click play, go away for 10 mins for a cuppa, come back and the game is running.
Not ideal but just launch it once then leave it for a bit
2 Likes
Not played in a few days.
Just tried after weekly reset and game will not launch.
Pretty much this, right now… feels like loading a game back in the 90s…
300+ comments and a serious issue in the game and still no reply from blizzard…
i got the same issue i had yesterday when i made a comment here.
when will you fix this?
1 Like
Same boat here. Killing running process and scan/repairing took a bit but worked for the moment… short of an actual fix on their end, I’m afraid it’ll be only temporary. They acknowledged the issue, it’s a start I suppose
Day two of same issue…
Same here for 2 days. Task Manager force quitting the apps especially Blizz updater then trying again helps sometimes, but not always.
Problem is back again. Was working fine since last, see the thread that was closed and forced into here, and now the problem is back.
Guess something scuffed is going on.
Same problem here 
PARTIAL SOLUTION: Immediately on launch start scan and repair. When completing that process the game logs in. Don’t wait to launch scan and repair as background processes like Blizz Updater kick in and grey it out.
If scan and repair is greyed out task manager into force quitting Blizz updater; alternatively into quitting all blizz apps then relaunching. You may have to play whack a mole a bit to get scan and repair to be available. A computer restart may help.
1 Like
No offence but your post seems needlessly convoluted.
I think it would be much clearer and easier to understand if you just said something like “the game works after doing a Scan and Repair, but Scan and Repair may be greyed out if you have already hit the Play button, in which case you will need to close all WoW instances in Task Manager processes first”.
Also, I found that changing to Direct X 11 worked. To do this, open the Bnet app, select World of Warcraft, go to Options (gear icon to the right of Play button!), then Game Settings, find WoW, check the box for “Additional command line arguments” and enter “-d3d11” in the new text box. Click Done to save the changes. This solution seems a lot better as Scan and Repair took a long time.
So i had same issue with game would wait 15 minutes to start… But in nutshell i fix it… Since i’m still on Win10 There was Win 10 update stuck so i had to unstuck it download it and install it . After wards i restarted pc and all worked perfectly…
If you are having same issue check Win update first … If you don’t have update on stand by refresh and check if is gonna pop
It was a problem yesterday morning on my M4 Pro Mac mini yesterday too (not just Windows systems). 48 GB, macOS Sequoia 15.5.
Started a scan and repair, aborted it after 10 minutes, rebooted the computer, still no joy, rebooted again, and it worked.
Had the problem occur just now.
This is usually caused by a bad / slow response from Blizzard backend servers, as well as bad programming decisions that mean the client does not launch and appears unresponsive until it has downloaded this data.
If the menu UI launched and the client said something like “contacting Battle.net servers” it would make it obvious to users that something is happening and what the delay is. The client not launching into the menu is bad programming and poor attention to user experience.
Servers erroring in responses is a combination of bad infrastructure management, and also again bad programming because the client should be screaming to be allocated to a different backend server if the response is far too slow, erroring, or otherwise failing.
I have seen it take many minutes before it eventually shunts onto a different server, when it should be doing this after 10-20 seconds.
The operations team should be monitoring error responses and immediately be taking failed servers out of the production pool or otherwise taking corrective action.
The programmers of the game client should not hang the client waiting for it to complete an invisible task while not informing the user what is going on.
4 Likes