Most "it installs but won't connect" reports on Windows clients come down to three things, and none of them are the installer.
1. Installed is not the same as ready
A desktop client usually ships a virtual network adapter. The installer puts the binary in place, but the adapter is created only when you press Connect for the first time — and at that moment Windows raises a UAC-style prompt asking whether to allow the adapter to be created.
If that prompt is dismissed (or the user clicks No because it looks suspicious), the app opens, the tray icon appears, and the status line stays empty. Nothing errors out. The window simply sits there, which is why people conclude "the install failed" and reinstall — which resets the same state and reproduces the same silent failure.
2. Firewall rules, not the firewall switch
The other half of the problem is the Windows firewall. The correct fix is to allow the client process and the virtual adapter, not to turn the firewall off. Turning it off "works" long enough to confirm the diagnosis, then gets left off, which trades a connection problem for a security problem.
A quick test that separates the two: with the client connected, open a lightweight page. If the status line shows a route name and a latency number but pages never load, the tunnel is up and the problem is on the firewall/resolver side. If the status line is blank, the adapter permission is the thing to look at.
3. Autostart and the tray are separate switches
Closing the main window only hides it; the process keeps running in the tray. Two different places control whether it starts with Windows (the client's own setting and Task Manager → Startup), and they overwrite each other. If someone disabled one and not the other, the behaviour looks random across reboots.
A five-minute checklist
- Uninstall any older build, reboot, then install the current one. Two builds side by side produce two tray icons and flapping connections.
- On the first Connect, allow the adapter prompt. If it was already denied, the network adapter can be re-enabled from the adapter list.
- Add a firewall rule for the client and the adapter; leave the firewall on.
- Confirm the status line shows a route and a latency value before testing speed.
- Check Task Manager → Startup once, so autostart matches the client setting.
I keep a more detailed Windows-specific write-up, including the per-platform permission prompts and a five-platform compatibility table, at QuickQ desktop setup notes — it's a third-party handbook, not an official channel, and it documents where each prompt appears rather than promising a fix.
The short version: treat "installed" and "ready" as two different states, and check the adapter permission before touching the installer.
Top comments (0)