Guild Wars 2 · Known issues & fixes

Guild Wars 2 Known Issues, Workarounds and Fixes

Official low-risk Error 42 checks, Steam account/client restrictions, Code 1101 reporting and the displayed America login-region explanation.

PC
Documented workaround

Network error Code 1101 on a Steam account

Platforms: PCEvidence checked

The Steam FAQ separately identifies Code 1101:4:5:1750:102 with ErrAuthDataError/AuthSrv and asks affected players to contact the Guild Wars 2 support team. Keep the complete code when reporting it rather than treating it as interchangeable with Error 42. [2]

Documented steps

  1. Send support the Steam Support ID, Guild Wars 2 display name, character names, summary and exact error text using the support channel listed in the FAQ. [2]
Documented workaround

Error 42 interrupts login, guild or chat access

Platforms: PCEvidence checked

Error 42 is an interruption reaching the account servers, which handle login and social systems. It can occur before login or after entering the game, so a guild or chat disruption can belong to the same connection problem. [1]

The source includes both local-network and server-side causes. The code by itself does not prove that your router or firewall is the fault. [1]

Documented steps

  1. Completely close the game and client, wait five minutes, then relaunch and retry. [1]
  2. If the problem continues, use the support page’s PC reboot check. [1]

Limits & applicability

  • A larger service outage can take longer than the initial wait. Check the publisher’s service communications when the problem persists across players. [1]
Officially acknowledged

Steam account management shows America for a European shard

Platforms: PCEvidence checked

The FAQ explains that Steam login verification runs through an America-based service while game accounts and game servers remain regional. The America display in account management does not alone prove that a European character’s game data has moved. [2]

For a player on a European shard, the FAQ specifically states that the game data is still in Europe despite that displayed login region. [2]

Officially acknowledged

Existing ArenaNet account will not log in through Steam

Platforms: PCEvidence checked

ArenaNet and Steam account/client logins are distinct. An account created through the Guild Wars 2 website cannot use Steam login, and a Steam-created account uses Steam login. This is a documented account restriction, not a lost-character diagnosis. [2]

Documented steps

  1. For the existing website-created account, continue using the Guild Wars 2 website client. [2]

Sources & verification

Platform and version details belong to the individual issue or guide section. A documented workaround may not resolve every case.

  1. Error Code 42 official-supportRetrieved
  2. Steam FAQ official-supportRetrieved

Report a correction · More Guild Wars 2 coverage