How do I update AnyDesk on Linux? First identify whether your copy came from an AnyDesk DEB/RPM repository, a downloaded installer, or a portable .tar.gz archive. Repository installations use the distribution’s package manager as root; installer-based copies use AnyDesk’s reinstall flow; portable archives must be replaced manually because they are not repository packages. Afterward, run anydesk --version to check the installed version.
This guide follows AnyDesk’s Linux documentation: Update AnyDesk, the Linux command-line reference, and Install AnyDesk.
As an Amazon Associate I earn from qualifying purchases.
Identify how AnyDesk was installed
The correct update procedure depends on the installation source. A package-manager command can update a package installed from a configured AnyDesk repository, but it does not update a standalone installer copy or a portable archive. AnyDesk describes DEB and RPM packages as its primary Linux formats and also provides a portable .tar.gz archive.
Recommended Free Tools
| How the copy was obtained | Update method | Privileges and scope | Important limitation |
|---|---|---|---|
| AnyDesk DEB repository on Debian or Ubuntu | Run apt upgrade anydesk |
AnyDesk specifies root privileges | Only the package visible to the configured APT sources is updated |
| AnyDesk RPM repository on RHEL or CentOS | Run yum upgrade anydesk |
AnyDesk specifies root privileges | It does not replace a separate installer or archive copy |
| AnyDesk RPM repository on Fedora | Run dnf upgrade anydesk |
AnyDesk specifies root privileges | The command must target the repository-managed package |
| AnyDesk RPM repository on SUSE | Run zypper upgrade anydesk |
AnyDesk specifies root privileges | A portable executable is outside this transaction |
| Downloaded standard installer | Download the latest installer, run it, remove the current version when prompted, then run the installer again | Installer-based route; standard-client instructions | Custom clients have separate update guidance |
Portable .tar.gz archive |
Obtain a newer archive and replace the extracted copy | No package installation or administrative privilege is required to run the archive | No service, Unattended Access, reconnect after reboot, or login-screen access |
Repository installation clues
If you deliberately added AnyDesk’s DEB or RPM repository and installed the package through your distribution’s package manager, use the repository route below. The package manager must be able to see the AnyDesk repository; otherwise it cannot retrieve a newer package. A command that reports no candidate or no upgrade is a reason to check the configured source and installation history, not a reason to try every package manager in turn.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Keep the package name exactly as AnyDesk documents it: anydesk. The distribution family determines the command, while the package name remains the same in all four documented examples. Do not substitute a command from another distribution family simply because it is available on your system.
Downloaded-installer clues
If you downloaded an installer file and launched it directly, use the installer route rather than an apt, yum, dnf, or zypper command. A downloaded installer is not automatically the same thing as a package-manager installation. AnyDesk’s update article covers standard clients. A custom client obtained through the my.anydesk portal has separate update guidance, so identify the client type before downloading a replacement.
Portable-archive clues
A portable archive runs from its extracted directory and is not the same as an installed DEB or RPM package. It can be used without installation or administrative privileges. Do not assume that a package-manager upgrade will find or replace it. If several copies exist, note which extracted directory your launcher or desktop shortcut uses before replacing files.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose the update route before changing anything
A short decision check prevents the most common failed updates:
- If the client was installed from an AnyDesk repository, use the command for the Linux distribution family.
- If a downloaded installer was opened directly, follow the documented uninstall-and-reinstall sequence.
- If the client is a custom build, obtain its update instructions from the organization or my.anydesk portal rather than applying the standard-client sequence automatically.
- If the client is an extracted
.tar.gz, download and extract a newer archive, then replace the copy that you actually launch. - After any route, run
anydesk --versionand make sure the command refers to the updated copy.
This distinction also matters for capabilities. A package or installer deployment can provide an installed client and service, while the portable archive intentionally does not install the service and lacks several installed-client functions. Select the format that matches the way the machine is administered, not merely the format that is quickest to download.
Update a repository installation from the terminal
AnyDesk lists one command for each supported distribution family. Open a root shell or otherwise execute the command with root privileges. Keep the package name exactly as shown: anydesk. Finish the package-manager transaction before starting AnyDesk again; otherwise you may be testing the old executable while an update is still pending.
Debian or Ubuntu
- Confirm that this is the DEB/repository installation.
- Open a terminal with root privileges.
- Run
apt upgrade anydesk. - Allow the package manager to resolve and install the available AnyDesk update.
- Wait for the transaction to finish without a permission or dependency error.
- Verify the result with
anydesk --version.
The command upgrades the AnyDesk package that the configured APT sources provide. It is not a general updater for every AnyDesk copy on the machine. If you have both a repository package and a portable directory, only the package is addressed by this command.
RHEL or CentOS
- Use this route only when the RPM package was installed through the AnyDesk repository.
- Open a root shell.
- Run
yum upgrade anydesk. - Complete any confirmation requested by the package manager and let the transaction finish.
- Check the installed version with
anydesk --version.
A successful YUM transaction concerns the repository-managed RPM. It does not establish that a separately downloaded installer or archive has changed, so verify the executable you intend to run.
Fedora
- Verify that the installed client is the repository-managed RPM package.
- Run a root shell.
- Execute
dnf upgrade anydesk. - Let DNF finish the transaction before launching AnyDesk again.
- Run
anydesk --versionto confirm which version is now installed.
If DNF says there is nothing to upgrade, compare that result with the version output and the repository configuration. “No update” describes what DNF can currently obtain; it does not validate an unrelated copy.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
SUSE
- Use this command for an AnyDesk package supplied through the configured SUSE repository.
- Open a root shell.
- Execute
zypper upgrade anydesk. - Accept the package-manager prompts that apply to the transaction.
- Verify with
anydesk --version.
Keep the terminal output until the transaction completes. If Zypper stops because of authorization or package-resolution problems, correct that issue and rerun the documented command instead of changing to an unrelated package manager.
What to do if the package manager finds no update
A message that no upgrade is available does not prove that every AnyDesk copy is current. It can mean the repository has no newer package, the repository is not configured for this system, or the running copy came from an installer or portable archive. Recheck the installation method before switching commands. Do not use a different distribution’s package-manager command merely because it is familiar.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Also distinguish a completed transaction from a command that never had permission to run. AnyDesk specifies root privileges for these repository updates. A permission error means the package was not authorized to change; version verification should happen only after rerunning the appropriate command with the required privileges.
Update AnyDesk installed with the downloaded installer
AnyDesk documents a reinstall sequence for standard Linux clients installed with its installer. This route is separate from repository upgrades and uses two installer runs when removal is requested.
- Download the latest standard AnyDesk version from the AnyDesk website. If your organization uses a custom client, obtain that client from the my.anydesk portal instead; custom clients have separate update instructions.
- Run the downloaded installer.
- When the installer asks, uninstall the current AnyDesk version.
- After the existing version has been removed, run the installer again to install the updated version.
- Start AnyDesk and run
anydesk --versionin a terminal to verify the installed executable.
The update article says this process preserves the previous version’s AnyDesk ID and settings. That preservation is useful when maintaining an existing workstation, but it does not remove the need to check the version and confirm that the expected client is running. Record any organization-specific configuration or access policy before maintenance so you can recognize an unexpected change after installation.
Why the installer route uses two runs
The documented flow is not simply “open the new file once.” The first run handles removal of the current installation when prompted; the second run performs the new installation. Stopping after the uninstall step leaves no updated client to verify. If the installer closes after removing the old version, launch the same downloaded installer again rather than assuming the first run completed the update.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Standard versus custom clients
The documented installer procedure applies to standard clients. A custom client may contain organization-specific branding, configuration, or deployment rules, so use the update instructions associated with that custom build rather than substituting the standard-client sequence. Downloading a standard client merely because it is newer can result in a client that does not match your organization’s expected configuration.
Replace a portable .tar.gz copy
AnyDesk’s portable Linux archive can be run from an extracted folder without installation or administrative privileges. It is therefore outside the DEB/RPM repository workflow. To update it, obtain a newer portable archive, extract it, and replace the old extracted copy according to how you launch that archive.
- Identify the extracted directory used by your launcher, script, or shortcut.
- Obtain a newer portable archive from the same appropriate AnyDesk distribution channel.
- Extract the new archive into a separate location so you can distinguish it from the old files.
- Replace or repoint the copy that your normal launch method uses.
- Start the replacement executable and check its version from that copy.
The key verification point is which executable is being launched. If an installed package also exists, a plain anydesk --version may report that installed command while you are testing an archive from another directory. Run the version check against the executable you actually launch, and avoid treating a successful repository transaction as evidence that portable files changed.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Capabilities that differ from an installed package
The portable archive does not install the AnyDesk service. It also does not provide Unattended Access, reconnect after reboot, or login-screen access. Those limitations matter when deciding whether simply replacing an archive is sufficient for your use case. A portable update changes the files in the extracted directory; it does not add those installed-client capabilities.
When a portable replacement is the wrong choice
If the machine must accept connections through Unattended Access, reconnect automatically after a reboot, or provide access at the login screen, the portable format does not meet those documented requirements. Choose an installed deployment path that supports the features you need and follow the corresponding repository or installer instructions.
How do I check my AnyDesk version in Linux?
Open a terminal and run:
anydesk --versionAnyDesk’s Linux command-line reference defines --version as displaying the installed AnyDesk version. Read the value returned by the command and compare it with the release you intended to install. The command is a verification step; it does not itself download or install an update.
Check immediately after an update
- Finish the package-manager transaction or the installer’s second installation run.
- Open a new terminal session if the old session was open before installation.
- Run
anydesk --version. - Confirm that the displayed version belongs to the copy you updated, especially if a portable archive and installed package coexist.
- Launch AnyDesk and verify that your expected ID, settings, and required features are present.
The update documentation states that the documented update process preserves the previous AnyDesk ID and settings. Checking those values after the version command gives you a practical confirmation that you are using the intended installation rather than an older duplicate.
If the command is not found
A “command not found” result usually means the shell cannot resolve an installed executable under that command name, or that you are working with a portable archive whose executable is in its extracted folder. Revisit the installation method: repository packages and installer-based installations should be checked using the installed command, while a portable copy must be checked from the copy you extracted and launch. Do not infer that no client exists solely from a missing command in the current shell.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallIf the version did not change
- Confirm that the update command completed successfully rather than stopping on a dependency or permission error.
- Check that you used the package manager for your distribution and the exact package name
anydesk. - Make sure the repository contains the release you expected.
- Verify that the command is not resolving a different AnyDesk copy than the one you just updated.
- For an installer-based copy, repeat the documented uninstall-prompt and second-install sequence.
- For a portable archive, replace the extracted files with the newer archive and launch that replacement.
- For a custom client, stop and obtain the custom-client update instructions instead of repeatedly installing the standard client.
Repository, installer, and portable routes compared
| Comparison point | Repository package | Downloaded installer | Portable archive |
|---|---|---|---|
| How it is updated | Distribution-specific package command | Run installer, remove current version when prompted, run installer again | Download, extract, and replace the launched copy |
| Administrative privilege | Root privileges specified by AnyDesk | Use the installer’s requested permissions | Not required to run the archive |
| Package-manager scope | Yes, for the configured AnyDesk repository package | No | No |
| Service installation | Installed-client route | Installed-client route | Service is not installed |
| Unattended Access and reboot reconnect | Available to evaluate as installed-client features | Available to evaluate as installed-client features | Not provided by the portable archive |
| Login-screen access | Available to evaluate as an installed-client capability | Available to evaluate as an installed-client capability | Not provided by the portable archive |
| Custom-client handling | Follow the repository associated with that deployment | Use custom-client instructions | Replace only with the appropriate custom archive |
The table is a selection aid, not a claim that one route updates every other route. Always match the procedure to the copy that is actually installed or launched.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common update mistakes and their fixes
Using a repository command for an installer copy
Installing AnyDesk from a downloaded file does not automatically make it an APT, YUM, DNF, or Zypper package. If the package manager reports that AnyDesk is absent or unchanged, return to the installer procedure instead of forcing a package transaction.
Using the wrong distribution command
The commands are distribution-specific. Debian and Ubuntu use apt upgrade anydesk; RHEL and CentOS use yum upgrade anydesk; Fedora uses dnf upgrade anydesk; SUSE uses zypper upgrade anydesk. Running a command from another family can fail or address a different package source.
Running without root privileges
AnyDesk’s update article specifies root privileges for the repository commands. A permission error means the package transaction was not authorized. Re-run the appropriate command from a root shell rather than changing the command to a different package manager.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Stopping after the first installer run
The installer flow can remove the current version when prompted. You must run the installer again to install the update; otherwise the version check may show no installed client.
Expecting portable archives to provide installed-client features
Replacing a portable archive updates the files you run, but it does not add the service, Unattended Access, reconnect after reboot, or login-screen access. If those capabilities are required, evaluate an installed package or installer-based deployment instead of treating the archive as equivalent.
Updating a custom client as if it were standard
Custom clients have separate update guidance. Identify the client type before downloading a replacement, and use the organization’s custom-client instructions rather than the standard-client flow.
Checking the wrong executable
Multiple AnyDesk copies can make a correct update appear ineffective. A repository command may update the installed package while a launcher still opens a portable directory, or a version command may resolve the installed executable while you are testing an archive. Tie the version check to the copy you intend to use and confirm the running client’s ID and settings.
Does an update change the AnyDesk ID or settings?
AnyDesk’s July 31, 2025 update documentation states that updating preserves the previous version’s AnyDesk ID and settings. The statement applies to the documented update procedures; it is not a reason to mix installation methods or skip version verification. After the update, launch the client and confirm the expected ID, settings, and access features, particularly on a managed workstation.
Documentation dates and scope
The official Update AnyDesk article was published July 31, 2025 and contains the Linux repository and installer procedures. The Linux command-line article was published July 17, 2025 and updated November 4, 2025; it defines --version as the installed-version display parameter. The installation article was published July 9, 2025 and updated December 30, 2025; it explains the DEB, RPM, and portable archive formats and the portable limitations. Procedures can change, so consult those pages if your client or distribution presents different prompts.
A repeatable Linux update checklist
- Identify the source: repository package, downloaded installer, custom client, or portable
.tar.gz. - Note which distribution family and package manager apply.
- Choose the matching route and distribution command.
- Use root privileges for repository commands.
- For installer updates, complete both runs when removal is requested.
- For portable copies, replace the extracted archive rather than invoking a package-manager upgrade.
- Run
anydesk --versionafter the change. - Confirm that the reported version comes from the copy you intend to use.
- Check that the expected AnyDesk ID and settings remain present.
- Check that the required service and access features are available for your installation type.
- If the client is custom, follow its separate update guidance.
For the authoritative command definitions and current procedure wording, consult AnyDesk’s update article, Linux CLI reference, and installation documentation.
Frequently Asked Questions
How do I update AnyDesk on Ubuntu or Debian?
If AnyDesk was installed from its DEB repository, open a root shell and run apt upgrade anydesk. After the transaction finishes, run anydesk --version. Do not use this command for a downloaded installer or portable archive.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHow do I update AnyDesk on Fedora?
For an AnyDesk RPM installed from the configured repository, run dnf upgrade anydesk with root privileges. Let DNF finish, then verify with anydesk --version.
How do I update AnyDesk on RHEL or CentOS?
Use the repository route only for a repository-managed RPM. From a root shell, run yum upgrade anydesk, complete any prompts, and check the result with anydesk --version.
How do I update AnyDesk on SUSE?
For a repository-installed AnyDesk package, run zypper upgrade anydesk as root. Verify the installed version after Zypper completes.
How do I update AnyDesk installed from a downloaded file?
Download the latest standard installer, run it, uninstall the current version when prompted, and run the installer again to install the update. Then run anydesk --version. Custom clients have separate instructions.
Can I update a portable AnyDesk .tar.gz with apt or dnf?
No. A portable archive is outside the repository package workflow. Obtain a newer archive, extract it, replace the copy you launch, and check that executable’s version.
What does anydesk --version do?
AnyDesk’s Linux CLI reference defines --version as displaying the installed AnyDesk version. It verifies the executable being resolved; it does not perform an update.
Will updating AnyDesk change my ID or settings?
AnyDesk’s July 31, 2025 update documentation says the documented update process preserves the previous version’s AnyDesk ID and settings. Verify them after updating anyway, especially when multiple copies or a custom client are present.
Why does the version still look old after updating?
Check that the package transaction completed with the required privileges, that the correct distribution command and package name were used, and that the version command resolves the copy you updated. For installer copies, complete both installer runs; for portable archives, replace and launch the new extracted copy.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsDoes the portable archive support Unattended Access or reconnect after reboot?
No. AnyDesk states that the portable archive does not install the service and does not support Unattended Access, reconnect after reboot, or login-screen access.
The Bottom Line
Match the update method to the original installation source: use the documented root package command for a repository package, complete AnyDesk’s two-run installer flow for a standard installer copy, or replace the extracted files for a portable archive. Then run anydesk --version against the copy you actually use and confirm the expected ID, settings, and capabilities.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
