"Crashes?" Yes. "Unplayable?" Yes. Sincerely, Mac user

Support Technical Support
1

Dear Blizzard, hear our plea!

As you surely know, the game crashes consistently and constantly for many of your Mac-users following the pre-patch. Even though Sonoma has done some, it is your update that is creating a serious conflict between our computers and your/our game. Whether a graphics issue, a memory issue, something related to the wonky UI update, or anything else, this is an issue that is in your hands to fix as it affects both Silicon and non-Silicon Macs alike.

It comes as no real surprise that playing the game on a Mac after the pre-patch of a new expansion is done at one’s own risk. Not only does it stress-test one’s patience and persistence just to get a few minutes of somewhat normal gameplay before facing bugs and crashes, it also forces us to rethink our financial choices of choosing to pay for a game that time and time again delivers absolutely unplayable weeks when all we want is to experience the liminal atmosphere and content between two expansions. In our current day we all know technology to generally work as it should, and we know Blizzard generally provides seamless gameplay.

HOWEVER!

It feels utterly absurd, bordering to being violated, to have the game be patched — which has surely been tested in and out on various platforms — only to find it not only unplayable, but actually disintegrating further following each minor maintenance or fix! Where the violation spikes further is when these clearly Blizzard-caused issues are not acknowledged clearly. We are paying for this game, many of us have done so for nearly two decades, yet dropping us some lines of actual assurance in the fora seems to be above your current level of customer support. A simple “we know, we see the issue, and we will fix it” or “this sucks, here’s how we’re approaching it, we will not let you down much longer” would do, though I have yet to see this kind of engagement from you anywhere. Give us a timeline, even just an estimate, and we’ll even be grateful (sound abusive at all?)! Here on the EU forums us Mac-users, whom Blizzard have generally treated quite well ever since the inception of Mac OS, don’t even have our own technical page as the US one does.

The chonky warband screen that met us when we logged in was curious, but surely resizable. Nope. When we’re not already clicking us through the “Your computer restarted because of a problem” after a sudden and intense wind-down of our computers, as if it just took an arrow to its electronic lung, we may be able to click us through to the loading screen. The chances of reaching the blue bar of progress, and promise of impending joy, is increased if the character you’re logging onto is not from your warband screen. Generally, once the bar has been filled and the background music eventually comes to a halt, another void-filled arrow pierces our computers and we’re back to Apples power logo with the equally annoying two sentences delivered in six languages on top. Once in a while we’re able to get all the way into the game, and the frequency of this I assume is affected by the freshness of the organs of our Raskin/Jobs-machines.

Stuttering and sudden freezes, with the always looming doom crash, ensues. Never far away, these crashes, but the hope that this time, just this time, I’ll be lucky to get some playtime. Is it the zone that I am in? Nope. Is it the character I logged onto? Not that either. Maybe if I tweak the graphic settings a little? False hope. No matter how many times the graphics are tweaked according to advice from the various fora, even though these might result in slivers of somewhat normal play, the crash *slams desk * always *slams desk * strikes *slams through desk *! All traces of addons have been removed, temporary files have been shredded, and the game has been scanned and repaired multiple times. I even found myself logging onto Classic when there’s only a few days left of the magnificent Dragonflight! Help!

You know the issue, you already know the above — sans the verbosity and grandiloquence perhaps — so please, tell and show us there’s light at the end of the tunnel, as right now it’s looking pretty darn bleak. Here you have proof that three weeks of progressively worse gameplay experience may culminate in essayed cries for customer respect!

Onto the technicals…

Now I know my Macbook is pushing 80+ years according to some computer-year calculations, though I have never had any issues running WoW apart from certain pre-patches. Ageism is not cool. Here are my specs:

MacBook Pro, 13-inch, 2018, Four Thunderbolt 3 Ports
Processor: 2.3 GHz Quad-Core Intel Core i5
Graphics: Intel Iris Plus Graphics 655 1536 MB
Memory: 16 GB 2133 MHz LPDDR3
MacOs: Sonoma 14.6.1 (23G93)

Now for the most part, the crashes have completely shut down my computer. The one and only time the game crashed and closed, however — after I had restored graphics to default and turned off Optional GPU Features and Advanced Work Submit (the one time that worked a little) — the error I was given was 0632F1AA-7CF7-4D20-80E7-A04C8BE965E4. The other countless times my computer has black-screen crashed since the pre-patch has resulted in crash reports from the Mac OS. One of the latest ones I have pasted at the very end of this post, and above this I have paste the text from the latest crash text from Error folder in the _retail _ directory. Surprisingly there are only three errors logged in this folder since the pre-patch, considering the amount of crashes I have experienced, and the previous two since the pre-patch are considerably longer (including CVar settings, GxInfo, Streaming diagnostics, etc. which I can share here or elsewhere if they would be of use).

In closing (I promise)…

I would happily play my few sessions before launch in black+white until you sort this out, if that meant I could experience some of the soon-reserved-for-the-bronze-dragonflight content. What we ask as a bare minimum is for a playable game, and save your fancy little updates that don’t significantly affect gameplay for when they actually work. Puh-lease!

If you have read all of the above, you must now surely believe that the game is truly unplayable for some of your fellow Azerothians. Here’s to hoping that Blizzard heeds our call and request! Cheers either way! :beers:

—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—

App: /Applications/World of Warcraft/retail/World of Warcraft.app/Contents/MacOS/World of Warcraft

Exception: SIGTERM [HANG]: Terminated
ProcessID: 885
ThreadID: 259

<Exception.IssueType> Exception
Crash
<Exception.Summary :>
SIGTERM [HANG]: Terminated
0 0x00007FF816D0B846 “libsystem_kernel.dylib” ← 1 0x0000000110FCABF3 “com.blizzard.worldofwarcraft” ← 2 0x0000000110DE5859 “com.blizzard.worldofwarcraft”
<:Exception.Summary>
<Exception.Assertion :>
0 0x00007FF816D0B846 “libsystem_kernel.dylib”
1 0x0000000110FCABF3 “com.blizzard.worldofwarcraft”
2 0x0000000110DE5859 “com.blizzard.worldofwarcraft”
3 0x0000000110DE20E1 “com.blizzard.worldofwarcraft”
4 0x000000010F9BA04F “com.blizzard.worldofwarcraft”
5 0x00007FF816C1C231 “libsystem_c.dylib”
6 0x00007FF816C1C052 “libsystem_c.dylib”
7 0x000000010E695A47 “com.blizzard.worldofwarcraft”
8 0x000000010E695A18 “com.blizzard.worldofwarcraft”
9 0x000000010E6959E9 “com.blizzard.worldofwarcraft”
10 0x00007FF8169BE345 “com.apple.darwin.ignition”
<:Exception.Assertion>
<Exception.HashBlock :>
ERROR #132

0 0x00007FF816D0B846 “libsystem_kernel.dylib”
1 0x0000000110FCABF3 “com.blizzard.worldofwarcraft”
2 0x0000000110DE5859 “com.blizzard.worldofwarcraft”
3 0x0000000110DE20E1 “com.blizzard.worldofwarcraft”
4 0x000000010F9BA04F “com.blizzard.worldofwarcraft”
5 0x00007FF816C1C231 “libsystem_c.dylib”
<:Exception.HashBlock>
No
<Jira.JiraProjectId> 11701
<Jira.JiraProjectKey> WOW11
<Exception.ProjectId> 10

11.0.2.56110
<Exception.BuildNumber> 56110
<Exception.Branch> 11.0.2
<Exception.WowProject> Mainline
World of Warcraft
Client

11.0.2.56110
Retail
Type: WoW
World of Warcraft.app
Executable UUID: D4E9B04B-7272-3E07-B6C5-D6156C273ED5
<Wow.Platform> X64
<Exception.Platform> All Mac (x86 64-bit)
User: …
Computer: … .home
Virtual Memory: 0.00 MB
Free Disk Space: 11657.12 GB
Exe Built: Aug 12 2024 09:46:26
0000003F 00001FFF 00001FFF
App Up Time: 0 days, 0 hours, 7 minutes, 40 seconds
System Up Time: 0 days, 0 hours, 9 minutes, 22 seconds
mach_absolute_time
Current Frame: 32623
Current Time: 549110
Current Tick: 32
0
2
Number of thread pool threads: 0/0/0 (High/Mid/Low)
launchd
<Locale.Text> enUS
<Locale.Audio> enUS
Session Time(hh:mm:ss): 00:07:15
<SessionTime.Grouping> 00:00:00 - 00:14:59
Time in World(hh:mm:ss): 00:00:00
<TimeInWorld.Grouping> 00:00:00 - 00:00:00
Total Time in World(hh:mm:ss): 00:00:00
<TotalTimeInWorld.Grouping> 00:00:00 - 00:00:00
<Addons.HasAny.Loading> No
<Addons.HasAny.Loaded> No
0
0
No
<SoundSystem.Restarts> 0
<LoadingScreen.Enabled> No
<CombatLogEntry.Current> CombatLogEntry::PushEvent(casterGuidType, targetGuidType): 0, 0
Number of successful WoWConnections: 9
Battle Tag: n/a
Last Known Player: Player-3657-0B14876F, (870, -44.9812, -17.7549, 154.048)
Selected Player: 0000000000000000

CVar Settings:

Installation settings:

Installation settings not created.

           GxInfo

No GX Device Created
0
0
0

—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—0—

Example of one of many Mac OS crash reports:

panic(cpu 6 caller 0xffffff7f988aab14): “[IGPU] sendHostToGucMessage: Firmware communication error: no action response!\n” @IGGuC.cpp:3536
Panicked task 0xffffff9f234bb7d8: 221 threads: pid 0: kernel_task
Backtrace (CPU 6), panicked thread: 0xffffff90bf4c7b30, Frame : Return Address
0xfffffffe01233840 : 0xffffff8003c26561
0xfffffffe01233890 : 0xffffff8003d8bc30
0xfffffffe012338d0 : 0xffffff8003d7b1ec
0xfffffffe01233950 : 0xffffff8003bc0971
0xfffffffe01233970 : 0xffffff8003c2684d
0xfffffffe01233a60 : 0xffffff8003c25ef3
0xfffffffe01233ac0 : 0xffffff80043db7ab
0xfffffffe01233bb0 : 0xffffff7f988aab14
0xfffffffe01233bf0 : 0xffffff7f98824ddd
0xfffffffe01233c20 : 0xffffff7f98822dd3
0xfffffffe01233c60 : 0xffffff7f988255a2
0xfffffffe01233cc0 : 0xffffff7f9882607b
0xfffffffe01233d00 : 0xffffff7f988aaaa1
0xfffffffe01233d40 : 0xffffff7f98824ddd
0xfffffffe01233d70 : 0xffffff7f98822e40
0xfffffffe01233db0 : 0xffffff7f988261a6
0xfffffffe01233e10 : 0xffffff7f988a8e76
0xfffffffe01233e60 : 0xffffff7f98cbcdb2
0xfffffffe01233ea0 : 0xffffff7f98cbc4ff
0xfffffffe01233ed0 : 0xffffff80043109da
0xfffffffe01233f20 : 0xffffff800430f1fe
0xfffffffe01233f60 : 0xffffff800430e826
0xfffffffe01233fa0 : 0xffffff8003bc019e
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(481.40.2)[D4E64BC5-BB33-38C7-A445-932573231969]@0xffffff7f98ca9000->0xffffff7f98d13fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5B020421-9B82-3828-BC4D-C83045159601]@0xffffff800529c000->0xffffff80052d3fff
dependency: com.apple.iokit.IOGraphicsFamily(598)[79F2F7E4-E451-35E1-BF22-1EFFA4192888]@0xffffff7f98e39000->0xffffff7f98e67fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[250D1260-447B-3BF3-96B2-C784699ED806]@0xffffff8005f68000->0xffffff8005f99fff
dependency: com.apple.iokit.IOReportFamily(47)[8476E632-A5DB-34EC-A637-30C25D8C1767]@0xffffff8005faa000->0xffffff8005facfff
dependency: com.apple.iokit.IOSurface(352.50.1)[7CADA50D-8D9C-3062-995C-7A44CB17D810]@0xffffff80060cc000->0xffffff80060f2fff
com.apple.driver.AppleIntelKBLGraphics(22.0.5)[5B52FAFF-7DD4-34AF-AC18-0BDC593BE034]@0xffffff7f9881f000->0xffffff7f988fafff
dependency: com.apple.iokit.IOAcceleratorFamily2(481.40.2)[D4E64BC5-BB33-38C7-A445-932573231969]@0xffffff7f98ca9000->0xffffff7f98d13fff
dependency: com.apple.iokit.IOGraphicsFamily(598)[79F2F7E4-E451-35E1-BF22-1EFFA4192888]@0xffffff7f98e39000->0xffffff7f98e67fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[250D1260-447B-3BF3-96B2-C784699ED806]@0xffffff8005f68000->0xffffff8005f99fff
dependency: com.apple.iokit.IOSurface(352.50.1)[7CADA50D-8D9C-3062-995C-7A44CB17D810]@0xffffff80060cc000->0xffffff80060f2fff

Process name corresponding to current thread (0xffffff90bf4c7b30): kernel_task

Mac OS version:
23G93

Kernel version:
Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64
Kernel UUID: B8A95C25-3789-30A2-AE3C-7A48E0B91426
roots installed: 0
KernelCache slide: 0x0000000003800000
KernelCache base: 0xffffff8003a00000
Kernel slide: 0x00000000038e4000
Kernel text base: 0xffffff8003ae4000
__HIB text base: 0xffffff8003900000
System model name: MacBookPro15,2 (Mac-827FB448E656EC26)
System shutdown begun: NO
Hibernation exit count: 10

System uptime in nanoseconds: 14216846857723
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000cee1e1b5e65
Sleep : 0x000006c8ad5daede 0x00000950f6f9a3d6 0x000006be6cffeaca
Wake : 0x000006c8c6ae8ed6 0x00000a32b6f734d2 0x000006c8c4a32e58
Compressor Info: 3% of compressed pages limit (OK) and 4% of segments limit (OK) with 1 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff8a55bf9000 - 0xffffffaa55bf9000
. PGZ : 0xffffff8a55bf9000 - 0xffffff8a57bfa000
. VM : 0xffffff8a57bfa000 - 0xffffff8f243f9000
. RO : 0xffffff8f243f9000 - 0xffffff90bdbf9000
. GEN0 : 0xffffff90bdbf9000 - 0xffffff958a3f9000
. GEN1 : 0xffffff958a3f9000 - 0xffffff9a56bf9000
. GEN2 : 0xffffff9a56bf9000 - 0xffffff9f233f9000
. GEN3 : 0xffffff9f233f9000 - 0xffffffa3efbf9000
. DATA : 0xffffffa3efbf9000 - 0xffffffaa55bf9000
Metadata: 0xffffff8027767000 - 0xffffff8047767000
Bitmaps : 0xffffff8047767000 - 0xffffff804a767000
Extra : 0 - 0

last started kext at 10905525124: >!AHIDKeyboard 7440.3 (addr 0xffffff8005108000, size 20480)
loaded kexts:

!ATopCaseHIDEventDriver 7440.8
!AHIDALSService 1
AGPM 135
!APlatformEnabler 2.7.0d0
X86PlatformShim 1.0.0
@filesystems.autofs 3.0
!ABridgeAudio!C 440.1
!AGraphicsDevicePolicy 8.1.9
!AUpstreamUserClient 3.6.11
@AGDCPluginDisplayMetrics 8.1.9
!AGFXHDA 340.1
pmtelemetry 1
@filesystems.nfs 1
|IOUserEthernet 1.0.1
usb.!UUserHCI 1
!AUIO 1
!ASunrise 1
AGDCBacklightControl 8.1.9
!AFIVRDriver 4.1.0
!AHV 1
!A!IKBLGraphics 22.0.5
!A!IPCHPMC 2.0.1
!ABacklight 180.9
BridgeAudioCommunication 440.1
!AAVEBridge 6.1
!AMCCSControl 1.17
!A!ISlowAdaptiveClocking 4.0.0
@UVCService 1
!A!ICFLGraphicsFramebuffer 22.0.5
!AThunderboltIP 4.0.3
ACPI_SMC_PlatformPlugin 1.0.0
BCMWLANFirmware4388.Hashstore 1
BCMWLANFirmware4387.Hashstore 1
BCMWLANFirmware4378.Hashstore 1
BCMWLANFirmware4377.Hashstore 1
BCMWLANFirmware4364.Hashstore 1
BCMWLANFirmware4355.Hashstore 1
!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.lifs 1
@filesystems.hfs.kext 650.140.2
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@filesystems.apfs 2236.141.1
!ABCMWLANBusInterfacePCIeMac 1
@private.KextAudit 1.0
!ASmartBatteryManager 161.0.0
!AACPIButtons 6.1
!ASMBIOS 2.1
!AACPIEC 6.1
!AAPIC 1.7
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 405
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
@Dont_Steal_Mac_OS_X 7.0.0
!ADiskImages2 276.120.7
@kec.!AEncryptedArchive 1
!AHIDKeyboard 7440.3
!AHS!BDriver 7440.8
IO!BHIDDriver 9.0.0
!AActuatorDriver 7440.9
!AMultitouchDriver 7440.9
!AInputDeviceSupport 7440.1
!UAudio 640.12
!AAudioClockLibs 340.8
!AGraphicsControl 8.1.9
!AHDA!C 540.3
|IOHDA!F 540.3
|IOAudio!F 540.3
@vecLib.kext 1.2.0
@kext.triggers 1.0
IOHIDPowerSource 1
!ACallbackPowerSource 1
|IOAVB!F 1220.1
!ARSMChannel 1
|IORSM!F 1
!AIPAppender 1.0
!A!ILpssUARTv1 3.0.60
!A!ILpssUARTCommon 3.0.60
!AOnboardSerial 1.0
!ASMBusPCI 1.0.14d1
!ABacklightExpert 1.1.0
|IONDRVSupport 598
!ASMBus!C 1.0.18d1
@!AGPUWrangler 8.1.9
|IOSlowAdaptiveClocking!F 1.0.0
@plugin.IOgPTPPlugin 1240.15
|IOAccelerator!F2 481.40.2
@!AGraphicsDeviceControl 8.1.9
|IOGraphics!F 598
!AThunderboltEDMSink 5.0.3
!AThunderboltDPOutAdapter 8.5.1
IOPlatformPluginLegacy 1.0.0
X86PlatformPlugin 1.0.0
IOPlatformPlugin!F 6.0.0d8
driverkit.serial 6.0.0
usb.IOUSBHostHIDDevice 1.2
usb.cdc.ecm 5.0.0
usb.cdc.ncm 5.0.0
usb.cdc 5.0.0
usb.networking 5.0.0
usb.!UHostCompositeDevice 1.2
!AHPM 3.4.4
!A!ILpssI2C!C 3.0.60
!A!ILpssDmac 3.0.60
!AThunderboltDPInAdapter 8.5.1
!AThunderboltDPAdapter!F 8.5.1
!AThunderboltPCIDownAdapter 4.1.1
!ABSDKextStarter 3
|IOSurface 352.50.1
@filesystems.hfs.encodings.kext 1
!ASyntheticGame!C 11.6.1
!AXsanScheme 3
!AThunderboltNHI 7.2.81
|IOThunderbolt!F 9.3.3
usb.!UVHCIBCE 1.2
usb.!UVHCICommonBCE 1.0
usb.!UVHCI 1.2
usb.!UVHCICommon 1.0
!AEffaceableNOR 1.0
|IOBufferCopy!C 1.1.0
|IOBufferCopyEngine!F 1
|IONVMe!F 2.1.0
!ABCMWLANCoreMac 1.0.0
|IO80211!F 1200.13.0
IOImageLoader 1.0.0
!AOLYHALMac 1
|IOSerial!F 11
corecapture 1.0.4
usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
!A!ILpssI2C 3.0.60
!A!ILpssGspi 3.0.60
usb.!UXHCIPCI 1.2
usb.!UXHCI 1.2
!AEFINVRAM 2.1
!AEFIRuntime 2.1
!ASMCRTC 1.0
|IOSMBus!F 1.1
|IOHID!F 2.0.0
|IOTimeSync!F 1240.15
|IOSkywalk!F 1.0
mDNSOffloadUserClient 1.0.1b8
|IONetworking!F 3.4
DiskImages 493.0.0
|IO!B!F 9.0.0
|IOReport!F 47
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
!ASSE 1.0
!ALockdownMode 1
!AKeyStore 2
!UTDM 556
|IOUSBMass!SDriver 245
|IOUSBHost!F 1.2
!UHostMergeProperties 1.2
usb.!UCommon 1.0
!ABusPower!C 1.0
|IOSCSIBlockCommandsDevice 495
|IOSCSIArchitectureModel!F 495
!AFDEKeyStore 28.30
!AEffaceable!S 1.0
|IO!S!F 2.1
!ACyrus 1
!AMobileFileIntegrity 1.0.5
$!AImage4 6.3.0
@kext.CoreTrust 1
!ACredentialManager 1.0
|CoreAnalytics!F 1
!ASEPManager 1.0.1
IOSlaveProcessor 1
!AACPIPlatform 6.1
!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
watchdog 1
@kec.pthread 1
@kec.XrtHostedXnu 1
@kec.Libm 1
@kec.Compression 1.0
@kec.corecrypto 14.0

5 Likes
2

I’ve never had to visit the forums in the past because the game has been running flawlessly on my MacBooks, including my new one during Dragonflight. Now that the TWW pre-patch, which is in the same state the game has been in since Beta, has more or less broken the game for seemingly no good reason it’s honestly shocking how difficult it is to get help. We don’t even have our own Mac forum here in Europe :frowning:

I wish we’d at least get some aknowledgement so we could know whether the Mac issues are even being worked on, because it’s lasted so long that I worry we won’t see any updates until far into TWW. It has killed all my hype, not knowing whether we’re even in for a complete or even functional product.

(And don’t suggest contacting customer support. The bots have straight up responded with information on the wrong operating system (told me how to do stuff on Windows) and even the wrong game (Somehow gave me information about CoD…?)

3 Likes
3

I’m having the same issue and I can’t get into the game in my M1 MBP to file a ticket but the game works on my old 2013 (!!!) Macbook Pro albeit, it’s very slow and my machine sounds like it’s trying to take off.

4 Likes
4

Same problem here! iMac 2019 with i9-9900k and Rx580x. While playing I get a black screen and only shut down by pressing the power button works! It happens especially while flying fast with dragonriding and when the system gets stressed! At first glance I thought my gpu was dying but after running multiple benchmarks including “Heaven” which I stressed enough my gpu for an hour I didn’t have any issues. I followed many steps including disabling all new GPU features, lowering from 7 to 5 the video details, disabling all my addons but in the end nothing helped to get rid of these crashes!! Any help would be much appreciated!!

P.S. These crashes happen very often… while random from the one hand, the game remains still unplayable!!

4 Likes
5

This is not a thread that should be closed. There are many reports of players giving up once updating to Sonoma, but this is very frustrating.
I am not prepared to see my mac crashing at WOW start with a black screen and the ominous “Your computer restarted because of a problem” too many times and I find it unbelievable that neither Blizzard or Apple are doing anything to fix this problem.
My specs are:
2.3 GHz Quad-Core Intel Core i7
Intel Iris Plus Graphics 1536 MB
32 GB 3733 MHz LPDDR4X
MacOS Sonoma14.6.1 (23G93)

2 Likes
6

Not a blizz issue and blizz has no ability to alter the drivers of the OS. Roll back to Ventura.

1 Like
7

I am still unable to launch the game, 2 weeks I haven’t been able to play, either due to patch download issues or game not launching from Bnet or manually.

Tried everything!

8

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