Haze Setup & Support

The request could not be confirmed. Check your account before retrying.

The request outcome is uncertain. Check your account before retrying; for key redemption, contact support before redeeming another key.

Sign in again.

There is no usable authenticated session. Sign in again.

session check failed.

The authentication session check failed. Sign in again; repeated failures need support review.

Enter your username and password.

Both sign-in fields are required.

No active products. Buy or redeem a key to add access.

No configured, unexpired product subscription was returned for this account. Check the dashboard and redemption result.

Select a product first.

Choose the product row before pressing Launch.

Enter a valid license key.

The supplied key is missing, outside the allowed length, or contains disallowed whitespace. Copy it from your order.

Invalid activation request.

The activation request failed format validation. Use the current loader and re-enter your sign-in details.

Invalid sign-in details.

The server rejected the format of the sign-in request.

Account verification failed.

The service could not confirm the requested account identity. Sign in again.

Sign-in verification failed.

The product-build service could not verify the account. Sign in again; persistent rejection needs support.

No active subscription.

The driver service found no qualifying, unexpired subscription. Check the account dashboard.

This customer account is not active.

The local customer account is not active. Contact support or your issuing reseller.

That key is invalid or already used.

The key could not be accepted as an unused active key. Check your order and previous redemptions.

This key has a pending redemption. Contact support before trying again.

A previous redemption has an unresolved outcome. Stop retrying and have support reconcile it.

Local key record changed.

The key changed while the redemption transaction was running. Ask support to check the result.

Redemption could not be confirmed. Contact support; do not buy or redeem a replacement key yet.

The system cannot safely confirm whether redemption completed. Support must resolve the existing attempt first.

Activation is busy. Try again.

Another activation for this account holds the activation lock. Wait briefly and retry once.

A pending license has an unsupported duration.

The pending subscription is not mapped to a supported duration. Support must correct its configuration.

The product is updating. Your pending key time has not started; try again when it is available.

The service paused first-launch activation because the product is not available. Check the status page before trying again.

Unable to authorize this product build. Check your access and product status or contact support.

The server rejected the build request. Account status, entitlement, product availability or release configuration needs checking.

Other sign-in, HWID, token or subscription message

Some messages are returned directly by the authentication provider and can change without a loader update. Invalid credentials, device-binding, bans, expiry and account restrictions require different actions.

Re-enter your details or request the legitimate reset/review through your account or support. An expired session can require a new sign-in; only timestamp-specific failures justify treating the clock as the cause.

Unable to connect to the account service.

The account-service connection could not be initialized.

Unable to read the response.

The service response could not be fully read.

Response is too large.

The response exceeded the loader's allowed size.

The account service returned an invalid response.

The account service did not return the expected response format.

Unable to start activation connection.

The activation connection could not be initialized.

Unable to connect to haze.ac.

The loader could not establish a connection to haze.ac.

Unable to create activation request.

The activation request could not be created.

First-launch activation service is unavailable.

The activation request or response failed. This alone does not show whether pending time was activated.

Unable to read activation response.

The activation response could not be fully read.

Activation response exceeds the size limit.

The activation response was larger than allowed.

Activation service returned an invalid response.

Activation returned data in an unexpected format.

Unable to start the driver download.

The driver-download connection could not be initialized.

Unable to create the driver request.

The driver-download request could not be created.

The driver service is unavailable.

The driver service could not complete the network exchange.

Unable to read the driver response.

The driver response could not be fully read.

The driver service returned an invalid response.

The driver service returned an unexpected response format.

CURL Initialization Failed!

The networking library could not initialize.

Redemption is unavailable.

The server could not complete redemption. Check account state before retrying.

POST required.

A service endpoint was opened with the wrong request method. Use the normal website/loader flow; browsing an API URL directly does not test a licence.

CURL Error: <network error text>

The authentication networking library supplied the text after the prefix. DNS lookup, connection, timeout and TLS errors have different causes; keep the entire line.

Check service availability and local connectivity. Use the libcurl reference below for the exact suffix; there is no fixed country or VPN requirement.

Cannot resolve temp directory.

Windows did not return a usable temporary directory.

Cannot create temp file for product.

The temporary product file could not be created.

Cannot write product to temp file.

Writing the temporary product file failed.

Unable to find your Downloads folder.

Windows could not locate your Downloads folder.

Unable to create the update download folder.

A new folder for the loader update could not be created.

Unable to save the loader update.

The loader update file could not be opened for writing.

Loader update could not be saved. Your original loader is unchanged.

Writing the update failed; the original loader was kept.

Unable to save your cloud account connection. Please sign in again.

The authenticated cloud connection could not be saved locally. Sign in again; report repeated failures.

Unable to refresh your cloud account connection.

The previous local cloud connection could not be cleared or refreshed.

Saved sign-in could not be restored. Please enter your details again.

Windows could not restore the saved credentials. Enter your details manually.

Windows could not remove your saved sign-in. Please try again.

The local saved-credential record could not be removed.

You are signed in, but Windows could not save these details. You will need to enter them again next time.

Sign-in succeeded; only Remember me failed.

File not found. Please make sure the file exists.

An authentication initialization file was not found. Get the current official loader and report repeats.

Unable to verify the current loader.

The loader could not inspect its own executable for the update check.

Invalid loader update package.

Update metadata or package size did not pass validation.

Loader update integrity check failed. No files were replaced.

The downloaded loader did not pass its content or integrity checks; the original file was kept.

Loader release fingerprint mismatch.

The update's executable fingerprint does not match the advertised release.

Saved loader update failed verification.

The update saved on disk differs from its expected checksum.

The driver response is malformed.

Required fields in the driver package are missing or invalid.

Driver decryption is unavailable.

The loader's cryptography library could not initialize driver verification.

Driver integrity verification failed.

The driver package failed authenticated integrity verification.

The driver download is not a valid Windows driver.

The verified download does not have the expected Windows-driver format.

Invalid product build selection.

The server selected an unknown product-build channel.

The product SHA-256 variable is not configured correctly in KeyAuth.

The release checksum is missing or malformed in the service configuration. Support must fix the release metadata.

Invalid debug package size.

A support-enabled debug package has an invalid size.

Invalid debug package encoding.

A support-enabled debug package cannot be decoded as advertised.

Product integrity verification failed.

The product checksum does not match the value supplied by the authenticated service.

The downloaded product is not a Windows executable.

The download does not have a Windows executable header.

download returned empty contents.

The download service returned no file contents.

invalid JSON response from download endpoint

The authenticated download did not return the expected structured response.

Invalid build request.

The product-build request contains missing or invalid fields. Use the current loader.

Invalid driver request.

The driver-service request contains missing or invalid fields. Use the current loader.

Driver is not available on the server.

The required server-side driver file is unavailable. Support must restore the release.

Server crypto is unavailable.

The hosting environment cannot initialize the package encryption. Support must repair the service.

Driver read failed.

The server could not read its driver file. This is a service-side failure.

Cannot prepare product branding.

The product branding data could not be prepared.

Cannot pass product branding.

The loader could not hand the selected appearance to the product.

Cannot start product process.

Windows could not start the product process. This does not identify a particular driver or antivirus as the cause.

The application stopped because of an unhandled error.

An unhandled application exception occurred. Include the full hexadecimal exception code and stage.

The application stopped because of an unexpected internal error.

An unexpected internal exception stopped the application.

The existing startup safety checks did not pass. The application has stopped.

BattlEye or Riot Vanguard is running. Disable it and restart your PC before launching Haze again.

Windows could not create the application's single-instance lock.

Windows could not create the lock used to prevent duplicate instances; the code gives the system reason.

Another copy is already running. Close that copy before trying again.

The product detected another running copy. Close that copy normally before starting another.

This build requires 64-bit Windows 10 or Windows 11.

The operating-system check did not identify Windows 10/11 on native x64. Windows on ARM and 32-bit Windows do not pass this check.

Game initialization failed because the required game component was not available. Startup has stopped.

A required game component was unavailable during initialization. Confirm the normal game reaches its menu and check product status.

The game window was not found before menu initialization timed out.

The expected game window was not found in time. Open the normal game and leave its window visible.

Startup has not completed this stage after 45 seconds. The application is still waiting; this does not necessarily mean it crashed.

This is a warning, not a fatal timeout. The application keeps waiting. Check the displayed stage before launching another copy.

The menu could not continue because its target window or display bounds are no longer available.

The application lost the target window or usable display bounds. Restore the game window; report repeats after a normal restart.

The menu window has invalid display dimensions.

The menu received an invalid window or zero/negative display size.

Windows could not initialize the graphics adapter service.

Windows could not initialize the graphics-adapter service.

Direct3D could not create the menu's graphics device or swap chain.

Graphics-device and swap-chain creation failed, including the fallback attempt.

Direct3D initialization returned incomplete graphics resources.

Graphics initialization returned incomplete resources.

Direct3D could not obtain the menu's back buffer.

The renderable back buffer could not be obtained.

Direct3D could not create the menu's render target.

The menu render target could not be created.

The menu window could not be created or located before startup timed out.

The menu window could not be created or located before the startup deadline.

The menu could not be initialized.

The menu did not initialize; use any accompanying stage and code to narrow the cause.

public key mismatch detected.

The authentication verification key failed its consistency check.

local auth gate failed.

The local authentication guard rejected the request.

API URL must use HTTPS.

The configured authentication address is not HTTPS; this requires a corrected official build.

Hosts file override detected for API host.

A hosts-file override was detected for the authentication service. Have support or your administrator inspect the network configuration.

API host is not in allowed host list.

The configured authentication host is not permitted by this build.

loopback or local host detected for API URL.

The authentication URL points to a local host instead of the expected service.

API host must not be an IP literal.

The authentication URL uses an IP address where a hostname is required.

API host resolves to private or loopback.

Authentication DNS resolved to a local or private address, which the guard rejects.

Multiple pinned public keys not supported.

This build does not support the configured public-key pin format.

Pinned public key not supported by this libcurl build.

The linked networking library does not support the configured public-key verification.

SSL verify result failed.

The TLS certificate verification did not pass. Check Windows time and legitimate network certificate settings; retain verification.

missing signature headers.

The response did not include the required signature headers.

invalid signature header format.

The response signature header has an invalid format.

invalid signature timestamp header format.

The signed response timestamp has an invalid format.

payload verification marker mismatch.

The response marker does not match the expected signed payload.

libsodium init failed in request guard.

The cryptography library could not initialize the response verifier.

signature decode failed in request guard.

The response signature could not be decoded.

public key decode failed in request guard.

The response verification key could not be decoded.

signature verify failed in request guard.

The response failed its cryptographic signature check.

effective url not https.

The final authentication connection did not use HTTPS.

effective url host mismatch.

The final authentication host differs from the expected host.

api port mismatch.

The authentication connection used an unexpected port.

api host resolved to private or loopback ip.

The connected authentication address is local or private.

api host ip mismatch vs fresh dns.

The connected address differs from a fresh DNS result. This may need network or service investigation.

You need to run the KeyAuthApp.init(); function before any other KeyAuth functions

The authentication library was used before initialization. This needs a software fix.

module path check failed, possible side-load detected.

A loaded module came from a path the application does not accept.

timing anomaly detected, possible time tamper.

The application detected an unexpected timing change. Check Windows time, then report repeated failures.

.text rolling crc mismatch.

An application code-integrity check failed. Get a fresh official download; repeated failures need investigation.

critical module path violation.

A required module was loaded from a disallowed path.

libcurl checksum mismatch.

The networking-library integrity check failed.

libsodium checksum mismatch.

The cryptography-library integrity check failed.

check_section_integrity() failed, don't tamper with the program.

An application-section integrity check failed. This message alone does not establish why the check failed.

LockMemAccess() failed, don't tamper with the program.

A process-memory protection step failed. Send the exact message to support.

Pattern checksum failed, don't tamper with the program.

An application integrity pattern check failed.

Missing signature headers in response

The authentication response is missing required verification metadata.

Application Not Setup Correctly. Please Watch Video Linked in main.cpp

The application credentials/configuration in this loader are invalid. Support must provide a corrected build.

Application not found. Please copy strings directly from dashboard.

The authentication service did not recognize the configured application. This requires a release-configuration fix.

You forgot to remove "secret" from main.cpp. Copy details from

The authentication library received a URL where it expected a local initialization-file path. This is a build configuration problem; support must provide a corrected loader.

invalidver / Version in the loader does match the one on the dashboard, and the download link on dashboard is blank.

The authentication provider rejected the loader version. The longer popup also means no update link was configured; its wording is misleading. Get the current official download and report the exact message if it persists.

Signature verification failed (timestamp length)

The response timestamp has an invalid length.

Signature verification failed (timestamp format)

The response timestamp has an invalid format.

Signature verification failed (invalid timestamp)

The response timestamp could not be parsed.

Signature verification failed (timestamp skew)

The signed response time differs from the local clock by more than two minutes. Sync Windows date/time, sign in again, and report repeats.

Signature verification failed (libsodium init)

The signature-verification library could not initialize.

Signature verification failed (sig length)

The response signature has an invalid length.

Signature verification failed (invalid signature format)

The response signature could not be decoded.

Signature verification failed (invalid public key)

The configured verification key could not be decoded.

Signature verification failed (invalid signature)

The signed response failed verification.

HAZE_LOCAL_PAYLOAD file not found.

A developer-only local-file override names a missing file. Ask support to restore the normal release setup; this is not a missing licence key.

Diskless support is unavailable.

This alternate launcher cannot initialize its required Windows process APIs.

The product download is not a valid executable.

The alternate launcher rejected the executable format.

Unable to allocate the driver handoff.

Memory for the driver handoff could not be allocated.

Unable to map the driver handoff.

The allocated driver handoff could not be mapped.

The product host could not be started.

The alternate product host process could not be started.

The host thread context could not be read.

The alternate launcher could not read the host thread state.

The host image base could not be resolved.

The alternate launcher could not locate the host image.

The product image could not be mapped.

The alternate launcher could not allocate or map the product image.

The product headers could not be written.

Writing the product header failed.

The product sections could not be written.

Writing one or more product sections failed.

A product dependency could not be loaded.

A module required by the product could not be loaded. Support needs the build and any accompanying module name.

A product import could not be resolved.

A required function could not be found in a dependency. Do not download replacement DLLs from third-party sites.

The product bootstrap could not be allocated.

Memory for the alternate startup routine could not be allocated.

The product bootstrap could not be written.

The alternate startup routine could not be written.

The host image could not be read.

The alternate launcher could not read the host image.

The host image is invalid.

The host executable format was rejected.

The host entry could not be prepared.

The alternate host entry could not be prepared.

The host entry could not be patched.

The alternate host entry could not be updated.

The product headers could not be wiped.

The alternate launcher could not complete its final image-preparation step.

popen() failed!

An authentication-library helper could not start a subprocess.

Failed to find WdFilter RuntimeDriversList / Failed to acquire PiDDB lock

Older or alternate driver-initialization diagnostics. They do not establish a universal antivirus or Windows configuration fix.

Stop repeated launch attempts and send the exact message, Windows build and product version to support for compatibility review. Do not apply registry-disabling commands from older guides.

0x000000B7 / 183 — ERROR_ALREADY_EXISTS

For the duplicate-instance popup, the named application lock already exists. Close the existing copy normally.

Official code reference

0x0000047E / 1150 — ERROR_OLD_WIN_VERSION

The product uses this code when its Windows 10/11 x64 compatibility check fails. Record your Windows build and System type.

Official code reference

0x00000005 / 5 — ERROR_ACCESS_DENIED

Windows denied an operation. The accompanying message identifies what was denied; this is not proof of an antivirus conflict.

Official code reference

0x00000002 / 2 and 0x00000003 / 3

A file or path was not found. Use the accompanying message to identify which location is missing.

Official code reference

0x80070057 — E_INVALIDARG

An argument was invalid. The menu explicitly uses this for invalid window/display dimensions. Restore a visible game window and report repeats.

0x80004005 — E_FAIL

A generic operation failure. It does not identify the root cause; include the full message and stage.

0x887A0004 — DXGI_ERROR_UNSUPPORTED

The requested graphics operation is unsupported. Check the GPU/driver and ask support to review compatibility.

Official code reference

0x887A0005 — DXGI_ERROR_DEVICE_REMOVED

The graphics device became unavailable, for example during a driver change. Restart the application and report repeated device loss.

Official code reference

0x887A0006 — DXGI_ERROR_DEVICE_HUNG

The graphics device rejected application commands. This can require an application fix; send the complete error to support.

Official code reference

0x887A0007 — DXGI_ERROR_DEVICE_RESET

The graphics device needs to be recreated after a command failure. Restart the application; report repeats.

Official code reference

CURL 6 / 7 / 28 / 35 / 60

Respectively: hostname lookup failed; connection failed; request timed out; TLS connection failed; peer certificate verification failed. Use the full error text and retain TLS checks.

Official code reference

HTTP 400 / 401 / 403 / 405 / 503

For the reviewed Haze endpoints: invalid request; sign-in/identity rejection; access or build authorization rejection; wrong method; service unavailable. The returned message narrows the reason. These are HTTP statuses, not Windows error codes.