Use the Cyberdriver 1.x beta only when you specifically need the newer Windows service path for boot-time startup or Windows login-screen control.
Stable install: Legacy Cyberdriver
Legacy Cyberdriver is the default stable install path for desktop automation today. It does not require inbound firewall ports and works well for machines where a user session is already available.Run the PowerShell installer
Open PowerShell and run this installer script. It downloads legacy Cyberdriver
v0.0.41, adds it to your user PATH, and verifies the download.Join Cyberdesk
Close and reopen PowerShell, then join your machine with an organization API key from the Cyberdesk dashboard.After the key is saved, the desktop should appear in Cyberdesk -> Desktops.
Connect and test
From the Cyberdesk dashboard, open the desktop and click the Desktop Tools button. Verify that it connects and you can control the computer.
Create your first workflow and run
Now that your desktop is connected, create your first workflow and then create your first run. Let us know if you have any trouble.
[BETA] Cyberdriver 1.x Windows install
Cyberdriver 1.x beta is based on RustDesk and currently supported for Windows only. Use this beta path when you need Cyberdriver to run as a Windows service, start at boot, or control the Windows login screen.Administrator is required for the current Windows installer because Cyberdriver installs a system service. After installation, users can open and use the Cyberdriver app normally; they do not need to run the app as Administrator day to day.
Run the PowerShell installer
Open PowerShell as Administrator and run this beta installer script. It downloads Cyberdriver If Windows warns that the installer is not commonly downloaded, choose More info, then Run anyway. The beta MSI is not yet code-signed.
1.0.2, installs Cyberdriver as a Windows service, adds Cyberdriver to PATH, verifies the CLI, and opens Cyberdriver.Paste your API key
Open Cyberdriver from the Start menu. In the Cyberdesk tunnel card, paste an organization API key from the Cyberdesk dashboard and click Save.After the key is saved, the desktop should appear in Cyberdesk → Desktops.
Connect and test
From the Cyberdesk dashboard, open the desktop and click the Desktop Tools button. Verify that it connects and you can control the computer. Cyberdriver will now persist on your machine, even across shutdowns.
Create your first workflow and run
Now that your desktop is connected, create your first workflow and then create your first run. Let us know if you have any trouble.
Why Administrator Is Required For The Beta MSI
The Cyberdriver 1.x beta Windows release is service-first. The MSI installs intoProgram Files, registers a Windows service, and adds Cyberdriver to the machine PATH, which requires Administrator.
This is what enables:
- Cyberdriver starting when the machine boots.
- Remote access before a user logs in.
- Windows login screen access.
- More reliable unattended automation after shutdowns and restarts.
Updating Cyberdriver 1.x beta
You can update Cyberdriver1.0.0+ from the Cyberdesk dashboard without manually opening RDP as long as the existing Cyberdriver service is healthy enough for Cyberdesk to connect.
We are working on making this process even more seamless. For now, the dashboard update flow is the recommended way to update Cyberdriver
1.0.0+ without manually RDPing into the machine.Open Cyberdriver Web
In the Cyberdesk dashboard, open the desktop and click Desktop Tools. For Cyberdriver
1.0.0+, this opens the live Cyberdriver Web stream by default.Start the update from the sidebar
If an update is available, the right sidebar shows an Update button. Click it to start the guided update flow.
Confirm there are no active runs
Cyberdesk blocks the update if the desktop currently has a running or scheduling run. If no run is active, confirm that no run is about to start on that desktop.
Approve Windows prompts if needed
Cyberdesk runs the update through the existing Cyberdriver tunnel. If Windows shows an administrator prompt in the stream, approve it. The stream may briefly disconnect while the MSI updates or restarts the service.
Troubleshooting
Corporate TLS Inspection and Firewalls
Cyberdriver needs outbound access to Cyberdesk Cloud over HTTPS and secure WebSockets. Most enterprise networks work without inbound firewall changes because Cyberdriver initiates outbound connections, but corporate TLS inspection or strict proxy rules can still interrupt the tunnel. Cyberdriver validates TLS certificates. Cyberdesk Cloud uses publicly trusted certificates, and Cyberdriver uses public CA roots plus the Windows certificate store when available. If a firewall or proxy intercepts TLS and re-signs Cyberdesk traffic with a private enterprise CA, Cyberdriver may reject the connection if that CA is not trusted by the service context. Common symptoms include:- Cyberdriver diagnostics show
api_key_configured = true. - The Cyberdriver service status is
ready. - The Cyberdesk tunnel stays in
reconnecting. last_errormentionsinvalid peer certificate: UnknownIssuer.
- Confirm the machine can reach Cyberdesk Cloud over HTTPS.
- Confirm Cyberdesk WebSocket tunnel traffic is not blocked or intercepted.
- Check whether the presented certificate issuer is a corporate proxy instead of a public CA.
- If a corporate issuer is present, either bypass inspection for Cyberdesk or deploy the corporate root CA for the Cyberdriver service context.
- Restart or reopen Cyberdriver and retry the connection.
What should happen after setup
Once connected:- The machine appears online in the Cyberdesk dashboard.
- Other users in the same Cyberdesk organization can connect through Cyberdriver.
- RustDesk peer IDs stay under the hood; the UI shows Cyberdesk machine names and IDs.
- Desktop Tools can screenshot, click, type, scroll, use clipboard, access files, and run shell commands.
Advanced topics
Desktop Tools
Use screenshots, mouse, keyboard, files, clipboard, and shell commands from Cyberdesk.
Diagnostics and logs
Collect logs and state when something goes wrong.
Keepalive
Keep idle machines lightly active during long-running operations.
Remote management
Understand remote update and shutdown behavior.
Display reliability
How Cyberdriver handles RDP disconnects and virtual displays.
Custom hosts
Route Cyberdriver through your own proxy domain.
Legacy Cyberdriver
Stable Python-based client for most installs.