AION 2 Error Codes: Steam 1138:100134, NCGUARD Block Codes and 0xFA000103

Save the log first

This guide covers the AION 2 Global PC release through Steam and PURPLE. NC’s NCGUARD error tables and community launch-error reports were reviewed on 28 October 2026. We have not reproduced the errors in a running client.

Before you close any error window, save the log if the popup offers a Save button, and screenshot the full message including the numeric code. A short code after the error name points to a specific cause, and support needs the exact string — not a paraphrase.

Steam error 1138:100134

This appears as “Failed to reset Steam account linking. Please check Steam’s status and restart the game.” It is a Steam account-link processing failure, not a damaged install.

• Fully exit Steam, then right-click its shortcut or Start search result and choose Run as administrator, sign in, and launch AION 2 again.
• If the same code returns, contact NC support with the full message and the result of that retry.
• Keep this separate from account recovery: if you changed account links and a character disappeared, use the character-missing guide — that is a different problem.

Some popups show an NP:1138:100134 prefix. NC’s FAQ documents 1138:100134 without that prefix, and we have not confirmed a separate official definition for the NP form. If the wording differs, include the full popup in your support request rather than assuming the same cause.

0xFA000103: missing runtime module

NCGUARD could not find a runtime module the game needs.

• Use the popup’s Save button, then check the bottom of the saved log for a DLL name.
• Match the named component: Windows or DirectX components mean installing applicable Windows updates; a Microsoft Visual C++ runtime means installing or repairing the matching Redistributable from Microsoft’s official guidance.
• If Steam verification completes but the popup still names a runtime DLL, keep that name and investigate the matching runtime branch. Use the official packages rather than downloading individual DLLs from unrelated sites.
• No DLL name? Send the saved log to NC support and ask which component needs repair.

NCGUARD Block Codes

A Block Code window is an anti-cheat message, not automatically a ban. A launch Block Code and an account restriction are different things.

Match the entire code, not just its first digits. Note that NC’s tables disagree on 0xE0000013, so use the full code and saved log even if the game closes before character selection.

0xE0000027: a conflict, not a broken install

This error means something running alongside AION 2 conflicts with its protected launch. Game-modification tools, memory utilities, process managers, hardware-monitoring software, RGB apps and overlays are the usual suspects — Cheat Engine has been reported by players as one possible trigger.

Work top to bottom, changing one thing at a time:

1. Restart Windows and launch AION 2 clean.
2. Check game-modification, process-management and memory-cleaning software.
3. Temporarily disable monitoring, RGB and overlay utilities (MSI Afterburner, RivaTuner, Discord, NVIDIA overlay).
4. Verify the AION 2 installation.
5. Use a Windows clean boot to isolate third-party software.
6. Save the NCGUARD log if the problem remains.

Do not disable security or anti-cheat components just to make the game launch, and avoid random registry edits or unofficial “repair” tools.

0xE0000015: leftover client processes

This is a client-count limit. Open Task Manager, force-end any leftover Aion2.exe or NCGuard.exe process, then relaunch. The official notice also pairs this with restarting the game client rather than reinstalling.

DirectX 12 and Intel 13th/14th-gen notes

• A “DirectX 12 not supported” warning usually means the GPU driver is out of date — update it from the vendor’s own site.
• On Intel 13th/14th-gen CPUs, connection instability can follow an outdated motherboard BIOS. Update the BIOS from the board maker’s site if the instability persists.

What we have not confirmed

These are official error tables and community launch reports, not a tested fix for every case, and we have not reproduced them in a running client. The same code can have different causes on different PCs, so make one change, relaunch, and record whether the error returns before trying the next step. If an exact code persists, send the saved log and the full message to NC support.