Windows setup

How to set up ErrorX on Windows

Install the ErrorX client on Windows 10 or later, sign in with your account, and get a system-wide encrypted tunnel running. Around five minutes, and one administrator prompt.

5 min read5 stepsVerified against the current build
Setting up ErrorX on Windows

What you need

  • Windows 10 or later, 64-bit
  • x64 or arm64 processor
  • Administrator rights for installation
  • An active ErrorX subscription
  • About 200 MB of free disk space
  • A Google, Facebook or Discord account to sign in with
01

Download the right build

Open the ErrorX download page and take the Windows installer. Most machines need the x64 build; take arm64 only if you have a Snapdragon-based PC such as a Surface Pro X. The portable ZIP is the same app without a Start menu entry or an uninstaller — pick it only if you specifically want to avoid installing.

Stable releases publish a SHA256SUMS file next to the downloads if you want to verify what you got before running it.
02

Run the installer

Right-click the installer and choose Run as administrator, then follow the wizard — the defaults are correct. Windows SmartScreen may warn you about an unrecognised publisher; choose More info, then Run anyway. If ErrorX is already running, the installer closes it for you before copying any files.

The installer needs administrator rights. This is the only elevation the app requires during setup — the app itself does not run elevated afterwards.
03

Sign in through your browser

Launch ErrorX and press Continue with ErrorX. Your default browser opens the ErrorX login page; sign in with Google, Facebook or Discord, and the browser hands you straight back to the app. The app never asks you for a password and never shows a login form of its own.

If the browser tab stays open after the app takes focus, you can close it — the handoff is already done.
04

Approve the helper service, once

The first time you press Start, Windows shows a UAC prompt so ErrorX can register a small background service called ErrorXHelperService. That service is what creates the network interface your traffic travels through. Approve it once; you will not be asked again on later connects.

Command Prompt (admin)
sc query ErrorXHelperService
You can confirm it later from an elevated prompt with the command below. RUNNING means everything is in order.
05

Press Start and pick a routing mode

Hit Start. The app downloads your encrypted config, claims one of your subscription's device slots and brings the tunnel up. Leave the mode on Rule — it sends international traffic through ErrorX while leaving Bangladeshi and locally-cached destinations on the direct path, which is faster than tunnelling them.

Use Global when you want every single connection tunnelled, and Direct to compare against your normal route without disconnecting.

Check that it actually helped

Test against something genuinely international — a BDIX speed test was already fast and will tell you nothing.

  • Note your download speed from a cloud or GitHub target before connecting
  • Connect, then run exactly the same test again
  • Compare the two numbers — that difference is what you are paying for
  • Your dashboard shows the device as online while the tunnel is up
Open the speed test

If something goes wrong

Start fails and no UAC prompt appears
The helper service is not running. Run `sc query ErrorXHelperService` from an elevated prompt — if it reports anything other than RUNNING, restart ErrorX and press Start again to re-register it.
Microsoft Store apps lose internet access in system proxy mode
Windows blocks Store apps from reaching local addresses, which is what system proxy mode needs. Open Tools in the app and run the Loopback unlock tool once.
SmartScreen blocks the installer
Choose More info, then Run anyway. This appears on new releases until enough people have downloaded them, and it is not a sign that anything is wrong with the file.
The app says the device limit is reached
Every slot on your plan is held by a device that is online right now. Stop ErrorX on another machine, or disconnect it from Dashboard → Subscription, then press Start again.