Your remote desktop download is on the way

Two asks while the installer lands

If the project helped you, star rustdesk/rustdesk on GitHub. Stars help other Windows users find the real repository next to lookalike names.

Follow new builds via the releases feed. The feed lists current tags and asset names so you can see when rustdesk-*-x86_64.exe moves without refreshing Releases by hand.

The first hour with remote desktop

Work the eight steps in order so you do not redo settings later. Finish the download before you chase self-host extras. Confirm Your ID appears before you blame the download. Connect one trusted peer before file transfer trees. Updates use the same GitHub door you already trust. Longer install context: install on Windows, exe or msi, and for this computer.

1. Finish the Windows install. If you took rustdesk-*-x86_64.exe or rustdesk-*-x86_64.msi from GitHub Releases, run it and complete the prompts. Do not run a renamed setup from a search ad while you wait.
2. Launch once and read Your ID. Start RustDesk from Start. Pass SmartScreen only when the file came from GitHub Releases. Confirm Your ID and the one-time password appear. First run: first run.
3. Confirm architecture matched the file. x64 PCs use rustdesk-*-x86_64.exe or .msi. ARM64 PCs use rustdesk-*-aarch64.exe. About in Windows Settings shows the processor. Guide: exe or msi.
4. Connect a trusted peer. Install on a second machine you control, or ask a trusted peer for their ID. Enter the peer ID, connect, and accept. Move the mouse once. Guide: first run.
5. Try file transfer only after the screen works. Open file transfer for a small test file. Guide: file transfer.
6. Skip random mirrors. If something fails, re-fetch from GitHub Releases. Softonic-style wrappers and blog accelerators are the wrong door. Safety: is it safe. Download-safe: download safe.
7. Leave advanced extras for later. Self-host ID servers, permanent passwords, and fleet --config strings can wait until one interactive session works. Self-host: self-host. Unattended: unattended.
8. Plan the update door. Take the newer exe or msi from the same Releases page. Do not mix three mirrors. Update notes: update and uninstall.

What success looks like

You are done with the first hour when Your ID is visible, a trusted peer session moves the mouse, and you know GitHub Releases is your update door. Deepen with guides when you need self-host, unattended access, or troubleshooting.

If one peer fails, confirm sleep and network before you blame the install. Keep the original download so you can reinstall without hunting a new mirror.

Common first-hour mistakes

Stacking the GitHub exe and a second random "setup" into two Start entries wastes time when you later wonder which binary opened. Prefer one install location. Testing against a sleeping laptop is the other common mistake. Wake the peer first.

Fetching a helper named setup from a search ad is the same class of mistake as fetching RustDesk from unofficial wrappers. The GitHub rustdesk-*-x86_64.exe is complete for desktop peer use. Releases list: releases. GitHub layout: GitHub.

Borrowing a locked-down lab PC can block unknown exe files. Stop rather than forcing a helper installer. Use a machine you control when you need a clean path.

After the hour

Next useful reads: self-host, unattended, file transfer, vs AnyDesk, and the guides index. Upstream docs cover Network settings and Pro API fields in more depth than this install page.

Internal links: home, releases, GitHub, download safe, exe or msi, vs AnyDesk, troubleshooting.

Quiet first-hour checklist

• Confirm the asset name on GitHub Releases before you run it.
• Prefer rustdesk-*-x86_64.exe or .msi over renamed mirrors.
• Keep one update door so Start Menu shortcuts stay honest.
• Wake both peers before blaming the installer.

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. Read the project LICENSE before you redistribute a modified build under AGPL-3.0 terms. Prefer one door per PC so Start Menu shortcuts stay honest after upgrades.

Remote desktop sessions fail more often from sleep, wrong IDs, and blocked networks than from installer choice. Plug in power, disable sleep for the test window, and confirm the peer still shows online before you change brands.

More remote desktop first-hour context

Prefer GitHub Releases for rustdesk/rustdesk when the remote desktop download needs a clean second try. Confirm the asset name, re-run the installer, and open Your ID before you chase Softonic-style wrappers. Related: download safe, Windows install, first run.

Remote desktop success in the first hour means a trusted peer session moves the mouse and you know which Releases asset you installed. File transfer and unattended permanent passwords can wait. Self-host ID servers can wait. Keep the original download so a reinstall does not require hunting a new mirror.

Frequently asked questions

What should I do first after the download?

Finish the installer from GitHub Releases, launch RustDesk, confirm Your ID and the one-time password, then connect a trusted peer and move the mouse once before self-host or file transfer extras for remote desktop.

Which file did I download?

Usual x64 machines take rustdesk-*-x86_64.exe or the matching .msi from the current tag. ARM64 machines take rustdesk-*-aarch64.exe. Match Settings System About before you run the remote desktop installer from GitHub Releases.

Where do updates come from?

Take newer remote desktop builds from the same GitHub Releases door you used to install. Prefer one install path so Start Menu entries stay honest and you do not mix three mirrors.