World of Warcraft: Forever Beta - Login Queue Disconnects
The failure loop: you sit the beta queue, the timer hits zero, the client authenticates, then you disconnect and land at the back of a longer line. The Sept 27 population-cap and queue-fill fix cleared most of it, but these are the steps that still work if you are getting kicked.
The goal: survive the handoff from queue to realm without losing your place. If you reach position 1, see "retrieving realm information," then disconnect, that is the login-metering failure - not your authenticator. EU testers disabled the authenticator completely and got the identical dump.
1Stay in the Client Until the Handoff Finishes
-
1
Do not alt-tab into a sleep state, change networks, or close the client mid-countdown
Players who dropped the window mid-queue lost their place. There is no skip - relaunching near the end of the timer did not save a spot in this beta.
-
2
After any Blizzard-side restart, fully relaunch before you queue
Lag/disconnect fixes required a full client restart to apply. Queueing on an old process can burn a full wait on an already-patched build.
-
3
Kicked exactly when the queue ends while everyone reports the same? Stop requeueing
During the Sept 17 crush, immediate requeue just stacked another 30k line. Wait for the realm to settle or try off-peak.
2Outside the US? Fix the Route Before You Queue Again
Beta realms are US-only. Non-US players who cleared the queue still got latency spikes (hundreds of ms, world MS in the thousands) and disconnects straight back into line.
-
1
Route the beta client through a US exit - Chicago or New York
Not a generic WoW preset. A tester in Turkey got a stable ~160 ms via Chicago and stopped disconnecting; Western Europe reported ~100 ms.
-
2
Point the tunnel at the beta executable
For example
C:\Games\World of Warcraft\_classic_beta_\WowB.exe- it must beWowB.exeunder_classic_beta_, not the retail client.
3Turn Off "Optimize Network for Speed"
-
1
In game: Menu > Options > Network > disable "Optimize Network for Speed"
-
2
Fully quit and relaunch so the client picks it up
Players who could not use a VPN reported fewer freezes and disconnects after this. Use it when the VPN path is unavailable - some still disconnected after only this change.
4If the Client Dies in Queue or Shows No Realms
-
1
Crash a few seconds after the queue appears
Reinstall and repair did not fix it for players who posted. No reliable client-side fix beyond waiting out the server-side patch and relaunching.
-
2
No realms are currently available (WOW51900309): restart the PCClosing Battle.net alone leaves
WowB.exerunning. Kill it withtaskkill /f /im WowB.exein PowerShell, or reboot - then the client updates and logs in. Players already in the world were often unaffected. -
3
Character screen loading forever after you finally get in
Alt-F4 was the only exit players had - but it sends you back to the queue, so only do it if the screen is truly stuck.
5Decision Points
| Symptom | Do this |
|---|---|
| Kicked exactly at queue end, authenticator irrelevant, widespread reports | Wait for the realm to settle or go off-peak. Instant requeue stacks another line. |
| Kicked with a ping spike from outside the US | US route on WowB.exe, or disable Optimize Network for Speed, then queue once. |
| Realm list error or frozen login screen | Reboot or kill WowB.exe, then log in. Do not sit a queue on a half-dead client. |
Mistakes That Cost You Another Queue
- Blaming the authenticator. Tested both ways - the disconnect was identical.
- Alt-tabbing or letting the PC sleep during the countdown.
- Using a normal WoW VPN profile. It must target the
_classic_beta_executable. - Closing only Battle.net when realms disappear.
WowB.exestays alive - kill it or reboot. - Remaking a character that fell through the world. Beta characters were not on the website unstuck list - delete was the only recovery. That is a different disconnect from the login queue.