Client · Error Codes
Self-service troubleshooting for the HOOZi client. Find the section matching your symptom and follow the steps. First time using it? Start with Getting Started.
If the problem persists, quote the section name and the full error text you saw (especially the code in parentheses, e.g. code 16 or license/expired) when contacting support — it saves a lot of back-and-forth.
Error code reference
Every error from the client and the child apps has the same shape: one plain sentence plus a code in parentheses.
Your subscription has expired (license/expired)·Authorization data failed verification (code 16)
Copy whatever is inside the parentheses and search for it below (Ctrl+F). You do not need to work out which category you are in first. The two spellings only reflect where the code came from — numbers from the child app itself, slashed ones from the server — you look them up the same way.
| code | Meaning | What to do |
|---|---|---|
| 10 | Not launched through the client | Launch from the HOOZi client; do not double-click the child app exe |
| 12 | Your system clock really is too far off | See System clock is wrong |
| 13 | Communication between client and child app failed | Close both, then launch again from the client |
| 14 / 15 | Malformed authorization data, or the build is too old to recognize the new server key | Update both the client and the child app |
| 16 | Authorization data failed verification | The file is corrupted or modified — download and reinstall |
| 17 | Received authorization for a different product | Relaunch from the client; contact support if it persists |
| 18 | This device does not match the one bound to your account | See Switched to a new computer — read that section before unbinding, two cases cannot be fixed by unbinding |
| 19 | Authorization data has expired | Usually still a clock problem — see System clock is wrong |
| 20 | This authorization was already used once | Close all child app windows and relaunch from the client |
| 21 | Debugger detected | Close any debugging / packet-capture / reverse-engineering tools and retry |
| 30 | Browser sign-in not completed within 5 minutes | Relaunch and complete the authorization promptly |
| 31 | Authorization cancelled, or the page was closed early | Retry, and leave the browser tab open until it finishes |
| 32 | Cannot reach the server | Check your network and retry; trying another network (a phone hotspot) narrows it down |
| 33 | Account is bound to another device | Read this note first, then consider unbinding |
| 34 | This account has no active subscription for this product | Check your subscriptions, then renew or redeem a code and retry |
| 50 | Network unreachable (DNS / connection / timeout) | Check your network and retry; try another network |
| 51 | Request rejected by the server, usually still a clock offset | See System clock is wrong |
| 40–44 / 52 | Encrypted channel problem, or the server returned an error | Update to the latest version first; contact support with the full error if it persists |
| 1 / 2 / 99 / 100 | Internal program error | See Internal errors that need support |
launch/blocked_by_dialog | Sub-app blocked by a dialog (usually your swapped leechcore.dll doing an online licence check) | The window is already in front - complete it there; see Swapping leechcore.dll |
launch/child_exited | Sub-app exited before connecting to the client | Open the runtime log for the exit code and module list; same section as above |
launch/dll_not_found | A dependency is missing; Windows failed it before startup | The runtime log names it; if you swapped a DLL yourself, add its companion files |
launch/dll_init_failed | A dependency failed to initialise | Usually a swapped leechcore.dll that does not match your firmware / driver - put back a matching build |
launch/dll_arch_mismatch | Dependency has the wrong bitness (32 vs 64-bit) | Put back the build matching the sub-app |
launch/child_crashed | Sub-app crashed right after starting | The runtime log has the exit code; if reinstalling does not help, contact support |
launch/child_no_pipe | Sub-app started but never connected to the client | Check for a browser tab waiting for authorisation; see Swapping leechcore.dll |
launch/sdk_rejected | The sub-app itself rejected the launch | The exit code in the runtime log is one of the numeric codes above - follow that row |
launch/handshake_failed | Secure handshake between client and sub-app did not complete | Retry; if it persists, send support the runtime log |
launch/spawn_failed | The system refused to start the sub-app | Usually security software or a locked file - allow-list the install folder and retry |
launch/console_hide_failed | The sub-app console window could not be hidden, so launch was aborted | Retry; contact support if it keeps happening |
api/unknown_error | Server returned an unrecognized error | Contact support with the full error text |
app_login/code_invalidapp_login/code_used | Authorization code invalid or already used | Relaunch the child app and go through a fresh authorization |
app_login/device_conflict | Account is bound to another device | Same cause as code 33 — see this note |
app_login/device_mismatch | The sign-in session does not match this machine (not the same as the account being bound elsewhere) | Do not unbind — it will not help. Just sign in through the browser again |
app_login/disabled | Child-app sign-in is temporarily turned off site-wide | Retry later, or check the site / forum announcements |
app_login/risk_stepup | Risk control triggered; email verification required first | Complete the email verification, then retry |
app_modules/no_subscription | The account has no active subscription at all | Redeem a code or renew, then retry |
app_modules/rate_limit | Too many calls (per-minute cap) | Wait a minute and retry; if it keeps happening the child app is retrying abnormally — contact support |
app_session/branch_invalid | Invalid version branch | Update the client to the latest version |
app_session/hwid_changedapp_session/hwid_mismatch | This machine device ID does not match the bound one | See Switched to a new computer |
app_session/no_hwid | Cannot read this machine device ID | Same cause as code 100 — see Internal errors that need support |
app_session/software_archivedapp_session/software_disabled | The product is delisted or disabled | Not an account problem — watch the site / forum announcements |
apps/manifest_corrupt | The server-side file manifest is malformed | Contact support and say which product and version |
apps/no_release | This version line has no published release yet | Pick another version line in the client, or wait for the release |
apps/pack_unavailable | Installer package temporarily unavailable | Retry later; contact support if it persists |
auth/banned | Account is banned | Contact support |
auth/device_locked | Account is bound to another device | See Switched to a new computer |
auth/device_mismatch | This machine does not match the device bound at sign-in | See Switched to a new computer |
auth/session_expired | Your sign-in has expired | Sign in again in the client |
enc/stale | Your system clock is too far off from the server | See System clock is wrong. This is the most common one here, and you can fix it yourself |
any other enc/… | Secure channel error (usually an outdated client) | Update the client; if it persists contact support with the full error |
license/expired | Subscription has expired | Renew or redeem a new code, then retry |
license/frozen | Subscription is frozen | Contact support to find out why |
license/none | No active subscription for this product | Redeem a code in your account first |
license/revoked | Subscription was revoked | Contact support |
net/request_failed | Cannot reach the server | See Cannot reach the service |
For a code that is not listed, contact support using the format in the last section — the code itself is the single most useful clue, so always include it verbatim.
About "Please launch through the launcher"
That message maps to code 10. If you see it even though you did launch from the client, the child app is likely outdated — download the latest version.
Older builds may also report code 11 ("parent process is not the launcher"). That check has been removed; seeing it means the build is out of date.
First, check which account the browser is signed in as
Read this before you unbind
The authorization page issues the grant for whichever account is signed in to your browser. If that is your other account, unbinding will never help — you unbind account A while account B is the one being authorized.
The page shows "Authorizing as" together with the email. Verify it before approving; if it is wrong, use "Switch account" on that page.
Only after confirming the account is correct does code 33 mean a genuine device binding: unbind at hoozi.cc/me/account and retry.
device_conflict and device_mismatch are not the same thing
Both say "device", but they call for opposite actions:
app_login/device_conflict(same cause ascode 33) = the account is bound to another machine, so unbinding helpsapp_login/device_mismatch= this sign-in session does not match this machine, regardless of which device the account is bound to, so unbinding does nothing — just sign in again
Treating the second as the first is the case where unbinding a hundred times still will not fix it.
Internal errors that need support
1 / 2 / 99 / 100 mean an internal program error with no self-service fix. The most common cause of 100 (and of app_session/no_hwid) is failure to read this machine hardware identifiers — if you are on a virtual machine, a stripped-down Windows build, or have edited your BIOS information, please mention that.
Quote the full error text and this section name when contacting support.
The client has been replaced by another program
These signs suggest the client files on your machine have been altered by third-party software:
- The client is installed but behaves oddly, or child apps keep failing
- In the properties of
hclient.exein the install folder, the product name is not HClient, or the copyright is not HOOZi
How to check: locate hclient.exe in the install folder, right-click → Properties → Details, and verify three fields:
| Field | Expected |
|---|---|
| Product name | HClient |
| Copyright | © HOOZi |
| Product version | Matches the version shown on the client's About page |
If any field does not match, stop using it. Instead:
- Uninstall the client from Control Panel
- Run a full antivirus scan
- Reinstall from the official site only
Do not download from third parties
Installers from non-official sources (cloud-drive reposts, chat group files, "portable" or "no-login" builds) are the most common cause of this. Only obtain the client installer from the official site.
System clock is wrong
The client and child apps verify your system time. A drift over 5 minutes blocks startup (code 12).
Windows Settings → Time & language → Date & time → turn on "Set time automatically", then click "Sync now". Also confirm your time zone is correct — with a wrong time zone the displayed time may look right while the actual value is off.
If you are certain your clock is correct and still get
code 12: update to the latest child app. Older builds reported the same code when the time servers were unreachable (corporate, campus, and hotel networks often block the time-sync port), which looked like a clock error and usually went away after a restart. That false alarm is fixed — an unreachable time server no longer blocks startup.
Switched to a new computer
An account is bound to a single device. Changing machines, reinstalling Windows, or replacing the motherboard changes the device identifier, which triggers a device mismatch (code 18) or "bound to another device" (code 33).
Perform a device unbind at hoozi.cc/me/account, then bind on the new machine. Unbind rules (allowed count, cooldown) depend on your license type and are described on that page.
Check three things before unbinding
1. Which account you are signed in as. This is the classic trap for people with more than one account: you unbind account A while the child app authorizes as account B — whichever one the browser is signed in to. In that case unbinding will never help.
2. "Device unbind" is not "license unbind". They are two separate features in the account center — a license unbind returns the license and issues a new key; it does not release the device binding. To move to another machine you want device unbind.
3. If the error says "version mismatch" or "could not be read", unbinding will not help. For the first, update both the client and the child app; for the second see Internal errors that need support. Only when the two device codes in the error are clearly different did you actually change machines.
"Cannot reach the service"
First rule out your local network: try a different connection (a phone hotspot, for example).
If it still fails on another network, it is most likely a temporary server-side condition. Retry later — there is no need to reinstall the client or redeem a new license.
Not covered here?
This manual is expanded over time. For anything not listed, contact support and describe: what you did → what you expected → what actually happened, with a full screenshot of the error.