If the Battle.net launcher opens fine but WoW itself refuses to start or crashes immediately, the first thing to check is your graphics drivers — outdated GPU drivers cause this more often than anything else. Run a game file scan through the launcher (the gear icon next to the Play button → Scan and Repair). Also disable any overlay software like Discord or NVIDIA GeForce Experience temporarily.
Ping jumping to 300–2000ms mid-session is usually a routing issue between your machine and the game servers. Try these steps:
Error codes like WOW51900319 or BLZBNTBNA00000005 typically mean the authentication server is under load or your session token got corrupted. Log out of Battle.net completely, clear the app cache (delete the Cache folder inside the Battle.net installation directory), then log back in. If two-factor authentication stops delivering codes, check that your system clock is synced correctly — time drift breaks TOTP codes.
Stuck downloads or update errors often come from the launcher's cache going stale. Close Battle.net, navigate to %ProgramData%\Battle.net\, delete the Agent folder, and restart the launcher as administrator. Make sure your antivirus isn't blocking the update agent — add Battle.net to the exclusions list.
After patches, outdated addons are the most common reason the UI becomes unresponsive or throws Lua errors. Type '/console scriptErrors 1' in chat to see which addon is breaking. Disable all addons via the character select screen, then re-enable them one by one to isolate the culprit. Keeping a manager like CurseForge up to date saves a lot of this debugging.