Game Client Won't Launch

Support Mac Technical Support
1

Im guessing this is because of the maintenance… but the client won’t even launch…

Was fine yesterday.

Usually during maintenance the client will launch it will just say all realms are down or some such issue…

Right now it just crashes and throws this.

73DAB1B9-982C-4549-B220-9E3ADA26E0AC

11 Likes
2

Same problem here.
Under Sequoia 15.0.1 with m2 max.
Tried scan and repair, tried removing WTF, Interfaces, Cache, Errors directories, no lucks.
ID would be: B8A92B49-E748-44F1-9D9C-E77597DF2538

3

Same issue.

M3 Macbook Pro running Sonoma 14.6.1.

Error: 47353565-2DB9-47C8-B511-25337E02C786

4

It’s bad enough that the Mac bnet client has been broken for months (toggle button state is apparently too much for them to deal with), but yeah.

I don’t know what I expected.

This is a really good time to back up your WTF folder. Just in case.

5

macOS up to date; battlenet up to date; scan and repair done; – still crashing. Anyone have any fixes yet?

6

Same issue here 17958081-5644-416E-B1FD-43CC3FBF8161

M1 Max Mac Studio

7

Works fine for me when i start up on M3 Max running macOS 15.1 beta.

I wonder if it’s specific to 15.0 or 14.x? or just specific macs?

8

Crashed when running on 15.0.1

9

Tried updating to macOS Developer Beta Sequioa 15.1 on my machine and still crashing.

Error: E887E7FD-EA93-4C24-BE4E-7B7F893C95BA

10

Delete and reinstall has worked for me.

2 Likes
11

Same issue. I’m on 13.0.1.

12

I fixed the issue on my machine; if you have custom Fonts loaded in the Fonts folder, trying deleting that folder and running WoW again.

That solved the problem of the WoW client crashing for me.

13 Likes
13

Same issue.
Scan and repairing, hope it will work.

14

The font thing worked for me.

1 Like
15

I just backed up my WTF and Addons folders - deleted reinstalled - started game - exited replaced folders - good as new.

UPDATE: I just went to override fonts using custom .ttf files in a Fonts folder hack and it made the client fail to launch… Deleted them and it launched fine… So it was indeed the custom fonts causing the issue.

8 Likes
16

I am on an M1 Max chip based Mac Book Pro (iow, laptop) running Sonoma, and it was refusing to launch even as far as cinematic or the warband screen. Immediately spewed the crash reporter app.

I just tried the suggestion to destroy the fonts and it actually launched!

Currently, 'tis noisy as heck because I also moved the WTF dir. I’m about to attempt the experiment of putting my interface and WTF back on. Wish me luck.

17

I felt it worthy to mention that this went well. I have not yet dared reintroduce any SharedMedia that contains fonts with its textures or sound sets.

Maybe next reset.

18

Same issue

19

Custom fonts is definitely the issue. It’s still a problem. Will continue to try reimplementing fonts and report back if/when it starts working again.

2 Likes
20

Definitely, the custom fonts in the Fonts folder. I deleted it and it worked right away!