Error Codes

Every launcher error dialog shows three lines:

• Error name - short human-readable label
• Code - a Windows-style HRESULT (e.g. 0x80091007)
• Diagnostic ID - a short per-build token (e.g. e1ZT, A7X2)

If you contact support, include all three. The Diagnostic ID is the most important: it tells us exactly which internal check fired in your specific build, even when multiple checks share the same Code and Name. Runtime errors (login failures, network trouble, download problems) surface inline with the same three-part prefix format:

[0x80070057 / A7X2] Login failed: invalid credentials

What happens when an error fires

Some errors close the window and then remove the launcher from disk. That is intentional: a leaked, tampered, expired, revoked, or environment-invalid build should not stay on the machine. Two different mechanisms cover this:

• Delete-on-reboot (MoveFileEx): the file survives the current session but is gone after the next reboot.
• Immediate NTFS self-delete: the file is gone right away, after a 30-second confirmation dialog.

Both mechanisms end at the same place. To use the launcher again after a self-removing error, redownload from your dashboard and every download is freshly built for your account.

Self-removes?	Categories
Yes	Integrity / bake tamper, Hardware mismatch, Build expired / revoked, Unsupported environment, Response signature mismatch, Downloaded-file verify or decrypt failure, No active subscription, Launcher out of date
No	Everything else (recoverable startup, auth, HWID pairing, network transport, download in transit, product-launch)

A recoverable error keeps the file on disk so you can fix the underlying cause (close the other instance, accept the UAC prompt, sign in again, etc.) and try again. Self-removing errors require a fresh download from your dashboard.

“No active subscription” is a special case: it also clears your locally-cached products directory and your DPAPI-protected sign-in credentials, so the next launch starts from a completely clean slate.

Startup errors (self-remove)

These fire during the launcher’s boot sequence, before the main window appears. Each shows in the styled launcher dialog (with a Win32 MessageBox fallback if the dialog subsystem itself fails).

0x80091007 - Integrity check failed (bake missing)

This copy of the Mudcrab Launcher is not bound to any account. Please sign in to your dashboard and download a fresh copy.

Cause. The launcher’s per-customer bake region cannot be found. This happens when the exe is an untouched template that never went through the per-customer mint step, or the file was truncated in transit.

Fix. Redownload from your dashboard. Do not share a downloaded launcher with anyone else - each copy is bound to the account it was minted for.

0x80091007 - Integrity check failed (bake corrupt)

The Mudcrab Launcher’s bake region was modified after download. Please sign in to your dashboard and download a fresh copy.

Cause. The bake region was found but its signature or checksum did not verify. Usually antivirus quietly modified the file after download, or the file was tampered with.

Fix. Redownload from your dashboard. Add the file to your antivirus exceptions before running it if the problem repeats.

0x8007000B - Integrity check failed (bake wrong version)

This launcher’s bake region uses a wire format that does not match this build. Please redownload from your dashboard.

Cause. You are running a launcher build whose bake region was minted for a different, incompatible build version.

Fix. Redownload the latest launcher from your dashboard so the build and the bake match.

0x80070005 - Hardware mismatch

This machine is not the one your account is locked to. Contact support to move your license to a new PC.

Cause. Every account locks to one PC on its first successful launcher sign-in and stays there. This error fires when the launcher runs on any other PC. Legitimate reasons: a new PC, dead motherboard, OS reinstall to a different disk. A less legitimate reason is that somebody else is running your launcher on their PC.

Fix. If you have not changed hardware, close the launcher and change your password immediately so any other session is logged out. If you legitimately need to move (dead hardware, new PC), contact support with the Diagnostic ID and we will unlock your account; the next sign-in on the new PC will lock to it.

0x800B0101 - Build expired

This build is no longer valid. Please download the latest version from the official source.

Cause. The build was minted with an expiry date and that date has passed. Every customer-facing build has an expiry baked in at mint time.

Fix. Redownload the latest build from your dashboard.

0x800B0101 - Build revoked

This build was recalled and is no longer permitted to run. Please download the latest version from your dashboard.

Cause. The build was recalled by us (usually a security fix in a newer version supersedes it). Old builds are marked revoked and refuse to run once the server sees them.

Fix. Redownload the latest build from your dashboard.

0x80004005 - Unsupported environment

The application cannot run in the current environment. Close other windows and try again.

Cause. One of the launcher’s environment checks tripped. This is a deliberately generic message that covers several distinct internal checks (they all share the same Code and Name on purpose). The Diagnostic ID is what tells support which specific check fired. Possible internal causes:

• Debugger - x64dbg, IDA, ProcessHacker, Wireshark, or a debug loop attached
• Hypervisor / VM - VMware, VirtualBox, Hyper-V, KVM guest
• API hook - hook engine, anti-cheat shim, third-party detour
• Suspicious module - cheat-engine DLL, known RE tooling in-process
• Timing anomaly - startup timing pattern matches sandbox / emulator
• Sandbox - Windows Sandbox or Sandboxie container
• Screen capture - screen recording / capture software the anti-capture layer could not neutralise

Fix. Close any debugging, monitoring, capture, or RE tooling. Exit any VM and run on bare metal. Disable third-party tools that hook into running processes (overlay software, capture utilities, etc.) and try again. If the error persists on what looks like a clean machine, send the Diagnostic ID to support: that is how we identify which specific check is being tripped.

Startup errors (recoverable, file stays on disk)

0x80070057 - Unexpected error (UI init failed)

Failed to initialize the launcher UI. Please try again.

Cause. DirectX 11, DirectComposition, or the ImGui subsystem refused to initialise. Usually a missing / broken graphics driver or a graphics driver that is being updated in the background.

Fix. Update your graphics driver and try again. If the driver is fine, reboot: driver state can get wedged between updates.

0x80070057 - Startup timed out

The application did not finish starting. Please try again.

Cause. The launcher’s startup watchdog fired before initialization completed. This usually means a long-running antivirus scan stalled one of the helper-init steps past the budget.

Fix. Temporarily disable real-time scanning, run the launcher, then re-enable real-time scanning. If it keeps timing out on a clean machine, send the Diagnostic ID to support.

0x80070057 - Unexpected error (init threw)

Something went wrong while starting. Please send the codes above to support so we can help you.

Cause. An exception escaped the launcher’s main init handler. This is the catch-all path for “we do not know what happened, but it should not have.”

Fix. Try once more. If it fires twice in a row, send the Diagnostic ID to support: every fresh occurrence of this error is something we want to investigate.

0x80070020 - File in use

Another instance of the application is already running.

Cause. The launcher uses a Windows named mutex to enforce single-instance behavior. This error means another copy is already running, or crashed in a way that left the mutex held.

Fix. Close the existing window. If you cannot see one, open Task Manager and end any launcher process (its filename is a random 8-character .exe you downloaded from your dashboard). Then try again. A reboot also works if Task Manager is unhelpful.

0x800701E7 - Insufficient privileges

Administrator access was not granted. Please try again.

Cause. You declined the UAC prompt, the UAC prompt was dismissed by group policy, or your account does not have administrator rights.

Fix. Run the file again and accept the UAC prompt. If you are on a managed machine where UAC is locked down by your IT department, you will need their help.

0x8007000B - Unsupported Windows version

This build requires a newer version of Windows. Update Windows and try again.

Cause. Your Windows version is older than the minimum this build supports. Recent builds require modern DirectComposition + DXGI features present in Windows 10 1809 and later.

Fix. Install pending Windows updates. If you are on Windows 7 / 8 / 8.1, upgrade to Windows 10 or 11.

0x8007000B - Unsupported architecture

This build cannot run on your processor architecture. Please download the correct build for your system.

Cause. You are running an x64 build on a 32-bit or ARM CPU, or vice-versa.

Fix. Download the correct architecture from your dashboard.

0x80092013 - System clock error

Your system clock is set too far in the past or the future. Correct the date and time and try again.

Cause. The launcher validates TLS certificates and signed responses against the system time. A clock more than a few days off makes every certificate look expired (or not yet valid).

Fix. Open Windows Settings > Time & language > Date & time, enable “Set time automatically”, and click Sync now.

0x80070005 - Cannot write launcher data

The launcher could not write to your AppData folder. Check that your account has write access to LocalAppData.

Cause. The launcher stores credentials, license sidecar files, and staged product binaries under %LOCALAPPDATA%\Mudcrab. Something is denying write access there: usually an antivirus in aggressive mode, a corporate group-policy lockdown, or a filesystem attribute set to read-only.

Fix. Add %LOCALAPPDATA%\Mudcrab to your antivirus exceptions. On a managed machine, ask IT to allow writes to the LocalAppData subtree.

0x80070070 - Not enough disk space

There is not enough free disk space to continue. Free up some space and try again.

Cause. The launcher needs a few hundred megabytes free on the drive that holds %LOCALAPPDATA% to stage product binaries and write configuration data.

Fix. Free up space on your system drive and try again.

0x80090005 - Cannot protect stored data

Windows Data Protection API refused to secure the launcher’s stored data. Sign out of Windows and back in, then try again.

Cause. DPAPI (which the launcher uses to encrypt stored credentials) is refusing the wrap or unwrap call. Usually caused by a corrupted user profile, or a recent password reset that invalidated the DPAPI master key.

Fix. Sign out of Windows and back in. If the problem persists, delete %LOCALAPPDATA%\Mudcrab\creds.dat and sign in again in the launcher.

0x8007007E - Missing system component

A required Windows system library is missing. Install any pending Windows updates and try again.

Cause. A Windows system DLL the launcher depends on cannot be resolved. This usually means an incomplete Windows install or a system-file corruption.

Fix. Install pending Windows updates. If that does not help, run sfc /scannow from an elevated Command Prompt.

0x8007007E - Cannot read machine identity

The launcher could not read this machine’s identity. This usually clears after a reboot.

Cause. The subsystem the launcher uses to identify the PC refused to answer. WMI service can be temporarily unavailable, or a required registry key is locked.

Fix. Reboot and try again. If the error persists, send the Diagnostic ID to support.

Auth / session (runtime, inline in the launcher)

0x80070057 - Login failed

Your email or password was rejected.

Cause. The server did not accept the credentials you entered.

Fix. Check for typos. If you forgot your password, reset it at your dashboard.

0x80070005 - Account disabled

Your account is currently disabled. Contact support to appeal.

Cause. An administrator disabled your account.

Fix. Contact support if you believe this is a mistake.

0x800705B4 - Account temporarily locked

Your account is temporarily locked after too many attempts. Wait a few minutes and try again.

Cause. Rate-limiting kicked in after repeated failed login attempts.

Fix. Wait a few minutes and try again. If you cannot remember your password, reset it at your dashboard.

0x80070005 - Email not verified

Please verify your email address before signing in. Check your inbox for a verification link.

Cause. Your account exists but the email verification step is pending.

Fix. Check your inbox (and spam folder) for the verification link. You can request a resend from your dashboard.

0x80090330 - Password refresh required

For security, please re-enter your password to continue.

Cause. The launcher signs you out roughly monthly and asks you to re-enter your password. This is the monthly freshness rule.

Fix. Type your password again in the sign-in form.

0x800704C7 - Session expired

Your session has expired. Sign in again to continue.

Cause. Your session token timed out while the launcher was running.

Fix. Sign in again.

0x80070005 - Session ended elsewhere

This session was ended from another device or by an administrator. Sign in again to continue.

Cause. Someone signed out of this session from another device, or an administrator revoked it.

Fix. Sign in again. If you did not initiate the sign-out, change your password immediately.

0x80070005 - Session required

This action needs a signed-in session. Please authenticate and try again.

Cause. You hit a session-only endpoint without a valid session. This usually means the launcher’s stored credentials were stale and the auto-retry has not yet fired.

Fix. Sign in on the login form and try again.

Hardware pairing (runtime, inline)

The launcher pairs your account to the PC on first sign-in. These errors fire at activation / preflight time when the server thinks the current PC is not the one it should be.

0x80070005 - This device is not paired

This device is not paired to your account.

Cause. The server has no HWID pairing for the fingerprint your launcher just presented. Usually a fresh install after a hardware reset, or the pairing on file was cleared by an admin.

Fix. Sign out and sign back in on the launcher; the fresh sign-in will re-pair automatically if your account is still eligible for this machine. If the launcher keeps refusing, contact support with the Diagnostic ID.

0x80070008 - Too many devices paired

Your account already has the maximum number of devices paired.

Cause. Your account is at its per-account device cap. This is usually one device; some accounts have been granted a higher cap.

Fix. Contact support with the Diagnostic ID and the PC you want to keep using. Support can unpair an old device so the new one can pair.

0x80070005 - This device was revoked

This device was revoked. Contact support if you did not expect this.

Cause. The pairing for this machine was explicitly revoked, either by you asking us to move it or by an admin action.

Fix. If you did not initiate the revoke, change your password immediately, then contact support with the Diagnostic ID.

Subscription

0x80070005 - No active subscription

You do not have an active subscription for this product.

Cause. You do not currently have an active subscription that covers this product.

Fix. Subscribe or renew from your dashboard.

0x800B0101 - Subscription lapsed

Your subscription has expired. Renew it from your dashboard.

Cause. Your subscription expired and was not renewed.

Fix. Renew from your dashboard.

0x8007041D - Subscription paused

Your subscription is paused. Resume it from your dashboard.

Cause. Your subscription is in a paused state (e.g. billing hold, manual pause).

Fix. Resume from your dashboard.

0x80070005 - Subscription refunded

Access to this product was removed after a refund.

Cause. Access to this product was removed after a refund on the subscription that granted it.

Fix. Subscribe again from your dashboard if you would like access back.

Network / server (runtime)

0x80070057 - Network error

The launcher could not reach the server.

Cause. Generic transport failure that does not fit one of the more specific network buckets below.

Fix. Check your internet connection and try again. Send the Diagnostic ID to support if it keeps failing.

0x800705B4 - Network timeout

The server took too long to respond. Check your connection and try again.

Cause. The HTTP request took longer than the launcher’s budget to complete.

Fix. Check your internet connection. Try a different network if possible (mobile hotspot is a good diagnostic).

0x80072EE7 - DNS resolution failed

The launcher could not resolve the server address. Check your DNS settings and try again.

Cause. Your system could not resolve the launcher’s server hostname to an IP address.

Fix. Try switching your DNS server (Cloudflare 1.1.1.1, Google 8.8.8.8). If you are on a corporate network, contact IT.

0x80072F8F - Secure connection failed

The launcher could not establish a secure connection. This is usually a system clock, DNS-hijack, or corporate-proxy issue.

Cause. TLS handshake failed. Common causes: system clock wildly off, DNS returning a wrong IP, a corporate MITM proxy replacing the certificate, or a compromised network.

Fix. Fix your system clock first. If that does not help, try a different network. If you are on a corporate network with SSL inspection, that inspector must not intercept our domain.

0x80072EFD - You appear to be offline

The launcher could not detect an internet connection.

Cause. Windows reports the system as offline.

Fix. Connect to the internet and try again.

0x80070422 - Server maintenance

The server is temporarily offline for maintenance. Please try again shortly.

Cause. Our server is in a maintenance window.

Fix. Wait a few minutes and try again. Follow our status page for outage announcements.

0x80072EE5 - Too many requests

The launcher is making too many requests. Wait a moment before trying again.

Cause. You (or the launcher) hit our rate limit.

Fix. Wait a minute and try again.

0x80070005 - Access refused

The server refused this request. Please contact support with the diagnostic ID above.

Cause. The server refused the request outside of the usual auth flow (usually a defensive block).

Fix. Contact support with the Diagnostic ID.

0x80131533 - Bad server response

The server returned an unexpected response. Try again shortly.

Cause. The server returned a response the launcher could not parse.

Fix. Wait a moment and try again. If it repeats, send the Diagnostic ID to support.

0x80091007 - Signature verification failed

A response from the server did not verify against the expected key. This is usually a stale or tampered proxy on your network.

Cause. The launcher signs every meaningful server response and refuses to trust one that does not verify. Usually a corporate MITM proxy is re-signing our responses with its own certificate.

Fix. If you are on a corporate network with an SSL inspector, that inspector must not intercept our domain. On a home network, this is a serious warning: someone is tampering with your traffic.

This error self-removes the launcher immediately (not on reboot). A signature mismatch is treated as a live tamper attempt: the file is deleted and the process terminates as soon as you close the confirmation dialog. Redownload from your dashboard after fixing the root cause. The same behavior applies when a completed download fails its post-transfer hash check.

0x800B0004 - Client update required

This launcher is talking to a newer server than it expects. Please download the latest launcher from your dashboard.

Cause. Our server API moved ahead of what this launcher understands.

Fix. Redownload the latest launcher from your dashboard.

0x800B0004 - Launcher out of date

The current version of the Mudcrab Launcher is out of date. Download the new launcher from https://store.mudcrab.co/dashboard.

Cause. This launcher was built from an older template than the one that is currently live. The launcher checks its version when you sign in and retires itself when it has fallen behind.

Fix. Download the new launcher from your dashboard. The old copy self-deletes immediately when you close the dialog. Your saved sign-in credentials are preserved on purpose, so the fresh launcher signs you straight back in.

0x80040154 - Activation refused

The server refused to activate this license on this machine.

Cause. The server rejected the launcher’s activation request.

Fix. Contact support with the Diagnostic ID for the specific reason.

0x80040154 - Preflight refused

The server refused this preflight request.

Cause. The server rejected the preflight-checks call the launcher makes before every product download / launch.

Fix. Sign out and back in to refresh your session. Contact support if the problem persists.

0x80040154 - Heartbeat rejected

The subscription heartbeat was rejected.

Cause. The periodic subscription heartbeat came back with a rejection (usually an expired subscription).

Fix. Check your subscription status on the dashboard.

0x80040154 - Catalog load failed

The product catalog could not be loaded.

Cause. The launcher could not load the product catalog (either the server refused or the response failed to parse).

Fix. Try again in a minute. If it persists, sign out and back in.

Download / decrypt

0x80070057 - Download failed

A product download could not be completed.

Cause. Generic download failure that does not fit the more specific download buckets below.

Fix. Try again. If the problem repeats, check your internet connection and antivirus.

0x80091007 - Downloaded file verification failed

A downloaded product did not match its expected checksum. The download will be retried automatically.

Cause. The download completed but the file’s checksum did not match what the server said it should be. Usually caused by antivirus modifying the file in flight.

Fix. Add the launcher’s staging folder to your antivirus exceptions. If the retry keeps failing, contact support.

0x80090005 - Decryption failed

A downloaded product could not be decrypted. Please try downloading it again.

Cause. The downloaded ciphertext failed to decrypt. Usually a byte-level corruption in transit.

Fix. Retry the download.

0x80070057 - Download interrupted

The connection dropped mid-download. Try again.

Cause. The connection to the download server dropped mid-way.

Fix. Try again. If your connection is spotty, consider a more stable network.

0x800B0100 - Download size mismatch

The downloaded file’s length did not match what the server announced. Please try again.

Cause. The number of bytes received did not match the Content-Length the server declared.

Fix. Try again.

Product launch

0x80070002 - Product unavailable

This product is no longer available in the catalog.

Cause. The product you tried to launch was removed from the catalog since you last opened the launcher.

Fix. Refresh the catalog. If the product should still be available, contact support.

0x80070005 - Product staging failed

The launcher could not stage the product for launch. Check disk space and antivirus exclusions.

Cause. The launcher could not write the decrypted product binary to its staging folder. Usually disk full or antivirus block.

Fix. Free up disk space. Add the launcher’s staging folder to your antivirus exceptions.

0x80070005 - Product launch failed

The launcher could not start the product. Check that no antivirus is blocking it.

Cause. CreateProcess failed when the launcher tried to spawn the product binary. Usually antivirus quarantined the binary between staging and launch.

Fix. Add the launcher’s staging folder to your antivirus exceptions.

0x8007000B - Product architecture mismatch

This product cannot run on your processor architecture.

Cause. The product binary is built for a different CPU architecture than yours.

Fix. Contact support with the product name so we can flag the mismatch.

0x80070005 - Injection failed

The launcher could not attach to the target process.

Cause. For products that inject into a running target, the injection step failed. Common causes: target has anti-cheat that refuses the injection, target has protections that block foreign code, or the launcher was not elevated.

Fix. Make sure the launcher is running elevated. Close any third-party overlay / capture software. If a specific anti-cheat is blocking us, contact support.

0x80070002 - Target not running

The target application is not currently running. Start it and try again.

Cause. For products that inject into an existing target, that target application is not currently running.

Fix. Start the target application and click the product’s launch button again.

0x80070422 - Product unavailable

This product is not available to launch right now.

Cause. An operator paused this specific product on our side. The launcher shows a status pill on the catalog card and disables the Load button when a product is not operational. This is the one error whose message is replaced by the server verbatim, so you may see one of these instead of the default:

• Updating: “This product is being updated and is briefly unavailable. Check back soon.”
• In development: “This product is still in development and not available yet.”
• Down: “This product is temporarily down. We are working on it.”
• Fallback: “This product is currently unavailable.”

Fix. Wait for the product to come back to operational. Watch Discord for the announcement. Your subscription is not affected: pause time does not count down during an operator pause at the product level.

Catch-all

0x80070057 - Unexpected error

Something unexpected happened. Please try again, and send the Diagnostic ID to support if it repeats.

Cause. The launcher hit a failure that did not fit any of the specific categories above. This is deliberately a catch-all so no user-facing failure ships without a code.

Fix. Try the action again. If it fires more than once, send the Diagnostic ID to support: every fresh occurrence is something we want to look at.

Sign-in form banners (no code, no dialog)

A handful of short messages surface inline on the sign-in form instead of going through the full error dialog. They have no Code and no Diagnostic ID because they are not failures per se, just status. For completeness, this is every one that can appear:

• “Signed out for security. Sign in to continue.” - Your saved sign-in credentials went stale (usually because Windows recycled DPAPI, or because you changed your password on the website). Sign in again and the launcher re-caches them.
• “Signed out.” - Shown right after you clicked Log out on the main window. Sign in again to continue.
• “Sign in timed out. Check your connection and try again.” - The sign-in request took longer than the launcher’s budget. Usually a slow connection or an antivirus stalling the request.
• “Could not refresh from the store just now. Showing what we have.” - The catalog refresh failed on a background poll while a signed-in session is up. The launcher keeps rendering the last-known catalog and retries automatically. Nothing to do; if it stays stuck for more than a few minutes, sign out and back in.

”My launcher disappeared after an error”

That is expected when the error category is integrity / tamper / expired / wrong machine / bad environment. The launcher marks itself for delete-on-reboot so a leaked or modified copy cannot be reused. To recover:

1. Go to your dashboard at store.mudcrab.co
2. Re-download the latest build from Get the launcher
3. Run the new file

If you need to grab the exact bytes of the failing build for a support ticket, you can copy it before you reboot: the launcher schedules delete-on-reboot rather than deleting immediately.

If the same self-removing error keeps firing on a fresh download, open a support ticket and include the Diagnostic ID from the most recent failure: that lets us trace it to the exact code path on our side.