[{"data":1,"prerenderedAt":323},["ShallowReactive",2],{"site-settings":3,"article:\u002Fresources\u002Fguides\u002Ffix-wow-forever-beta-macos-crashes":16},{"id":4,"description":5,"email":6,"extension":7,"footerNote":8,"legalNotice":9,"locale":10,"meta":11,"name":12,"stem":13,"url":14,"__hash__":15},"settings\u002Fsettings.yml","Compare World of Warcraft realms by expansion, region, population and play style.","listings@realmlist.org","yml","An independent realm directory.","Not affiliated with Blizzard Entertainment.","en",{},"RealmList","settings","https:\u002F\u002Frealmlist.org","QXaYspLUSxnrVumL6oFir6PInhNsRw-yJchxEYSe1AU",{"id":17,"title":18,"author":19,"body":20,"category":286,"description":287,"draft":288,"extension":289,"featured":288,"meta":290,"navigation":291,"path":292,"publishedAt":293,"seo":294,"sitemap":295,"sources":298,"stem":314,"tags":315,"updatedAt":321,"__hash__":322},"articles\u002Fresources\u002Fguides\u002Ffix-wow-forever-beta-macos-crashes.md","Fixing the WoW: Forever Beta Crash on Apple Silicon Macs — the Workarounds That Actually Work","RealmList Editorial",{"type":21,"value":22,"toc":277},"minimark",[23,37,42,62,76,79,95,102,106,109,206,210,233,237,252,256,271],[24,25,26,27,31,32,36],"p",{},"As of September 19, the standing advice for Mac players in the ",[28,29,30],"em",{},"World of Warcraft: Forever"," beta was bleak: a tracker roundup noted that macOS testers were crashing at launch and that ",[33,34,35],"strong",{},"no player workaround had surfaced",". Over the rest of the weekend that changed. The crash threads on Blizzard's forums grew into the hundreds of replies, players with M1 through M5 machines systematically isolated which graphics settings trigger the failure, and a repeatable sequence of fixes emerged. It is still unofficial, still incomplete — and it is working for most people who apply all of it.",[38,39,41],"h2",{"id":40},"what-this-crash-actually-is","What this crash actually is",[24,43,44,45,48,49,52,53,56,57,61],{},"The signature is specific, and worth recognizing before you change anything: character selection works fine, you click ",[33,46,47],{},"Enter World",", the loading bar completes — and then the ",[33,50,51],{},"entire macOS graphical session dies",". On most machines that means a black screen, a forced reboot, and a \"WindowServer experienced a problem\" dialog on login. On at least one M5 Pro machine it escalated to a full ",[33,54,55],{},"kernel panic"," (",[58,59,60],"code",{},"IOGPU::systemPagingOff() timeout",").",[24,63,64,65,56,68,71,72,75],{},"The crash diagnostics confirm this is not an ordinary application crash: macOS records a ",[33,66,67],{},"WindowServer watchdog termination",[58,69,70],{},"bug_type 409","), killing the graphics session after the window server stopped responding for 40 seconds, with the WoW beta process stuck in its stack. One detailed EU report (Mac mini M4 Pro, beta client 1.60.1.69893, ARM64, Metal) logs four watchdog events in thirty minutes, all at the exact moment of the character-select-to-world transition — plus a separate repeatable ",[58,73,74],{},"AddAccountCharacter - no surname provided"," assert in the client's own error logs, likely related to Forever's mandatory surnames.",[24,77,78],{},"Two consequences follow from that diagnosis:",[80,81,82,89],"ul",{},[83,84,85,88],"li",{},[33,86,87],{},"\"Lower graphics\" is only half a fix."," The failing path is the modern lighting\u002Fshadow stack on Metal, not raw load — which is why quality presets alone fix some machines and not others.",[83,90,91,94],{},[33,92,93],{},"It can crash the OS, not just the game."," Save your work before testing any fix. Reports from M1 to M5 machines on macOS 26.x through 27 all describe the same whole-session failure.",[24,96,97,98,101],{},"Notably, this crash is ",[33,99,100],{},"not on Blizzard's official known-issues list"," (September 18 revision), which is part of why the community did the isolation work itself.",[38,103,105],{"id":104},"the-fix-sequence-in-order","The fix sequence, in order",[24,107,108],{},"Apply these from the character select screen. If a step gets you into the world, stop and play; the earlier steps are the ones with the most confirmations.",[110,111,112,122,132,150,156,162,185],"ol",{},[83,113,114,117,118,121],{},[33,115,116],{},"Reset in-game options first."," Battle.net → cogwheel next to Play → Game Settings → ",[33,119,120],{},"Reset In-Game Options",". Several testers reported this alone let them log in after nothing else worked, because it clears a corrupted graphics state that no in-game toggle can reach.",[83,123,124,127,128,131],{},[33,125,126],{},"Drop quality to 1 and log in from the character screen."," Do not try to fix settings mid-session. Set the quality slider to 1, enter the world successfully, ",[28,129,130],{},"then"," raise settings selectively.",[83,133,134,137,138,141,142,145,146,149],{},[33,135,136],{},"Uncheck all four Compatibility Settings"," at the bottom of the graphics options — this includes ",[33,139,140],{},"Optional GPU Features"," and ",[33,143,144],{},"Async Resource Creation",". This was the single most-repeated confirmed fix on Apple Silicon. One Mac Studio M4 user's summary after extensive testing: uncheck all four, quality 1, log in — then the game runs at 10 ",[28,147,148],{},"provided"," Secondary Lighting and Shadows stay at minimum.",[83,151,152,155],{},[33,153,154],{},"Secondary Lighting: Fair or minimum."," This setting is the crash's prime suspect — anything above Fair crashed one tester's client outright, and Medium reproduced the failure (and later a kernel panic) on an M5 Pro even after \"High\" had already failed.",[83,157,158,161],{},[33,159,160],{},"Shadow Quality: Low."," Above Low, testers report the world rendering dark with black grass and green-tinted geometry on Apple GPUs. The bug report thread documents pink, over-bright fog in Teldrassil at minimum shadows; raising shadows fixes the colors but re-triggers the instability.",[83,163,164,171,172,174,175,178,179,181,182,184],{},[33,165,166,167,170],{},"Compute Effects: Disabled — then ",[58,168,169],{},"\u002Freload","."," Compute Effects drains FPS over time even when set to Disabled, until a ",[58,173,169],{}," clears it. The same unload bug affects ",[33,176,177],{},"Environmental Distance",": lowering it does not reclaim the memory until you ",[58,180,169],{},". Plan to ",[58,183,169],{}," once after any settings change.",[83,186,187,194,195,198,199,141,202,205],{},[33,188,189,190,193],{},"If nothing above works: ",[58,191,192],{},"Config.wtf"," edits."," In the game folder's ",[58,196,197],{},"WTF\u002FConfig.wtf",", set ",[58,200,201],{},"SET gxApi \"Metal (Legacy)\"",[58,203,204],{},"SET ffxFSR \"0\"",". Results are mixed — some M1 users report it as the missing piece, others report no effect even combined with minimum settings — so treat it as a last resort, not a solution.",[38,207,209],{"id":208},"what-the-threads-have-already-ruled-out","What the threads have already ruled out",[80,211,212,218,224,230],{},[83,213,214,217],{},[33,215,216],{},"Lowering the quality preset by itself."," Repeatedly reported as insufficient; it helps only in combination with steps 3–6.",[83,219,220,223],{},[33,221,222],{},"Windowed mode."," Suggested early in the threads, then reproduced as failing in both fullscreen and windowed — do not count on it.",[83,225,226,229],{},[33,227,228],{},"Scan & Repair and reinstalls."," Multiple users ran the Battle.net repair tool and full reinstalls with no change; the failure is in rendering-path configuration, not corrupted files.",[83,231,232],{},"** blaming your machine.** The crash reproduces on 96 GB M2 Max laptops, M4 Max desktops and a brand-new M5 Max — this is a client\u002FMetal interaction, not a spec problem.",[38,234,236],{"id":235},"report-it-properly-the-fix-depends-on-it","Report it properly — the fix depends on it",[24,238,239,240,243,244,247,248,251],{},"Because the crash is absent from the official known-issues list, forum reports are currently the only signal the Mac team has. If you are affected: post in ",[33,241,242],{},"Mac Technical Support"," with your Mac model, macOS build, and beta build number; attach the macOS ",[58,245,246],{},".ips"," WindowServer reports from ",[58,249,250],{},"~\u002FLibrary\u002FLogs\u002FDiagnosticReports"," if you have them — the watchdog reports contain the exact stack the developers need. Note whether SSH or a remote session survives the freeze (at least one tester confirmed the machine is alive underneath the dead session; that detail matters for diagnosis).",[38,253,255],{"id":254},"windows-players-crashing-on-login-instead","Windows players crashing on login instead?",[24,257,258,259,262,263,266,267,270],{},"A related but distinct crash affects ",[33,260,261],{},"AMD GPUs on Windows"," — crash to desktop at the character-to-world transition, fixed by setting ",[33,264,265],{},"Secondary Lighting to Fair"," from the character select screen, with ",[33,268,269],{},"switching to DX11"," as the second option. Same suspect subsystem, different platform, and neither is an official fix yet.",[272,273,274],"note",{},[24,275,276],{},"Written September 21, 2026, on day four of the WoW: Forever beta. Every fix above is community-reported, not officially acknowledged: the Mac crash is absent from Blizzard's September 18 known-issues list, and the next beta build can change or break any of it. Re-test after each client update, and treat the Config.wtf edits as experimental. If a future build makes the crash worse rather than better, the Reset In-Game Options step is the fastest way back to a playable state.",{"title":278,"searchDepth":279,"depth":279,"links":280},"",2,[281,282,283,284,285],{"id":40,"depth":279,"text":41},{"id":104,"depth":279,"text":105},{"id":208,"depth":279,"text":209},{"id":235,"depth":279,"text":236},{"id":254,"depth":279,"text":255},"guides","The Forever beta hard-freezes entire Apple Silicon Macs at the \"Enter World\" loading screen — a WindowServer watchdog kill, not a normal game crash. Community testing over the first weekend converged on a settings sequence that gets most machines in. Here it is, in order.",false,"md",{},true,"\u002Fresources\u002Fguides\u002Ffix-wow-forever-beta-macos-crashes","2026-09-21",{"title":18,"description":287},{"loc":292,"changefreq":296,"priority":297},"weekly",0.7,[299,302,305,308,311],{"label":300,"url":301},"Blizzard Forums — Mac client crashing wow: forever (beta discussion thread)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fmac-client-crashing-wow-forever\u002F2352584",{"label":303,"url":304},"Blizzard Forums — Forever Beta freezes entire Mac when entering the world (MacBook Air M4, macOS 26.6.2)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fwow-forever-beta-freezes-entire-mac-when-entering-the-world-%E2%80%94-macbook-air-m4-macos-2662\u002F2352686",{"label":306,"url":307},"Blizzard Forums — MacOS 27 and Forever WindowServer Crash (includes kernel panic report)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fmacos-27-and-forever-windowserver-crash\u002F2352734",{"label":309,"url":310},"Blizzard Forums (EU) — MacOS client crashes entire PC, WoW: Forever Beta (log analysis, client 1.60.1.69893)","https:\u002F\u002Feu.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fmacos-client-crashes-entire-pc-wowforever-beta\u002F629297",{"label":312,"url":313},"Blizzard Forums — WoW Forever Beta Known Issues, September 18 (Kaivax)","https:\u002F\u002Fus.forums.blizzard.com\u002Fen\u002Fwow\u002Ft\u002Fwow-forever-beta-known-issues-september-18\u002F2352687","resources\u002Fguides\u002Ffix-wow-forever-beta-macos-crashes",[316,317,318,319,320],"World of Warcraft Forever","Beta","macOS","Troubleshooting","Apple Silicon",null,"DoK2nQUGEL3BAkx468bA5CSDaHqXzHvrYniJz97Hl3Y",1789953196528]