Antivirus and firewall block WoW: opening access
Vanilla WoW Classic 1.12 · x5 realm · wowx5.ruTwo common issues: antivirus deletes Wow.exe after extraction (false positive), or the firewall blocks the game from the server. Both are fixed by adding the game to exclusions.
Step 1: add the folder to antivirus exclusions
If Wow.exe disappears after extraction, it's a false positive. Open your antivirus (or Windows Security → Virus protection → Exclusions) and add the whole WoW folder. Then re-extract the client.
Step 2: allow the game in the firewall
Control Panel → Windows Defender Firewall → Allow an app → find Wow.exe and check "Private" and "Public". If the game isn't listed — "Allow another app" and point to Wow.exe.
Step 3: check the ports
WoW Classic uses:
| Port | Purpose |
|---|---|
| TCP 3724 | Login and realm |
| TCP 8085 | Game world |
Outbound connections are usually open. On a strict corporate or router firewall, allow these ports for play.wowx5.ru.
Step 4: temporary disable to test
To confirm protection is to blame, disable the firewall and antivirus for a minute and try logging in. If it works, turn protection back on and add targeted exclusions (don't leave everything off).
Step 5: third-party shields and VPN
- Some internet-security suites have their own firewall — look for exclusions there too.
- Disable VPN and proxy — they often break the realm connection; see disconnects.
- Verify your realmlist.
FAQ
Why does antivirus delete WoW files?
Old clients and private-server launchers often false-positive as threats (heuristics). The files are safe — add the WoW folder to antivirus exclusions, or it will delete Wow.exe after every extraction.
Which ports does WoW Classic need?
The client uses TCP ports 3724 (realm/login) and 8085 (world). Outbound connections are usually open by default; problems arise when the firewall or antivirus blocks Wow.exe specifically.
How do I know the firewall is at fault?
If the game reaches the character screen but won't enter the world, or won't connect at all while another device/network works, local protection is blocking it. Disable it temporarily to test.