ProxyPass on Windows — Native Service Installation

ProxyPass on Windows — Native Service Installation

Not every device in the field runs Linux. Point-of-sale terminals, industrial workstations, office machines, Windows-based kiosks — they all run Windows, and they all need remote access.

Native Windows Service

ProxyPass runs natively on Windows as a Windows service. No Docker required. No WSL. No virtual machine. The node installs as a standard service that starts automatically on boot, reconnects after restarts, and runs in the background without a logged-in user session.

Installation is a single PowerShell command. You paste the install command, it downloads the correct executable for your architecture — x64, x86, or ARM64 for Snapdragon-based Windows devices — registers the service, and starts it. The node appears in your dashboard within seconds.

Survives Everything Windows Throws At It

Because it runs as a Windows service, the node survives:

  • User logouts
  • Remote desktop disconnections
  • Windows Updates that restart the machine
  • Power cycles

It starts with the operating system and stays running until you explicitly stop it.

Scenario: Branch Office Windows Workstations

An accounting firm has 12 branch offices across Austria and Germany. Each office has Windows workstations running specialized tax software that occasionally needs remote support. The firm's IT team is centralized in Vienna.

They install a ProxyPass node on one workstation at each branch office. Now the IT team can RDP into any branch office machine through the CONNECT proxy — without maintaining 12 VPN configurations, without asking each office's ISP to forward ports, and without relying on third-party remote desktop services that route traffic through US servers.

When a tax specialist in Salzburg calls with a software issue, the IT team in Vienna connects through ProxyPass and is on the machine within seconds. The fix takes five minutes. No travel, no VPN troubleshooting, no GDPR concerns about data routing through foreign servers.

Full Feature Parity

All three access modes work identically on Windows and Linux. CONNECT mode for TCP tunneling, REST Bridge for local HTTP devices, and File Mount for WebDAV file access. The tunnel protocol is the same. The API is the same. The dashboard shows Windows and Linux nodes side by side with the same status, the same metrics, and the same controls.

Remote restart works on Windows too — you can restart the service or reboot the entire machine through the Management API or the dashboard. Auto-update on connect keeps Windows nodes current just like their Linux counterparts.

For organizations with mixed environments — Linux servers in the data center, Windows machines at branch offices — ProxyPass provides a single solution that covers both. One dashboard, one API, one billing model. No platform-specific tooling.

Request Access →

An unhandled error has occurred. Reload 🗙

Connection lost

Attempting to reconnect...

Connection failed

The server is not reachable.