Client · Common Issues
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 (including the code NN in parentheses) when contacting support — it saves a lot of back-and-forth.
Error code reference
A chain of checks runs when a child app starts; any failure shows a message with a code NN. The numbers belong to two different sign-in paths — identify yours first:
- Client launch — you press "Launch" inside the HOOZi client. Codes 10–21.
- Browser sign-in — the child app opens a browser for you to sign in (used by some products, e.g. DMA tools). Codes 30–33.
Both paths can hit the network / encryption codes (40 and above).
Client launch (10–21)
| code | Meaning | What to do |
|---|---|---|
| 10 | Not launched through the client | Launch from the HOOZi client; do not double-click the child app's exe |
| 12 | System clock too far off, or time server unreachable | 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 server's new 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 |
| 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 |
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.
Browser sign-in (30–33)
| code | Meaning | What to do |
|---|---|---|
| 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 the note below first, then consider unbinding |
code 33 — first, check which account the browser is signed in as
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.
Network and encryption (40–52)
This family is rarely caused by anything you did, and the handling is nearly identical.
| code | Meaning | What to do |
|---|---|---|
| 50 | Network failure (DNS / connection / timeout) | Check your network and retry; try another network |
| 51 | Request rejected by the server, usually still a local clock skew | See System clock is wrong |
| 40–44 / 52 | Encrypted channel problem, or the server returned an error | Update to the latest version; contact support with the full message if it persists |
Contact support (1 / 2 / 99 / 100)
These indicate an internal failure with no self-service fix. The most common cause of 100 is failure to read this machine's hardware information — if you are on a virtual machine, a stripped-down Windows build, or have modified BIOS information, mention that.
Quote the full error text and the name of this section 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 syncing errors out, your network is likely blocking the time-sync port (common on corporate, campus, and hotel networks). Try a different network.
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 two 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.
"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.