Interface & appearance · Interface & services
Technical support
The classic client needs write access for local files, and protected installation folders can cause connection or update failures.
Practical guide
3 steps for this topic- Install or repair from the current official distribution and keep the client in a location where it can write patches and local settings.
- Reproduce the problem after a clean restart and record the exact error, action, client version, and whether the issue affects login, patching, display, or one character.
- Use official support for account or server problems and never send a password, registration token, or unknown diagnostic executable to another player.
Key details
Keep these with the route- Common local issue
- Protected installation folders can block the classic client from updating or saving files.
- Safe escalation
- A concise reproduction and screenshot are more useful than repeatedly reinstalling modified clients.
Check the living world.
The underlying system is stable, but exact prices, schedules, laws, event rewards, availability, policies, or community rules can change. Current in-game dialogue and official notices win.
Detailed reference
3 concrete notes- Use the current official installer and place the client where the Windows account can write settings, patches, and screenshots. Protected Program Files permissions are a common update failure.
- Try the official client cleanly before changing compatibility or administrator settings. Record the exact error, client version, install path, and whether the failure occurs before or after login.
- Never solve a patch problem by replacing the executable with an unknown multi-instance or resizable client. Account and server-side problems belong in an official support request.