I tried logging in a short while ago, forgetting about maintenance. WoW app loaded just fine, I saw the maintenance message, swapped to Battle.net app to start the download of 10.0.5.
Downloaded and installed successfully per Battle.net, however now when I attempt to launch the game (either from within the Battle.net app or from the app directly), it crashes. I briefly see the window of the app come on screen, but it’s all black. I can see the WoW curser, and then after a few seconds it hangs and then crashes.
This happens even after a system restart. I’ve run scan and repair through Battle.net, no faults were found, still same issue.
MBP 2018 (Touch Bar), eGPU running MacOS 10.15.7.
Error code from Blizzard Error Reporter app:
EB63137A-89C4-4228-346AA8C3C7A1
83 Likes
Same issue happening here. I realized shortly after that the servers were down anyways so hopefully this issue is related to that.
3 Likes
The 10.0.5 WoW app also crashes for me when launching. At first, I thought it might be that I’m still running an older OS (10.14 Mojave) but now I’m not so sure. I checked the latest log file in the Errors directory and saw that it crashed with “Exception: EXC_BAD_ACCESS” and “Description: KERN_PROTECTION_FAILURE at 0x000000010A645FF8”.
5 Likes
Same issue here, at least i know the problem is most likely with the update and not the laptop itself. Hopefully they fix this soon.
4 Likes
Following. Having the exact same issue. Using MacOS 10.15.7 as well.
8 Likes
Same here! Crash on start up - there is no error message. That code at the bottom of Blizzard Error app changes every time I try to start the WoW app.
Running same: macOS Catalina 10.15.7. Perhaps Blizzard forgot that they were still supporting us?
11 Likes
C146883C-1B22-448C-8DC9-351A0C23FCB0 . Version 10.0.5.47799. Maintenance process was 11 hrs. System still boots out of realm log in. This has been like this all day.
1 Like
I have the same issue on MacOS 12.6.3
5 Likes
I am also getting continual crashes after the latest patch install. It goes to a black screen with the familiar WoW pointing finger and then a pop-up box with the crash
I have a 2018 MB PRO i9, eGPU/RX580 32Gb Ram.
[update] MAC OS = Big Sur. I never upgrade if it isn’t broke…
7 Likes
yep! imac pro 1,1 on os 11.4
1 Like
Same here on 11.7.2 BigSur.
3 Likes
Having the same issue, crashes when I hit play.
Did a scan and repair, as well.
Error: FE0DB163-B6DF-4AC8-AA39-FC73059651C1
1 Like
Just got another Battlenet update, first since early afternoon, about 200 MB
And it still crashes.
Jan 24 17:15:18 Sambas-iMac Battle.net[1982]: objc[1982]: Class BlizzardCore_URLCache is implemented in both /Applications/Battle.net.app/Contents/MacOS/Battle.net (0x100f89438) and /Users/samba/Library/Application Support/Battle.net/Versions/Battle.net.13894/battle.net-core.framework/battle.net-core (0x1066f7010). One of the two will be used. Which one is undefined.
Jan 24 17:15:18 Sambas-iMac Battle.net[1982]: objc[1982]: Class BlizzardCore_DownloadURLObject is implemented in both /Applications/Battle.net.app/Contents/MacOS/Battle.net (0x100f894b0) and /Users/samba/Library/Application Support/Battle.net/Versions/Battle.net.13894/battle.net-core.framework/battle.net-core (0x1066f7088). One of the two will be used. Which one is undefined.
Jan 24 17:15:18 Sambas-iMac Battle.net[1982]: objc[1982]: Class BlizzardCoreURLConnectionDelegate is implemented in both /Applications/Battle.net.app/Contents/MacOS/Battle.net (0x100f894d8) and /Users/samba/Library/Application Support/Battle.net/Versions/Battle.net.13894/battle.net-core.framework/battle.net-core (0x1066f70b0). One of the two will be used. Which one is undefined.
Jan 24 17:15:20 Sambas-iMac VTDecoderXPCService[1987]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Jan 24 17:15:20 Sambas-iMac VTDecoderXPCService[1987]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug
Jan 24 17:15:21 Sambas-iMac com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.mdmclient.1993): Failed to bootstrap path: path = /usr/libexec/mdmclient, error = 108: Invalid path
Jan 24 17:16:07 Sambas-iMac com.apple.xpc.launchd[1] (com.blizzard.worldofwarcraft.24984.EFDD6131-90BF-453F-80D3-34D3D77AC0E0[1998]): Service exited with abnormal code: 1
Jan 24 17:16:08 Sambas-iMac com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.system_profiler.2006): Failed to bootstrap path: path = /usr/sbin/system_profiler, error = 2: No such file or directory
1 Like
Same issue. Also on a Mac.
4 Likes
Same: app boots, black screen with the hand pointer showing for couple seconds, crash. I’m on 12.6.1 Monterey. Repairing didn’t solve it, nor did restarting the whole system.
7 Likes
I opened a Support Ticket with this issue. Frustrating that there is not actual error code to give, that long number string is not an error code - it changed every time the crash occurs.
4 Likes
Get the character select screen hit play- fatal crash
3 Likes
I havent even gotten as far as the character select screen, just immediately a black screen and an ‘unexpected error’ 
13 Likes
Nonstop crashing on loadup, same with my friend – mac problems.
5 Likes