WoW Forever beta crash, lag and FPS fixes
The most common beta problem, a crash when your character logs in on a Mac or an AMD card, is usually fixed by setting Secondary Lighting to Fair at the character select menu. EU and Oceanic lag improves by turning off Optimize Network for Speed. Everything else players have found, and what Blizzard has confirmed, is below.
WoW Forever beta problems and fixes
| Problem | Fix | Confidence |
|---|---|---|
| Crash to desktop or a frozen screen when logging a character in, worst on Apple Silicon Macs and AMD RX 9000 cards | At character select open the Menu, go to System, Graphics, and set Secondary Lighting to Fair. Log in, then raise it again later if it stays stable. | Reported |
| 600 to 800 ms latency from Europe or Oceania | Open Options, Network, and turn off Optimize Network for Speed. Some players also use a VPN with a US exit. The beta runs on one US-hosted environment, so some extra latency is unavoidable for now. | Reported |
| 25 to 50 frames per second on a high-end PC, or frame rate falling over an hour | Update your graphics driver, turn off Target Framerate in the graphics options, delete the Cache folder inside the beta install and try DirectX 11. If it still decays over time, restart the client; a memory leak is suspected. | Reported |
| Addon settings, keybinds or interface layout reset every time you start the game | This is a beta bug: saved settings are written but not loaded on a fresh start. There is no workaround yet beyond leaving the client running. It is not on Blizzard's list, so report it on the beta forum. | Reported |
| The Install button is greyed out or the beta is missing from the dropdown | Update the Battle.net app, then select World of Warcraft and open the Game Version dropdown. The beta sits under In Development. Purchased access can take up to 30 minutes to appear, and invites arrive in waves. | Official |
| Install fails on a Mac with an unexpected error | A command-line workaround using the Battle.net binary with the beta product flag is circulating on the forums. Check the official Known Issues post first, since Blizzard has linked the Mac threads from it. | Reported |
| Your operating system does not meet the minimum specs | Check the graphics card cutoff on the system requirements page. Cards older than AMD GCN 1, NVIDIA Maxwell or Intel Skylake cannot run the new lighting. | Official |
| The Legacy panel throws errors when you press Y | It is meant to open at level 25. Ignore it under the level 20 cap; Blizzard lists it as a known issue. | Official |
| Guild charter cannot get signatures | Hand the charter in with zero signatures for now. Blizzard has disabled the requirement temporarily. | Official |
Reported means players found it and Blizzard has not confirmed it. Official means it comes from Blizzard's Known Issues post or the beta announcement. The system requirements and the addon guide cover the rest.
What Blizzard has fixed and what is still open
- Official Blizzard keeps a Known Issues list on the beta forum. Items marked fixed in the next build include the Waylaid Crate turn-in bugs, Holy Strike rank scaling, Ret Paladin Vengeance triggering from periodic crits, Starshards ignoring Twilight Focus and the Coldridge Valley map not revealing. Still in progress: pet stat displays, glancing blow maths for casters, guild charters, the Cooldown Manager, the friends list and the character pane missing level and class.Blizzard forums: Beta Known Issues, 2026-09-18
- Official The Legacy panel (hotkey Y) is meant to open at level 25, so it throws errors if opened earlier in the beta.Blizzard forums: Beta Known Issues, 2026-09-18
- Official Feedback goes to the new WoW Forever Beta Discussion forum, opened on 2026-09-17. There are no separate beta forums beyond it.Blizzard forums: Beta Discussion forum
- Verified The beta runs on a single US-hosted regional environment. Launch-night queues reached the tens of thousands, and Blizzard's senior producer explained the causes as a login metering system tripping too early, stale database statistics and empty maps not shutting down, all since fixed with extra world servers added.2 independent reports
- Reported Players in Europe and Oceania report 600 to 800 ms latency on the US-hosted beta. Turning off Optimize Network for Speed under Options, Network helped some players, and press reported Blizzard pushed fixes that brought many EU players near 100 ms.Blizzard EU forums: latency thread · plus 1 independent report
- Reported Crashes on character login, worst on Apple Silicon Macs and AMD RX 9000 cards: the widely shared workaround is to open the menu at character select and set Secondary Lighting to Fair. Blizzard has linked the Mac crash thread from its Known Issues post but has not confirmed the fix.Blizzard forums: Mac crash thread · Blizzard forums: Beta Known Issues, 2026-09-18 · plus 1 independent report
- Reported Low or falling frame rates on high-end PCs: players report help from updating drivers, disabling Target Framerate, clearing the cache folder and switching to DirectX 11. Frame rate decaying over an hour suggests a memory leak that Blizzard has not acknowledged.Blizzard forums: beta FPS thread
- Reported Addon and interface settings reset every time the beta client restarts. Saved variables are written but never loaded on a fresh start, which affects addons and some of Blizzard's own settings. Not on the official Known Issues list yet.Blizzard forums: addon settings not saving
- Reported The Install button only appeared after the Q&A on beta day, so there was no pre-download. Mac installs that fail with an unexpected error have a command-line workaround circulating on the forums.Blizzard EU forums: install thread