Every desktop "network client" eventually hits the same support question: it installed, why doesn't it connect? After comparing five platforms, the answer is usually not the installer — it's one permission prompt that each OS phrases differently, and that users tend to dismiss because it looks like a driver warning.

Here is the table I ended up keeping.

Platform Package First thing to allow What "denied" looks like
Windows 10/11 exe Creating a virtual network adapter Click Connect, nothing happens, status line stays empty
macOS dmg Network extension in System Settings "Cannot verify developer" then a silent no-op
iOS App Store Adding a VPN configuration Toggle flips back by itself
Android apk / store VPN config + battery whitelist Connects, then drops a few minutes after lock
Ubuntu package / CLI The client service actually running No traffic is taken over at all

Three observations that took longer than they should have:

  1. Installed ≠ ready. The adapter is created on the first Connect, not during install. If that prompt is dismissed, the app opens normally and never connects, with no error.
  2. Firewall rule ≠ firewall off. Allow the process and the adapter; don't disable the firewall to "test" and then forget to re-enable it.
  3. The tray and autostart are two different switches. Closing the window only hides it; two separate settings decide whether it starts with the OS, and they overwrite each other.

I keep the full version, with the per-platform prompt locations and a CSV of the same table, here: five-platform compatibility table. It's an independent handbook — not the vendor's site — and it records where each prompt appears and the date it was last checked, rather than promising a fix.

If you maintain anything cross-platform, the reusable lesson is smaller than the table: treat "installed" and "ready" as separate states, and check the OS-level permission before touching the installer again.