WoW Forever beta: access, installation and system requirements

The beta is missing: license, launcher or installation? #

First separate an account entitlement from a visible download. Blizzard directs invited players to check for a Forever beta license under Your Game Accounts. An opt-in confirmation or a beta news email does not itself establish access.

Update to beta build 69977 #

Blizzard’s September 22 client notice identifies WoW Forever 1.60.1, build 69977. Exit the beta and update it through Battle.net before checking the affected behavior.

The notice reports Mac display/stability fixes, improved character-selection navigation when launched with gamepad active, and gamepad interaction with items that offer quests. These are developer-reported fixes; Kingy has not reproduced them. The September 24 weekly update is still planned.

Get help with a beta blocker #

Match a supported quest symptom in Quest Rescue, or compare dated mechanic and technical reports in Mechanics Lab.

Choose the access path that applies to you #

Check the account entitlement before reinstalling anything. A Battle.net login can be correct while the selected WoW account is not the one with the invitation or pack benefit.

Blizzard Support says game time is not required for beta access. Support cannot add beta access to an account, replace a lost Collector’s Edition beta code or troubleshoot the beta client.

Current beta dates and playable limits #

Use the September 17 beta announcement for current dates. Its October 21 guidance supersedes the earlier roadmap label; check later notices before your final session.

Treat friend codes as a separate launch offer #

Invite-A-Friend codes are for launch-week access, not beta access. Blizzard Support says eligible recipients can play Forever from November 4 through November 11 without a subscription or game time. The code excludes Skyborne and its starting quests, and it cannot be redeemed on a WoW account that already purchased a Forever upgrade.

Delivery, code counts, redemption limits and missing-email checks belong in the code reference. Keep them separate from beta entitlement so a launch code is never presented as a beta solution.

Install the beta in Battle.net #

These are Blizzard’s published installation steps; Kingy has not independently reproduced them on each platform. Opt-in alone does not grant access. Keep exact errors for support if the documented steps do not resolve the problem.

1. Sign in to the Battle.net desktop app with the account that has beta access. Update the app and your graphics drivers.
2. Select World of Warcraft, then choose World of Warcraft: Forever Beta under In Development in the Game Version menu above Play. Click Install.
3. After installation, click Play, select an available test realm and create a test character. Record the build when reporting a problem.
4. If access is missing after an eligible bundle purchase, Blizzard advises allowing up to 30 minutes and restarting the launcher. Verify the beta license under Your Game Accounts.
5. If the client is still missing, confirm the selected WoW account and that a digital order is Complete. Blizzard Support cannot grant beta access or troubleshoot the beta client.
6. For an install or launch error, keep the error text, operating system, build and time together for a reproducible support report.

WoW Forever system requirements: Windows and Mac #

Blizzard publishes separate Forever requirements for Windows and Mac. Both list 8 GB RAM minimum, 16 GB recommended and 128 GB of available SSD space. That storage allowance is not a measured beta download size. Requirements can change during development.

GPU compatibility errors: the architecture cutoff #

Blizzard’s September 17 notice requires AMD Graphics Core Next 1, NVIDIA Maxwell or Intel Skylake graphics architectures, or newer. Its examples exclude Radeon HD 6950, GeForce GTX 760/770/780 and GTX 8xxM, and Intel HD Graphics 6000.

Passing this architecture cutoff does not mean a card meets the full minimum requirements above. Blizzard explicitly describes some compatible older cards as below its minimum specification. An operating-system upgrade alone does not establish GPU compatibility.

On Windows, identify the installed GPU in Settings → System → Display → Advanced display, or Device Manager → Display adapters. Compare the model with both Blizzard’s architecture notice and the full requirements. Kingy has no verified bypass for unsupported hardware.

Mac requirements: Intel and Apple Silicon #

Mac is an officially listed platform. Blizzard names Apple M2 or ninth-generation Intel Core Coffee Lake for its minimum CPU specification; M1 is not listed. A successful community report on another chip does not change that published minimum.

• Both platforms list broadband internet, a keyboard and mouse, and a minimum 1280 × 720 display. A multi-button mouse with a scroll wheel is recommended.
• Minimum specifications are not an FPS guarantee. Kingy has not benchmarked the beta on these machines or verified every supported hardware combination.

Can WoW Forever run on Linux or Steam Deck? #

Blizzard’s Forever requirements list Windows and Mac, with no Linux specification or native Linux client documented there. Kingy has not reproduced a Linux, Wine, Proton or Steam Deck installation for the current beta build.

Compatibility-layer reports are not official support or a guaranteed fix. A useful report needs the beta build, distribution, GPU/driver and compatibility-layer version, plus the exact failure or successful test. No tested Linux setup is available in this guide yet.

Can’t install the beta? Check the symptom first #

The launch client and beta are separate. Blizzard’s “Can’t Install” article says the live game is unavailable before November 4; its beta announcement gives the separate Game Version menu path. A missing launch install button does not prove your beta access is broken.

What is available in week one #

More content and a temporary public Server Slam are planned later; no date for that window is established here.

Known issues checked September 19 #

• Blizzard’s September 18 list says character friends are disabled in beta.
• The minimap can appear partly off-screen; Cooldown Manager implementation varies by class.
• Some fixes are listed for the next build. This does not establish that they are already available.

Wipe, carryover and launch characters remain open questions #

Do not promise a character, name or achievement will survive the beta. Record a beta result as a beta result until Blizzard states what carries forward.

Record the first login so another player can reproduce it #

The beta-day checklist turns these fields into tests for the character matrix, first quests, dungeons and systems. A single successful login can prove that path on that build; it cannot prove every platform, region or account path.

1. Write down the date and time zone, platform, Battle.net app version if visible, game build and selected region.
2. Record the account access path without publishing account identifiers, invitation codes or private order details.
3. Capture the exact client label, ruleset choice, character screen and first error or successful world entry.
4. Separate what the client showed from what an announcement promised. Use the shared labels on this wiki when reporting the result.

KEEP GOING

Your next step.