An error code is a better starting point than a general description that the game is broken. Preserve it exactly, including the prefix and digits. Two similar-looking codes can lead to different checks, so do not replace a specific message with a workaround intended for another category.
The table is a compact paraphrase of Kefir’s reference. The rest of the guide explains how to organize a troubleshooting attempt without changing unrelated settings or losing the evidence you need for a report.
Official error-code lookup
Find the exact code, then follow the matching first check. This is a reference table, not a claim that the suggested action guarantees a repair. Use the official source link for the complete wording and any additional conditions.
| Code | Category | First check |
|---|---|---|
| E-0101 / E-0110 | Connection / startup data | Check connectivity. |
| E-0102 | Blocked or corrupt download | Check network / security interference. |
| E-0124 | Asset loading | Verify game files. |
| E-0201 | Lost server connection | Check connection; restart. |
| E-0301 / E-0302 | Old client | Restart Steam; update. |
| E-0303 / E-0304 | Mismatched game data | Wait 10–15 min; verify; update. |
| E-0401 | Steam authentication | Check online account session. |
| E-0403 / E-0404 | Authorization / EOS | Verify; inspect security settings. |
| E-0405 | Steam or library blocking | Check Steam / quarantine. |
| E-0501 / E-0502 | Anti-cheat | Launch through Steam; verify. |
| E-0601 | Input devices | Use connected physical inputs. |
| E-0904 | Internal error | Restart; report if persistent. |
Use one controlled check at a time
Record the original code and what you were doing just before it appeared. Choose one action from the relevant category, complete it and repeat the same launch or connection attempt. Note whether the code changed, disappeared or remained identical.
Changing several things together makes it harder to know what helped and harder to describe the result to support. An improvement after a large bundle of changes is not evidence that every step was necessary. Keep the test small enough to explain.
- Capture the code and the preceding action.
- Choose the matching category from the table.
- Complete one relevant check.
- Retry the same scenario once.
- Record the result before choosing the next action.
Finish updates and file checks before judging the result
For Steam file verification, open the game’s Properties, select Installed Files and choose Verify integrity of game files. Allow it to finish and complete any required download before launching again. A partially completed installation is not a clean test of the next attempt.
Use the Steam library for the launch so the client and required components follow the intended route. If the same error returns, keep the result instead of immediately replacing it with a full reinstall. Read loading and crash troubleshooting if the failure changes into a different symptom.
Keep account and network evidence separate
Check the Steam account actually in use and whether Steam is operating online. For a connection problem, test ordinary internet access and consider whether the connection requires a guest-network sign-in. These checks answer different questions, so keep their results separate in your notes.
Do not share passwords or authentication codes with someone offering to repair an account. If you compare another trusted network, record that comparison rather than declaring one provider universally incompatible. Use official server notices for service-side evidence.
Handle security and input checks narrowly
If the official category points to a security conflict, inspect the relevant application’s message or quarantine rather than permanently disabling protection. Keep any change specific and reversible, and restore protection after a diagnostic test. Do not install an unofficial anti-cheat bypass or a repair executable from a discussion comment.
For an input-related symptom, test the actual keyboard and mouse connection and record whether remote access or streaming is involved. A local input test is different from proving that a platform or streaming service is fully supported. See platform and requirement information for that distinction.
E-0601: check physical keyboard and mouse detection
This code calls for an input-device check, not a general server-outage assumption. Test a connected physical keyboard and mouse directly on the PC running the game. If the original attempt used remote access or cloud streaming, record that context before comparing a local launch.
Keep the result specific: whether the physical input was detected and whether the same code returned. A successful local test does not establish that every remote service is supported, and changing servers does not answer an input-detection question.
E-0904: preserve the internal-error evidence
Restart for this unexpected internal error and keep the exact message if it recurs. Record what happened immediately before the dialog: the same interaction failing repeatedly is useful evidence for support.
Do not assign an invented cause to the code or replace a reproducible report with an unrelated repair download. Send the message and the short sequence that produced it through the official support route. Include the checks already completed so the next person can distinguish a fresh incident from a repeated attempt.
Send the code and the reproducible sequence
A useful report includes the exact code, the action before it, the checks already completed and the result of each. For a crash, add PC specifications and the message text. For a character-related issue, use the UID through the official support route when requested.
Kefir describes finding the UID under the character name after pressing Esc. Keep account information in the official channel rather than posting it with an unrelated public screenshot. The point of the report is to preserve a clear incident, not to overwhelm support with a list of every workaround you found.
- Exact code and message text
- Server or region context if relevant
- Steps that reproduce the error
- Checks performed and their results
- PC specifications for a crash
- Screenshot or short video of the actual symptom
Error Codes FAQ
01What if my code is not in the table?
Keep the exact text and contact official support with the steps that produced it. Do not invent a meaning based on a similar-looking number.
02Should I reinstall for every error?
No universal reinstall step is established here. Start with the matching category and finish its controlled checks before making a larger change.
03Can I bypass anti-cheat to get past a code?
Use the official Steam launch and support process. An unofficial bypass is not a documented repair and can create a separate account or security problem.
04What if the code changes after a check?
Record the new code as a new result and use its category. A changed symptom is useful evidence; do not discard it because it differs from your first screenshot.
Sources & useful references
Game rules below are linked to their official references. Tactical suggestions in this guide are practical advice, and do not promise a particular payout or outcome.