Skip to main content
Starting with version 0.0.34, Cyberdriver supports remote updates directly from the Cyberdesk Dashboard. This means you can update Cyberdriver on any connected machine without needing to manually access that machine.

​
How it works

  1. Check for updates: In the Cyberdesk Dashboard, go to Desktops and click “Check Versions” to see which machines have outdated Cyberdriver versions
  2. Update individual machines: On any desktop’s detail page, open the Tools dialog and click “Update to [version]”
  3. Bulk updates: Select multiple outdated desktops and update them all at once
When you trigger an update:
  • Cyberdriver downloads the new version
  • Creates an updater script that waits for the current process to exit
  • Restarts automatically with the same configuration and flags you originally used

​
Requirements

  • Cyberdriver v0.0.34 or later: Machines running v0.0.33 or earlier need a one-time manual reinstall to enable remote updates
  • Connected to Cyberdesk Cloud: The machine must be connected via cyberdriver join
One-time manual update required for older versionsIf your machine is running Cyberdriver v0.0.33 or earlier, you’ll need to manually reinstall Cyberdriver once using the installation instructions. After that, all future updates can be done remotely from the dashboard.You can check which of your machines need manual updates by clicking “Check Versions” in the Desktops page.

​
What gets preserved

When Cyberdriver updates remotely, it preserves all your original command-line arguments:
  • --secret (your API key)
  • --keepalive and keepalive settings
  • --black-screen-recovery and its settings
  • --add-persistent-display
  • Any other flags you used
Remote updates are the recommended way to keep Cyberdriver up to date across your fleet of machines. Combined with the “Check Versions” bulk update feature, you can update dozens of machines in seconds.

​
Update process

When you trigger a remote update from the dashboard:
  1. Download: Cyberdriver downloads the new version from GitHub
  2. Prepare: Creates an updater script with your preserved arguments
  3. Exit: The current Cyberdriver process exits gracefully
  4. Replace: The updater script replaces the old executable with the new one
  5. Restart: Cyberdriver restarts with all your original flags
The entire process typically takes 5-10 seconds. The dashboard will show a verification status once the updated Cyberdriver reconnects.

​
Bulk updates

For managing multiple machines:
  1. Go to the Desktops page in the dashboard
  2. Click Check Versions
  3. See all outdated machines at a glance
  4. Select multiple machines for bulk update
  5. Confirm and watch the progress
Machines that are disconnected or busy will be skipped automatically. You’ll see a summary of successful and skipped updates when complete.