By Remote desktop editorial team · Last verified [date] · Current release [tag]
Open the main window
After install, start RustDesk from Start. Confirm Your ID and the one-time password are visible. The right side holds the field for another ID.
Connect
On the controlling PC, enter the peer ID and connect. Accept on the remote side (or use a permanent password later). Move the mouse once. Related: installed, file transfer, troubleshooting.
Keep it simple
Leave Network self-host fields alone until a public-server session works. Keep both machines awake. Home: /.
Extra remote desktop context
Prefer GitHub Releases for rustdesk/rustdesk when you need rustdesk--x86_64.exe or rustdesk--x86_64.msi. ARM64 peers take rustdesk-*-aarch64.exe from the same tag. Public copy says the current release rather than hardcoding dotted versions.
Wake both machines, confirm Your ID, and move the mouse once before you chase self-host, unattended passwords, or file transfer trees. Skip Softonic-style wrappers. Related: download safe, releases, GitHub, home.
Lab images may block unknown executables. Use a PC you control or an approved channel. Sleep and wrong IDs kill more sessions than codec choice. Update through the same GitHub door you used to install. Comparison shape: vs AnyDesk.
Tags are bare numbers without a v prefix. Nightly builds exist for testers; everyday installs prefer stable tag assets. Read AGPL-3.0 licence text on the repo before redistributing modified builds.
More remote desktop context for Windows
Prefer GitHub Releases for rustdesk/rustdesk when you need rustdesk--x86_64.exe or rustdesk--x86_64.msi for remote desktop on Windows. ARM64 peers take rustdesk-*-aarch64.exe from the same tag. Public copy says the current release rather than hardcoding dotted versions in HTML.
Wake both machines, confirm Your ID, and move the mouse once before you chase self-host, unattended passwords, or file transfer trees for remote desktop. Skip Softonic-style wrappers. Related: download safe, releases, GitHub, home, vs AnyDesk.
Lab images may block unknown executables. Use a PC you control or an approved channel when you need a clean remote desktop path. Sleep and wrong IDs kill more remote desktop sessions than codec choice. Update through the same GitHub door you used to install.
Tags are bare numbers without a v prefix. Nightly builds exist for testers; everyday remote desktop installs prefer stable tag assets. Read AGPL-3.0 licence text on the repo before redistributing modified builds. First-hour notes live on /installed. Machine chooser: for this computer.
A successful remote desktop connect on two machines you trust beats stacking three mirrors. Keep one Start Menu entry. Prefer the Flutter x86_64 exe or msi on the stable tag unless you have a specific reason to take another asset. Sciter-labelled builds appear as legacy UI paths on some tags.
Frequently asked questions
What do I need on first run?
Your ID on both PCs, a waking peer, and the one-time password or accept prompt. Prefer GitHub Releases for rustdesk/rustdesk, confirm the asset name before you run it, and keep one update door for remote desktop on Windows.
Do I need a permanent password immediately?
No. Leave unattended setup for later. unattended. Prefer GitHub Releases for rustdesk/rustdesk, confirm the asset name before you run it, and keep one update door for remote desktop on Windows.
Where do Windows files come from?
GitHub Releases for rustdesk/rustdesk. Prefer rustdesk-*-x86_64.exe or .msi. Related: releases. Prefer GitHub Releases for rustdesk/rustdesk, confirm the asset name before you run it, and keep one update door for remote desktop on Windows.