WoW Forever beta: access, installation and system requirements

The beta is closed: an entitlement does not reopen it #

The beta closed October 23. The following entitlement checks describe the former test; they do not reopen it. 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.

Current access: live since November 4 #

WoW Forever went live in all regions on November 4 at 3pm PST / 23:00 UTC. Blizzard closed the beta on October 23, and name reservations ended November 3. The dated beta instructions and observations below are historical, not a way to join the closed test or proof of launch behavior.

October 9 warning: stuck loading after the Tram, a flight or zone travel #

Beta players report characters stuck at 100% loading or unable to log back in after Deeprun Tram, flight and zone transitions. Reports continued October 9, including a reply at 08:12 PDT. Some other characters still load; recovery is inconsistent.

Consider postponing these transitions on a beta character whose progress you want to keep. Permanent save loss and a universal fix are unconfirmed. Graphics changes and reinstalling are not established fixes for this cluster.

Update to client 70425 before comparing the October 15 beta #

When realms came back on October 15, Blizzard's game producer said to exit and update through the Battle.net app if you are not on client 70425. The October 15 notes change every race's racial abilities and many class talents, add a new-player tutorial and make Auto Shot and wands wait 0.5 seconds while you stand still.

Record the installed build before comparing older results. Build 1.60.1 69977 belongs to the September 22/23 notice and is history. Officially reported changes still await independent gameplay tests.

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.

Closed-beta dates and former playable limits #

Blizzard’s October 20 notice gave the final dates: the Stress Test on October 21, then the beta reopened until it closed for good at 10:00 a.m. PDT on October 23. That replaced the older October 21 and October 22 labels.

Any WoW account could join the October 21 Stress Test, with no subscription; Blizzard moved it from October 19 on October 16. It ended at 6:00 p.m. PDT, 9:00 p.m. EDT and 03:00 CEST. In Taipei and Korea it ran from 5:00 a.m. and 6:00 a.m. on October 22, and in Sydney from 8:00 a.m. to noon AEDT. Blizzard said the Roleplay ruleset was unavailable for it, and calls the deletion a complete wipe, names included, so nothing made that day carries over.

On October 22 Blizzard confirmed the 10:00 a.m. PDT (19:00 CEST) close again and opened a final 24-hour celebration in the starting zones. It warns that items and events from that celebration won't be in Forever after launch.

On October 23 Blizzard confirmed the beta is closed. It is working on priority issues and the game service until launch, and opens character creation on Tuesday, October 27.

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.

Historical beta installation 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 closed beta.

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 beta closed October 23. The historical beta selector and troubleshooting below do not reopen it. Forever went live November 4 at 3pm PST / 23:00 UTC; check current Battle.net service and install notices rather than treating a missing beta button as a broken entitlement.

Closed-beta dungeons and historical opening ranges #

October 8 added City of Dalaran to beta testing. The cap was level 30, announced October 1. Before the beta closed October 23, Blizzard made Excavation Site: Wetlands (26–31), Razorfen Downs (25+) and Uldaman (30+) available alongside Ragefire Chasm, Hall of Thanes, Ruins of Lordaeron, Wailing Caverns, Deadmines, Shadowfang Keep, Stockade, Blackfathom Deeps, Gnomeregan, Razorfen Kraul and Scarlet Monastery. Announced availability is not a tested entry requirement.

The September 17 opening list gave Hall of Thanes as 13–18 and Ruins of Lordaeron as 15–20. Those historical content ranges are not minimum-entry or group-readiness guarantees. The public Stress Test ran October 21 before the beta closed October 23; it is not a future sign-up window.

Disconnects: check the date of the server notice #

On September 25, Blizzard acknowledged server issues affecting some beta testers, then announced brief realm restarts to apply stability fixes. This historical notice does not indicate a current outage or prove every connection problem is resolved.

For a new disconnect, check current official notices first. Record the time and time zone, region, client build and exact error before reporting it. Do not assume a server-side incident requires reinstalling the game.

Playing the beta from Europe: Blizzard said on September 21 that it had fixed its side of the early EU routing problems, which hurt testers' movement, interaction with the world and sometimes their connection. If you still lag, Blizzard points to your internet provider's routing or to firewall-type software slowing or blocking the game, so check those first.

Is the beta down? The weekly maintenance pattern #

So far Blizzard has taken the beta offline on Thursdays to deploy each new build: September 24, October 1, October 8 and October 15. Blizzard expected each to last a couple of hours or more; on October 8 it started at 9:00 a.m. PDT, and on October 15 at 1:15 p.m. PDT, later in the day. Development notes and known issues follow on the forum; for October 15, the full notes followed the same evening, and realms returned on client 70425.

Not every outage is a Thursday build. On Wednesday, October 14, Blizzard took the beta offline at 8:00 a.m. PDT for internal tests and said about 50 minutes later that it was coming back online; it didn't announce a new build.

Shorter realm restarts for fixes have come on other days, such as September 25, October 5 and October 6. Blizzard described those as quick restarts, with an in-game warning first. Blizzard announces both kinds in Beta Realm Maintenance threads on the official forum, so check there; past Thursdays don't guarantee future dates.

What is the Forever Open tournament? #

A creator-run 1v1 dueling tournament on the Forever beta, hosted by Tips Out, Esfand and Xaryu. Blizzard doesn't run it. Wowhead reports a $100,000 prize pool and Horde-only characters on the PvP ruleset, with online qualifiers on October 17 and the finals on October 18.

Registration closed early, on October 2, after about 4,000 sign-ups, so you can't enter now.

Known issues checked October 8 #

The October 1 issue reply lists late chain-casting effects, behind-target parry/block, oversized installation, gamepad layout resets and broken Liminal Passage. The older parent still lists character friends, Bear Form armor, Arcane Missiles and spell-queue problems; no independent fixed-build result is established.

October 1 says party leaders should no longer transfer when party composition changes. This does not guarantee placement for every member. October 8 expands Cooldown Manager to all classes, racials and trinkets; consumables are still planned for a later patch.

Escaping Ban’ethil and Snowbound remain explicitly marked resolved in the September 24 reply. Other next-build promises, including Waylaid Crates, are not automatically confirmed by age.

• The older issue-list body still lists character friends as disabled; the September 24 reply adds party changes that may move the world instance.
• Cooldown tracking and the Stormwind minimap have newly listed limitations. Check actual ability buttons before concluding that a missing tracker means an unavailable spell.
• Escaping Ban’ethil and Snowbound are officially marked resolved. Other next-build promises, including Waylaid Crate handling, are not automatically confirmed by that update.

Beta progress does not carry into launch #

Blizzard Support now explicitly states that beta progress will not carry over after official launch. The test is now closed; beta levels, equipment and Legacy progress are not secured launch progress.

The precise cleanup time and name-release policy remain unknown. The complete beta region and ruleset screens still need client verification.

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.