Authentication
Microsoft, Xbox, XSTS, Minecraft Services, ownership and entitlement failures.
LEVIATHAN ERROR CODES
Stable codes.
Useful answers.
Leviathan error codes are designed to identify a subsystem and failure class while preserving the original exception, service error, exit code or network response that caused the problem.
Diagnostic Context
Search by subsystem.
Architecture preview
EXAMPLELVT-AUTH-1003
Auth subsystem · stable code · separate correlation ID
CODEStable
TRACEPreserved
SECRETRedacted
CODE LOOKUP
Validate the format.
The live public explanation database is not connected yet. This lookup checks the Leviathan code format without inventing an explanation.
Enter a code to check its format.Example: LVT-AUTH-1003
CODE FAMILIES
Organized by the part that failed.
Downloads
HTTP failures, mirrors, retries, timeouts, size mismatches and checksum problems.
Java & runtime
Missing runtimes, incompatible versions, native libraries and launch-process failures.
Graphics
Drivers, OpenGL, LWJGL, renderer initialization and compatibility problems.
Mods & loaders
Loader conflicts, incompatible mods, configuration failures and version mismatches.
Network & services
Backend outages, API failures, server connections, DNS and timeout conditions.
DIAGNOSTIC RECORD
The stable code is only one layer.
Support needs enough context to understand a failure without putting secrets into a public error string.
1Error codeStable and searchable across launcher, web, Discord and documentation.
2Correlation IDUnique incident reference for logs and support records.
3Original errorPreserve HTTP status, Java exit code, stack trace or service response when safe.
Failure recordPrivacy safe
#
LVT-DL-2004Stable error code
SearchableID
Correlation IDPer occurrence
Unique403
Original statusPreserved when relevant
Context••
SecretsTokens and credentials
RedactedNeed help with a real failure?
Use the Support Center and include the Leviathan error code when one is available.