MacOS Client crashes on startup

Support Technical Support
1

The game keeps crashing on startup on my 2013 Mac Pro (12.6.1).
Anyone else having the same problem?

1 Like
2

Same issue here - also on a 2013 Mac Pro (12.6.1)

Blizzard Error message says: “The application encountered an unexpected error.”

1 Like
3

It seems to be a problem with Intel Macs https://us.forums.blizzard.com/en/wow/t/wow-retail-crashes/1379257/26

1 Like
4

I’ve been having the same problem on my 2012 MacBook Pro, sad day for intel users

2 Likes
5

There seems to be a temporary solution on the US forums:

1 Like
6

That temporary solution really works!

1 Like
7

Since I tried a fresh install I didn’t have a WTF config.
Tried creating a new txt file with SET playIntroMovie “10” and save it as .wtf.
Still didn’t stop the crashes from happening on launch… Hoping for a hot fix soon.

1 Like
8

I had the same problem. This helped me:

9

Unfortunately this still let’s the game crash with a code as such: EFB9A7B5-0774-458C-9602-8052FAACB4CE. Though I’ve heard the codes are always different.
I thought I’d try my luck today but perhaps there’s not much else I can do than wait for a fix.

10

For all those still wandering around for a fix, I solved the issue on my Mac by downloading and launching WoW Classic, copying the WTF folder from Classic to Retail and there changing the WTF folder by adding the SET playIntroMovie “10” code.

11

I did a full install / wipe of macOS today → still the same issue;

I have a solution which will help some people with Macs (and quite likely PCs, and systems which are crashing early due to the issue playing the intro video);

I tried creating ‘config.wtf’ (due to a fresh install I lost my config.wtf) - with the video fix - it still didn’t work;

I went to ‘Finder’, ‘get info’ info for the config.wtf I made, and clicked ‘show file extension’.

→ I then renamed it from config.wtf.txt, to config.wtf - and it renamed properly!
→ but still, the crash on launch.
→ I then discovered that, when renaming ‘config.wtf.txt’ to ‘config.wtf’ … macOS keeps the name as ‘config.wtf.txt’, and reverses the ‘show extension’ attribute. “It just works” until it doesn’t!

Solution : Finder menubar → settings → advanced → tick “show all filename extensions”, then rename config.wtf.txt to config.wtf!

If making a new file in TextEdit, you also need to do (TextEdit menu) → Format → Make plain text before saving, so it is in the correct format.

The line I added was:

SET playIntroMovie “10”

from the US forums; it is worth checking the config.wtf file as there may be a "SET playIntroMovie “something other than 10” lower down, and that could also prevent the fix form working.

This should help any system that is having a crash in the intro video player, regardless of the cause; it isn’t because of an old system (I’m on 15" mid-2012 non-Retina, 650M 512MB, 16GB ram, Ventura); I saw another post where someone is running on a nVidia 9600GT, which is very impressive (and which means it is likely that ‘Boot Camp’ will be an option for older Macs once the Metal drivers are no longer good enough in macOS for Wow!

12

Same problem for me since pre-patch went live.
Tried the work around with the Config.wtf file, that didn’t work for me either. Time to request a refund! Maybe if they start having to give money back, this will get sorted out quicker!

1 Like
13

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