RuDesk
RuDesk releases

RuDesk changelog

Official RuDesk release notes for Windows, macOS, Linux and Android.

RuDesk 1.0.27

Critical permanent-access, update and installation paths were fixed on supported platforms.

Current version
Updates verify file size and SHA-256 before installation. Windows offers standard 64-bit and separate 32-bit Legacy packages.

Release history

Key changes from earlier releases.

RuDesk 1.0.26

Release

Remaining traces of the former brand were removed and Windows-client launch reliability was improved.

  • Connection status shows a clear state and latency without exposing internal infrastructure addresses or ports.
  • The Windows client restores an existing window in the interactive user session instead of leaving the UI invisible in Session 0.
  • The Windows portable edition uses the RuDesk directory instead of the former application name.

RuDesk 1.0.25

Release

Release infrastructure and desktop-interface refinements.

  • Added website-controlled support links and information blocks that the app can receive without a new build.
  • Improved notifications and device-status display in the address book.
  • Fixed desktop-client and session-panel visual defects.
  • Windows provides standard 64-bit and separate compatible Legacy packages, including a clear 32-bit choice on the site.

RuDesk 1.0.24

Release

Remote-control and input compatibility improvements.

  • Fixed Delete and Backspace delivery between Windows devices.
  • Improved keyboard layouts, clipboard exchange and copying of selected text.
  • Improved multi-monitor switching and remote-device diagnostics.

RuDesk 1.0.9

History

The first transparent release-publication and update-check flow.

  • Configured the new-version check through the official API.
  • Added SHA-256 verification for update files where available.
  • Aligned versions between the website, update API and client.

RuDesk 1.0.8

History

Cross-platform compatibility improvements.

  • Improved connection compatibility between macOS and Android.
  • Improved client-to-client data exchange stability.
  • Prepared further mobile-client improvements.