A tray icon at login only means the UI started. Proxy readiness also needs the core, optional subscription refresh, a successful system-proxy write, a live network, and—if you use it—Tun service mode. Any race looks like “it’s on, but the browser is direct.”
Cold-start test: reboot → open a target site → check Connections.
Is it autostart or proxy readiness?
| Sign | Meaning | Next step |
|---|---|---|
| No tray icon at login | Autostart blocked | Check the startup entry |
| Tray present, no hits | Chain not finished | system proxy |
| Nodes empty | Subscription | update failed |
| TUN shows nothing | TUN start | Tun start failed |
Two kinds of failure
No tray icon → autostart blocked. Tray present but no hits → chain didn’t finish. System proxy deep dive: system proxy.
Four common causes
- System proxy not auto-enabled: check launch options; NIC may not be ready at write time.
- Boot subscription update fails: update failed.
- Tun empty: Tun start failed.
- Browser extension override: private window comparison.
Delayed start
Task Scheduler delay of 30–60 seconds often beats reinstalling. Verify with a full reboot.
Acceptance
- After reboot, Connections shows hits.
- Retest Tun tools if required (Tun & AI).
- Still silent: firewall.
Stop
Don’t stack endless startup entries. Builds: download center.