Login errors & queue: fixes

When: Anything fails on launch night.

1. Check Blizzard’s customer support account @BlizzardCS on X and the World of Warcraft forums for a known outage. On launch night most errors are server-side.
2. If others report the same problem, wait. Reinstalling or resetting your router does not fix a server outage.
3. Restart the Battle.net app once (fully quit it from the system tray or menu bar), then log in again.

When: You see a queue position and an estimated wait.

1. Leave the client open. Closing the game or logging out of Battle.net normally loses your place.
2. Make sure your PC will not sleep or drop Wi-Fi while you wait, because a disconnect also loses your place.
3. Blizzard has not said whether Forever queues are per ruleset or per region. Do not create characters on another ruleset to dodge a queue: you cannot group across rulesets, and changing ruleset later means a new character.

When: You get past login but cannot enter the world, or the list shows the realm offline.

1. This means the game servers are not accepting players right now: launch, a restart, maintenance or overload. Your client is fine.
2. Wait a few minutes and try again. Retrying every few seconds does not get you in faster.
3. If it lasts, check @BlizzardCS for a maintenance or restart notice.

When: You get in, then lose connection with error WOW51900319.

1. Blizzard says this code means the game lost its connection to the servers. First check @BlizzardCS for a server problem.
2. If the servers are fine: restart your router or modem, close downloads and streams that compete for bandwidth, and turn off any VPN.
3. Run Scan and Repair (below) to rule out damaged files.

Source: Blizzard SupportBlizzard

When: You see WOW51900102 while logging in or creating a character.

1. Players reported this code on the first night of name reservation. We have not found a Blizzard article explaining it, so we do not guess what it means.
2. Treat it as a connection problem: check @BlizzardCS for a known outage, wait a few minutes and try again.
3. If it continues while others can play, restart the Battle.net app and your router, turn off any VPN, and run Scan and Repair (below).
4. Still failing: open a ticket with Blizzard Support and quote the exact code and the time it happened.

When: The Battle.net app shows a code beginning with BLZ before the game starts.

1. BLZ codes come from the Battle.net app, not from the game. Search the exact code on Blizzard Support, since each code has its own article.
2. General fixes that solve most of them: quit and restart the app, log out of Battle.net and back in, turn off VPN or proxy, and allow the app through your firewall or antivirus.
3. If the app will not update or log in at all, reinstall the Battle.net app (not the game).

When: Your character list is empty, a reserved name is gone, or friends cannot find you.

1. In the Battle.net app, check the region selector next to the Play button (Americas, Europe, Asia and so on). Characters and names exist per region.
2. Names are reserved per region, so a name reserved on Americas will not show up on Europe.
3. Then check the ruleset. Characters are tied to Normal, PvP, Roleplaying or Roleplay-PvP, and you only see friends on the same ruleset in the same region.

When: Lua errors, broken action bars or a frozen screen after login.

1. At character select, open AddOns, choose “Disable all” and log in. If the error goes away, an addon caused it.
2. Re-enable addons one by one. Use builds that list WoW Forever as supported; Classic Era builds may not load or may throw errors.
3. Do not tick “Load out of date AddOns” to silence a warning on launch night. Update the addon instead.

When: Errors persist with all addons disabled, or settings are corrupted.

1. Quit the game completely. Temporarily remove any addon manager, because it would put the files back.
2. In the Battle.net app, click the cogwheel next to Play and choose Show in Explorer (Windows) or Show in Finder (Mac).
3. Open the World of Warcraft folder, then the folder for the game version you are fixing.
4. Rename Cache, Interface and WTF to CacheOld, InterfaceOld and WTFOld, then start the game. Your keybinds and addon settings reset; the old folders stay as a backup.
5. If errors continue, Blizzard’s article also lists the /console cvar_default command to reset console variables.

Source: Blizzard SupportBlizzard

When: Crashes on start, missing files, or after a failed patch.

1. In the Battle.net app, click the cogwheel next to Play and choose Scan and Repair.
2. Let it finish, then start the game. It downloads only damaged or missing files, so it is much faster than a reinstall.