Technical help
Azeroth Survivors Not Loading
Start with the error message. HTTP 429 or a too-many-players notice points to request limits; a WebGPU or graphics-card message points to the browser's graphics path. These need different responses.
The table below follows the original game's publicly served launcher. A blank canvas alone is not enough to tell which branch failed.
Match what you see
| Message or symptom | What it tells you | First action |
|---|---|---|
| HTTP 429 or too many people are playing | The web service is limiting requests | Try later, or follow the original Windows download entry |
| This browser has no WebGPU | The required browser API is unavailable | Update or use a current browser recommended by the original launcher |
| WebGPU found no usable graphics card | The API exists, but the launcher did not obtain an adapter | Check graphics acceleration and, on a dual-GPU Windows laptop, the browser's assigned GPU |
| WebGPU device lost | The graphics device stopped responding during the session | Reload once; if it repeats, follow the device-specific checks below |
| The game failed to start in this browser | Startup threw an error | Record the text in parentheses and any console error; use the more specific branch when present |
| Windows EXE opens a console and immediately closes | The downloaded program did not finish launching | Check the extracted game folder and use the Windows section below |
Request limits: HTTP 429
The original launcher's error handler displays its busy notice when a startup error includes HTTP 429. This does not mean your graphics card is unsupported.
Use one of these routes:
- Wait and try the original site later.
- Follow the Windows download instructions.
- Check the original community Discord for release or availability information.
Repeatedly refreshing does not remove a service-side request limit. A GPU setting also cannot remove it.
For a recorded example, Ghost Gaming Insider's video at 04:30 discusses the site's busy notice and the alternative Windows route over gameplay footage. This is historical footage, rather than a live status indicator.
Chapter illustration from the same recording. Clicking play connects to YouTube. Watch on YouTube ↗
No WebGPU or no usable adapter
The original game page recommends current Chrome, Edge or Safari. Its launcher checks for WebGPU and then requests a graphics adapter.
If WebGPU is missing: update the browser and operating system, or try another current browser supported on your device. The site's own Linux Chrome message mentions its WebGPU flag; treat that as platform-specific advice, rather than a universal fix.
If no usable graphics card is found:
- In Chrome or Edge, check the browser's system settings for graphics acceleration and restart the browser after changing it.
- On a Windows laptop with integrated and dedicated graphics, open Settings → System → Display → Graphics, select the browser and try High performance.
- Restart the browser completely before testing again.
- If it still fails, record the browser's graphics diagnostics and graphics-driver version. Chrome's launcher guidance points to chrome://gpu for the reason WebGPU is disabled.
The goal is to move past the graphics warning and reach the game menu. Obtaining an adapter does not guarantee that the rest of the game will run successfully.
The game loads, then freezes or loses its graphics device
The launcher distinguishes a lost graphics device from a missing one. It specifically includes advice for dual-GPU laptops and a separate message for phones.
Reload once. If the failure returns on a Windows laptop, keep the browser assigned to the chosen GPU and check the graphics driver. On a phone, a repeated device-loss message can indicate a driver failure during shader preparation; use the mobile guide to decide whether to try another route.
The current launcher saves a graphics-crash report and prints a previous report in the browser console on the next load. When reporting a fault, capture the relevant error and device details, and review the report for personal information before sharing it.
Older iPhone fullscreen errors
The original player discussion includes a webkitRequestFullscreen error on iOS. The currently served launcher contains a guard for browsers without that fullscreen method.
An old report therefore does not establish that every current iPhone still has the same startup bug. Reload the original site and capture the error you actually receive. If it is now a GPU error, troubleshoot that branch instead of following an obsolete fullscreen workaround.
Windows archive or immediate-exit failures
Confirm that the archive downloaded completely and that the executable remains with the extracted Data folder. The download guide separates archive problems from a security block or a failed launch.
A co-op message mentioning coop-lab or shutdown_drain_finished belongs to the Together package in the community discussion about that package. It needs that package's version and logs, rather than generic browser advice.
Still stuck? Record enough to identify the failure
Collect the route you used, the visible game version if available, operating system, browser version, graphics hardware, exact error and the point where loading stopped. State whether the menu appeared or the world ever rendered.
This guide uses the original site's launcher and the original player discussion. It does not report a successful test on your device.