Installation troubleshooting
Can't Install WoW Forever? Grey Button & Client Checks
WoW Forever cannot be installed yet? Check the client, grey Install button, Windows errors and Launching loops. Beta is closed; release access is separate.
If Battle.net says "This game cannot be installed yet", select World of Warcraft: Forever under World of Warcraft → Game Version. Check the selected WoW account and its game time. The beta is closed; the live game uses the entry in Blizzard’s starter guide. Use the checks below for a grey Install button, a launch loop or a ruleset error.
If WoW Forever says "This game cannot be installed yet" or Install is greyed out, check the selected client, WoW account and access window first. For reservation and launch preparation, Blizzard specifies World of Warcraft: Forever, without Beta or Stress Test. The beta is closed, as confirmed on October 23; its unavailable install does not prove a Windows or download fault.
Release check — November 6: Blizzard now lists Forever as live. Select World of Warcraft: Forever, not Beta or Stress Test, and the WoW account that holds your access. The reservation/preload examples below describe earlier stages: a new grey Install button should be diagnosed against current account and launcher messages, not the expired name-reservation window. For code access, follow redemption and eligibility checks; an Epic upgrade is not a universal installation requirement.
Start with release-client selection, preload and account checks, or the diagnostic record. On a handheld, use the Steam Deck setup checks; Windows-specific troubleshooting is not a SteamOS installation recipe.
Looking for a Steam download? Blizzard’s current starter guide directs players to the Battle.net desktop app, then World of Warcraft → World of Warcraft: Forever. That is the documented download route. Steam Deck setup is a separate device question, covered in the linked handheld guide.
Find your installation or launch problem
| Symptom | First check | Steps |
|---|---|---|
| Install is greyed out or the game cannot be installed yet | Selected Game Version, account entitlement and the published access window | Unavailable install checks |
| Your OS does not meet requirements, including BLZBNTAGT000009CF | Exact error code, Windows updates and compatibility mode | OS requirement checks |
| Play changes to Launching, then returns to Play | Pending updates and current launcher notices before a reinstall | Play-loop checks |
| The game opens, then disconnects with WOW51900102 | Correct client, access window and Blizzard's current service notices | Connection and server checks |
| No ruleset available / WOW51900309 after the game opens | Region, ruleset and current notices; downloading is no longer the failing stage | Ruleset availability checks |
| Valid license required / WOW51900337 during reservation | Selected WoW license and the benefit it holds | Reservation access messages |
Which client do I need: Beta, Stress Test or Forever?
Installing a client does not grant an entitlement or prove servers are open.
| What you want to do | Client or launcher entry | What to check |
|---|---|---|
| Identify the completed beta install | World of Warcraft: Forever Beta, under In Development | The beta is closed; an old entitlement does not reopen it. See the confirmed beta end |
| Identify the previous open stress-test install | WoW: Forever - Stress Test was the event label | The Server Slam schedule; an installed entry is not evidence the event is still running |
| Prepare for name reservation and release | World of Warcraft: Forever | The name-reservation requirements and dates and the release schedule |
The official reservation instructions are Battle.net → World of Warcraft → Game Version → World of Warcraft: Forever → Install. Select the intended WoW account as well as the right version. Follow the launcher's actual availability message; if the option is absent, check updates and the qualifying account before reinstalling.
Some players report that the Stress Test label has changed to Forever. That is a player observation, not our confirmation of a universal client conversion, preload opening or file-reuse policy. Do not download Beta solely on the assumption that it will reduce the final download. We have not independently verified how many files will be reused or the final download size.
If Battle.net says the game cannot be installed yet
For the old Beta entry, stop here: the test has ended. For the release entry, follow the launcher's availability message and check the qualifying WoW account. A grey button alone does not establish an OS fault or a universal preload opening.
- Fully exit Battle.net and make sure its Agent process has also closed, then reopen it.
- Confirm the selected WoW account and the entitlement required for what you are trying to do, especially Early Name Reservation.
- Check for a Battle.net update and restart the computer.
- Check Blizzard's current forums/status messaging before repeatedly reinstalling the game.
Some players reported transient entitlement or network-path behavior during the beta launch. A workaround that helped one player—such as changing networks—does not prove a universal cause.
If Battle.net says your OS does not meet minimum requirements
A number of Windows 10 and Windows 11 users have reported BLZBNTAGT000009CF or a message that their OS is below the minimum even when the displayed versions appear compatible.
Use the safe path first:
- install pending Windows updates;
- update graphics drivers;
- make sure the executable for the selected WoW version is not being forced into an old Windows compatibility mode;
- restart Battle.net after the updates;
- search Blizzard Support for the exact error code.
One forum user reported resolving the issue after moving to Windows 11, but that does not establish Windows 11 as a universal requirement. Do not upgrade an operating system solely because one community report did.
If Play changes to Launching and returns to Play
Blizzard's general World of Warcraft troubleshooting recommends restarting the computer, updating drivers and the OS, checking software conflicts/security exceptions, and reinstalling the Battle.net app if simpler steps fail.
Recent Forever forum reports also show this symptom during periods when players were unable to retrieve realms or when the client needed a pending update. Check whether the issue is widespread before repeatedly reinstalling everything.
What this guide does not recommend
This guide does not recommend unofficial command-line install methods or disabling Windows security protections. During a beta, launcher state and entitlement problems can change server-side, and aggressive local changes can make diagnosis harder.
For access and beta dates, use the WoW Forever Beta guide. For live ruleset/server architecture, use WoW Forever Servers.
Looking for the stress-test download?
The reported WoW: Forever - Stress Test entry is covered in the Server Slam guide. Check the exact client label before applying ordinary Beta troubleshooting; download availability does not guarantee the test is open.
Pre-download, client choice and disk space
Confirm the release entry before checking storage. The old Beta and Stress Test entries do not establish final-client availability.
Before installing:
- Read the selected version, availability message and destination folder. Do not confuse Modern, Classic, Beta and Stress Test labels.
- Compare free space on the destination drive with the launcher's current requirement, not just the compressed download size. Keep room for patching and temporary files; this guide does not invent a fixed extra-space percentage.
- Check the current Battle.net Shop requirements. That listing required account access during our review, so we do not present a separately verified GB requirement or fixed download size here. Beta build sizes can change.
- Do not delete another WoW installation or rename folders to force access. If Battle.net does not offer the intended client, resolve the version or entitlement question first.
- Before uninstalling Beta or moving files, follow the addon and settings backup checklist. Backing up local settings does not transfer beta characters, progress or access rights.
Blizzard's GPU architecture notice is a compatibility floor, not the full minimum specification. A card meeting that architecture boundary may still be below the game's actual minimum. Check full requirements before deciding an OS upgrade or hardware purchase is necessary.
Can I preload without an active subscription?
A subscription, a reservation upgrade and download permission are different checks. Reviewed November 2: the official reservation instructions identify the release entry, and we have not verified a universal preload opening or date. Follow its availability message for your selected WoW account.
| Your situation | What it establishes |
|---|---|
| No subscription and no eligible upgrade | Universal download permission has not been verified here; follow the selected release entry's availability message |
| Reservation upgrade, no subscription | Reservation has a game-time exception; check your account and benefit. This does not establish universal download or launch-play eligibility. Do not buy again to test a grey button |
| Active subscription or Game Time | Ordinary Forever access is included, but installed files do not prove an open service |
| Invite-A-Friend code | Check the November 4–11 offer and recipient restrictions; it does not promise reservation or universal preloading |
- Have WoW1 and WoW2? Select the account that actually holds the relevant purchase or benefit. Those labels alone do not identify a trial, subscription or eligible account. Check your order and account details before assuming the entitlement is missing.
The October 25–26 preload discussion contains differing player experiences. It is evidence of an account-access question, not an official preload date or a supported force-install method.
Still cannot install? Record the failing stage
If Install works but Play asks for access: open the account details for the selected WoW license, not just the Battle.net profile. Compare active Subscription/Game Time or the eligible November 4–11 invitation with the license you selected. Reservation ownership and a closed-beta entitlement answer different questions. If you already redeemed a code, record the redemption result and selected account before contacting Support; keep receipts and the code private. This check does not promise that every account can preload without access.
Before another reinstall, note whether failure occurs at version selection, Install, patching, process startup or ruleset connection. Record OS/Battle.net versions, the exact Game Version label, pending updates, error text and time with time zone. For storage faults, compare destination-drive free space with the launcher's displayed requirement, not a beta download estimate. Keep account identifiers, codes and receipts private.
On Deck, add the device/environment record. If the game opens but returns a realm or license message, follow the symptom table before changing installations.
Updating is a different stage from installing. If Battle.net reports BLZBNTAGT0000138F, save the complete message and identify whether the launcher itself or the selected game is updating. We have not verified a Forever-specific cause for that code. Record the failing percentage, drive space and pending tasks, then use Blizzard Support for that exact error rather than applying a fix written for another game or OS.
Desktop shortcut opens the wrong client? First launch the intended Forever entry from Battle.net. Compare the shortcut's destination with that installation before replacing it. A shortcut does not grant account access, and an old Beta shortcut is not evidence that release files are missing.
Sources
-
Blizzard — the Forever client selection for Early Name Reservation
-
Player reports — changing launcher labels and file-reuse questions, not confirmed policy
-
Blizzard Support — World of Warcraft technical troubleshooting
Battle.net never created a desktop shortcut
On Windows, launch the World of Warcraft: Forever entry in Battle.net to confirm which copy is installed. Next to Play, open the game options and use Show in Explorer if available, then find the executable for the Forever installation you just opened. Use Windows’ Send to → Desktop (create shortcut) or create a shortcut pointing to that file, and check its target under Properties. See the Windows shortcut steps for both menu options, and keep Battle.net as the entry point for updates and account checks.