Please help
1 Like
One of my raiders is suffering from this as well. We’ve tried:
Restarting the computer
Running Wow from the .exe
Restarting Battle.net
Logging out of and into Battle.net
Deleting the Battle.net Cache
Scan & Repair of Game Files
Ran the System File Checker
Full uninstall/reinstall of wow
None of the above assisted. Not sure what to suggest that he try next
Try to launch the game, then open the Task Manager to the Processes tab (it may be the default). Look in that list to see where the WoW executable is - if it’s under Background processes (the second section) then something is preventing it from launching properly, most probably at the driver level.
Unfortunately this is not an easy situation to resolve in my experience. When my system would occasionally do this I was able to track this behaviour back to a virtual input device - specifically the one provided by DS4Windows (a tool used to make a DS4 controller behave as an XInput device), which I could restart to momentarily correct it and later update to provide a more permanent solution. This was only possible through the log on a different program which showed the stall during startup, though it was so long ago now that I no longer recall which program it was.
Still, perhaps someone else may have another idea if this is what’s happening in these cases.
Troubleshooting is easier when DxDiags or MSInfos are provided. Pastebin.com is a good place to host them.
Just in case this helps the other player that was stuck on thus issue, the raider in my guild finally did get it fixed. An In-Place Upgrade of Windows 10 (See this support article - https://answers.microsoft.com/en-us/windows/forum/all/how-to-perform-an-in-place-upgrade-with-windows-10/7f0b236e-3c6c-4913-9691-c4baa2a6190a) fixed it for him.
This same issue happens for me.
I provided msinfo and dxdiags to blizzard customer support when I opened a ticket regarding this issue a couple days ago and their only response was for me to go seek assistance on the forums.
I can’t see anything you sent to CS. I don’t work at Blizz.
i was attempting to address a blue poster (someone who would have access to my customer support tickets)
Okay, well if you want more help, players in the forum would want to review those files. There are no staff members doing tech support here these days, just fellow players.
could this be related to the fact that i have not updated my windows 11 laptop to the 24H2 update?
I have two ASUS laptops, one with a 3080ti Nvidia and an intel processor, one with a 4090 nvidia and an AMD processor.
I had been mainly using the 3080ti laptop until I noticed there was significant and consistent screen tearing when using any browser (chrome, firefox, microsoft edge). I read that the 24H2 update is known to cause this.
So i switched to using my 4090 Laptop and i decided to not update to 24H2, even though it is showing in my system updates (and reminds me every day).
My 4090 laptop has no screen tearing (which is nice) but it has this problem with wow not launching right away after clicking play in BNET.
my 3080ti laptop still has the screen tearing but it does not have the problem with WoW not launching (my 3080ti laptop launches wow immediately once i press play on bnet)
Not sure why WoW is launching slower with the new card, it might be related to the driver for it.
As for the screen tearing, it sounds like the 3080ti had corrupted drivers or damage from overheating? If it was overheating, it would mean less resources available from the card. Then, using browsers with hardware acceleration can start to cause overall system problems because there aren’t enough resources available.
No, the screen tearing started the day I updated my 3080ti laptop to the windows 11 24H2 update. Worked perfectly fine before then (also there are threads on Microsoft’s official forums regarding screen tearing being caused by the 24H2 update).
A vast majority of companies no longer provide direct tech support. They have a guideline of typical troubleshooting guides but that’s about it.
You still haven’t provided any useful data for anyone to look at. No one here can see what you sent in via tickets. You’ll want to copy paste that here.
Though outright refuting possibilities without providing any evidence to support one way or another isn’t going to help anyone help you troubleshoot.
2 Likes
In case you haven’t read my previous posts, I already figured out the issue on my own.
I don’t need help troubleshooting.
Technically you can post on the main support channels, cs, ts and mac, without a subscription. Also new players. You are correct that it’s public and anyone can read.
Personally I don’t believe dx diagnose msinfo contains enough personal information, maybe a computer name that can be redacted. But since you seem to have figured out the issue, hopefully if others have the same concern they can get enough information to help them to.
Most gaming studios only have one or two pages of troubleshooting tips and do not have any sort of ticket system for one-on-one assistance. Blizzard’s methods are now in line with their competitors.
Microsoft has not moved into the game development teams for Blizzard games and hasn’t announced any plans to do so. One company can own another without changing their development processes.
If you have a bunch of sketchy apps installed, or you’re cheating, I could understand that. But your username and PC name are easy to remove. DxDiags were required in all new tech support posts for the last decade, but the sticky expired when blues stopped babysitting this forum.
The blame on the Windows update is an interesting move since we’re not being flooded with reports remotely similar to that situation.
1 Like
Well not all PCs were eligible for the update.
Only the higher end PCs were eligible for that update.
Yep, and I have both cards you mentioned in use in my household.
That didn’t need repeating. What we’re all confused about is why you made this post if you don’t want help from the community. There are no “other” staff here that are gonna pull up your system files and review them with you. As far as I know, they no longer even read those via the ticket system. I’m curious if they requested them.
But you asked me a question. Oh well, I guess you really set us volunteers straight that were trying to help you. We’re all very impressed. 
2 Likes
i never actually asked you a question. I clarified that in this post below:
Lol, I knew you’d be back.
You edited your post to remove the question. However, I already quoted the original post text above:
Anyway, you can have the last word after this if you truly need it. Happy New Year.