Especially went it amounts to “you must be morons, so we’re gonna tell you to try everything you’ve already tried, and do other stuff that is completely unrelated to the problem.”
I’ll admit to solving some problems with FM (freakin’ magic) during my TSA days, but it was because I was doing everything I could - where the customer could see me - & not sure which of the umpteen legitimate things I did actually fixed the problem, not because I was asking the customer to run around in circles.
response to my reply - which i did to keep the ticket active.
Epinexet
Hey there,I’m afraid as we mentioned previously, this issue is one that has already been reported, and is not something we currently have a workaround for. The tips we mentioned are things that can help in a few cases while the root issue is investigated, but the main problem affecting opening multiple World of Warcraft clients on Mac systems is one that will have to be fixed by the developers or Apple ina future update.
I double checked, and we already added your system information to our investigation for this trouble, however if you do want to track for any updates as we have them, there is a forum post here: Can’t open multiple clients on mac after prepatch
Please note as Customer support, sometimes the only answer we can give for an issue is that we are aware it is happening and that the Devs are looking into the root cause, as Customer support have no direct access to th e developers nor can we change the game, and the best we can do sometimes is just collecting data to send to the devs and QA team to look into replicating and correcting the issue in a future update.
In the meantime, we have seen a few reports that resetting the NVRAM on macs can help get multiple clients working as a temporary measure until Apple and the WoW dev team can track down the root issue and get it fixed up
https://us.forums.blizzard.com/en/wow/t/can%E2%80%99t-open-multiple-clients-on-mac-after-prepatch/682221/22 // https://support.apple.com/en-us/HT204063Hopefully though in the long run the devs and Apple can track down the main issue, and get that corrected in a future update so those kind of workarounds aren’t necessary!
i find it quite humorous that I’m told to look for updates in this thread right here. I get it that the CS people are often as much in the dark as we are when it comes to what the techs are doing. OTOH it tells me that the one who responded to my ticket is not reading the thread very carefully.
It’s also very telling that they refer to a QA team rather than QC. Quality Assurance is what you do before a product is released. Quality Control is dealing with product defects after the customer complains. The difference between beta testing & patches, if you will. That the ticket response is mentioning QA might mean that the CS rep is confused, or that our tickets aren’t being properly directed, or that Blizzard has the same people doing both QA & QC, … ???
“in the long run” confirms that part of my “temporary measure” ought to be transferring a couple of characters, getting refunds, and deactivating accounts.
Well, at least we are looking in the right place.
Things I tried that did NOT work:
They are aware of the issue. You play the game in a manner that it wasn’t really intended to. As such, you are much further down on the “fix” list than those issues affecting gameplay on a single client only.
Remember also that most Mac applications aren’t designed to be run in multiple instances either, so you’re really outside the box by trying to do so to begin with.
The issue will likely get fixed in time, just not now, probably not before SL launches… like many other things that don’t get fixed prior to launch.
Macs can run Windows in bootcamp. If you are that desperate to multi box this instant, perhaps running WoW under Windows is your best option.
Pulling your hair out trying to reboot, reinstall, reset, and twirl around isn’t getting you anywhere. Pretty sure the fix can ONLY be done on their end, so you’re more likely to break your setup trying to fix something you can’t fix.
@Oatmeal - kick rocks. In the politest sense possible. You’re obviously an outsider looking in. Your comments are patronizing and uninformed.
Thank you for trying, I can see how they could be potential workarounds. I first also thought it could be because of the new mac OS update that was causing the issue, so I restored a time machine backup from last month when the wow clients had still worked perfectly fine, and the issue still persisted. That shows that the problem lies in the new shadowlands client’s coding, and not from apple’s updates.
If it hadn’t been intended to, they would have banned or hot fixed it out already. As long as we don’t violate any ToS, then it is perfectly within the intended design to play the game however we find it fun. If anything we should be treated as valued customers because we pay double, triple, quadruple the amount of money others pay for the game, hence we have every right to demand an escalated fix for an issue that is directly hindering our financial investments and enjoyment of the game (compared to other in-game issues that are merely causing gameplay inconvenience).
I’m definitely new to the forums and have, over the years, sent in a dozen or so tickets. I don’t understand why my tech tickets (including sys specs and trace route) end up with people who say
“…Customer Support is not really able to do much else here sense this is a bug.”
If I send it to tech and such???
I must be doing it wrong.
I never said it was against ToS, I said you played in a way that was never intended… which is true, they never wrote the game specifically with multi-boxing in mind… if they did, you wouldn’t need a third-party assist to make it even possible in game. They aren’t stopping you. I’m not stopping you. I’m merely SUGGESTING that switching to the Windows side for the time being might be a solution to the problem in the near term. Get a grip.
You’re submitting the tickets correctly. We never get to talk to the people actually doing the work. The people assigned to reply to us are not techs, unfortunately. They’re the CS people assigned to the tech support department, while our submitted reports are forwarded to the actual techs for the actual work. It sounds a bit kafkaesque I know. But think of it like this - do you really want the people working elbows-deep on the problem to stop every time one of us bugs them?
I had the same issue on my Mac. I have 3 accounts, could only run 2, 3rd would hang.
This is what I did, and works for me - USE AT YOUR OWN RISK!
Running 10.14.6 with all updates. I launched activity monitor and launched 3 copies of the client from the Battle.net app.
Clicked “info” in the activity monitor for each of the 3 WoW clients. 2 running, 1 was “Not responding”. Once the info windows are open go to “Open Files and ports”. Compared the running to the non-running. The non-running always hung at line 127:
/private/var/folders/ts/l320s_yj3mx03_ww5gdjcv_00000gp/T/WoW ASYNCTHREADSHAREDMEM.1.mutex
This is the temp directory in Mac OS (from terminal type “open $TMPDIR”). I’m guessing it is different for each machine/user??
I went to that directory, and saw 4 recent files, all zero bytes in size:
WoW ASYNCTHREADSHAREDMEM.1.ex
WoW ASYNCTHREADSHAREDMEM.1.mutex
BlizzServiceRegistry.ex
BlizzServiceRegistry.mutex
So what I do is this:
So far this has worked 100% for me. I have not noticed any ill effects.
If you do choose to try this, let me know if it works for you. Also, if you check Activity monitor, I would be curious if it hangs at line 127, on that same file, for you as well.
This worked exactly as you said.
I did not let it crash to see if it was line 127 but I presume it was.
Others trying this… That terminal command isn’t to be feared.
It will open a good ol’ familiar finder window. Delete the files he mentioned.
This narrows the possible causes down vastly. What an amazing discovery.
Thank you.
Also, Blizzard thanks you for preventing people from canceling accounts and all that.
Great job Bheleu. I was able to follow your instructions and successfully opened up to 5 clients on my mac. Although you don’t have to log into the character in order to delete those files, deleting them while at the character selection screen also works.
PS: Blizzard should pay you for this, because your one comment is more helpful than all of those GM’s responses combined.
What is “a third party assist”?
Just tried opening my second account and this is the last line in activity monitor “open files and ports” for me:
134
/private/var/folders/7h/j4w8kstj6_1fg7pm0lpx6t2w0000gn/T/WoW ASYNCTHREADSHAREDMEM.1.mutex
So not line 127, however it is that same temporary file. Deleting the suggested files allows me to launch my second account.
Thanks for the find, Bheleu! 
Also as a note, I have NOT tried the other temporary solutions in the thread such as the “reopen windows on restart” or PRAM/NVRAM reset. So this “delete temp file” solution works WITHOUT having done anything else.
I have no idea why there’s a big green checkmark/“solution” for Bheleu’s hack. I agree it’s a very clever hack and kudos to Bheleu for figuring it out. It’s still a kludge, not a solution. A seven step process involving typing commands in the terminal & trashing files is not a solution that should be checked off like that. Liked - definitely. But please don’t let anybody at Blizz think they need do nothing further.
100% in agreement.
I just want to make it clear that I’m definitely happy Bheleu has been putting so much effort into coping with our situation. I’m in favor of his and others efforts. I was only saying that - if anything - his hack makes it obvious that the problem is not on our end.
Yeah, Bheleu has saved the situation! When I read his post, I was amazed. I figured it was some something with some file somewhere. I had no idea how to figure out where or what.
I also agree that it serves to shine a light on the cause. I’m confident the developers know right where to look.
Thanks for all the kind words. My motivation was that I have gotten used to running my own 3-man team (ok, 2 orcs and a troll). I just really wanted to play! But I agree, it does need a fix. It is a hassle to delete those files each time.
I’ll gladly take a long boi in lieu of money!
I completely understand. When I couldn’t play my groups of 3, I felt like something was off. I’d imagine you get it.
I have a hunter, a priest, and a DK in a team. I felt like I was cheating the DK when I ran without her. The other two need gear, so I ran them. Last couple days, has “felt” right once more.
I honestly am a little surprised by how attached I am to the groups of three. shrug