Remote Desktop Manager - MacOS

Ctrl + k

Remote Desktop Manager

MacOS

Remote Desktop Manager

Windows
MacOS
Android
iOS
Linux

Announcement

Monitor this forum to get notified when a new update is available

Support

Support forum for Remote Desktop Manager macOS

Integrated Security on SQL Server data source doesn't work with RDM Mac 5.5.0.0

Bug Report

Bug report forum for Remote Desktop Manager macOS

Feature Request

Feature request forum for Remote Desktop Manager macOS

Recent Posts

Published 4 hours ago

Undocked always starts full screen

Hi Carl, screen shot attached. I had it set at default with Screen sizing mode set to dynamic resolution, it works great until RDM is restarted. I tried setting it at a fixed size and it does maintain that after program restart, but unfortunately the window cannot be resized to meet the need at the time. Thanks again for having a look at this. Mike [image]

Published 4 hours ago

Undocked always starts full screen

Hello, Could you please provide a screenshot of the entry properties under RDP → Display ? Also, could you let me know what happens if you change the remote desktop size? I’m currently unable to reproduce the issue on my end. Best regard

Jesse Galarneau

Published 11 hours ago

Find Quickly Window No Longer Working Reliably

Hi, Remote Desktop Manager Mac version 2026.1.10.3 is now available and includes a fix for this issue. If the problem persists, please don’t hesitate to contact us. Best regards,

Jesse Galarneau

Published 12 hours ago

Rollback feature built into Remote Desktop Manager

Hi, Thanks for taking the time to share this, it’s a solid suggestion. I’ve created a ticket internally to create a rollback feature for RDM Mac. Our roadmap is quite full at the moment, but I’ve flagged this as a strong candidate for a future cycle so it’s definitely on our radar. Best regards,

Feature Request

Eduard Sepúlveda López

Published 16 hours ago

Configured Shortcuts Do Not Work Inside RDP Session

Hello kniem , Thanks for reaching out to us! What you are seeing is usually expected behavior on macOS: RDM’s configured shortcuts are handled by the RDM app itself, and when you click into the embedded RDP session, the RDP view takes keyboard focus and captures keystrokes to send them to the remote machine. In that state, RDM often won’t receive the key event needed to trigger actions like “Type Clipboard”, so the shortcut only works when the main RDM window is the active focus (as you observed), even on the latest available RDCM version. To confirm whether this is simply a limitation of the embedded session (vs. something we can tweak), could you share a few details? Session mode Is the RDP session running embedded (inside an RDM tab) or opened in a separate/external window? If you switch to the other mode, does the hotkey behavior change? Shortcut scope and combo Is the hotkey defined as “global/system-wide” (if that option exists in your build) or only as an RDM shortcut? What exact key combination are you using? (Some combos are intercepted by macOS or by the remote OS.) RDP engine/settings Which RDP implementation is RDM using in your setup (if there is a selectable engine/setting)? Any “send system shortcuts to remote” / keyboard passthrough-type settings enabled? Permissions (macOS) Does RDM have Accessibility and/or Input Monitoring permissions enabled in macOS Privacy & Security settings? (This mainly matters if you expect global hotkeys while another view/app has focus.) Thanks in advance! Best regards,

Published a day ago

SSH connection via HAProxy (TCP + TLS, custom OpenSSL command) broken since 2025.3.x

Dear Robert, Thank you, it's working correctly. 👍 Best regards, Gábor

Published a day ago

Undocked always starts full screen

Carl, I don't run anything full screen. I have the macbook connected to a Dell U5226kw display, which is 6k and about 4ft wide. This machine is only a few weeks old, macbook m5 pro, 16", macOS Tahoe 26.4, which I think is current. I have to resize the window every time I connect to that host after RDM has been closed. I does maintain size if I log off of the remote host and log back on, provided I have not closed RDM. I applied the latest update it offered a few minutes ago, 2026.1.10.3. I have tried toggling the Open undocked sessions in the last created undocked window on and off, it makes no difference. Thanks!

Published a day ago

Undocked always starts full screen

Hello, Thanks for the detailed report this is very helpful. What you're describing does not sound like intended behavior. The option "Open undocked sessions in the last created undocked window" should preserve the previous window state, including size and position, even after restarting RDM. A couple of quick checks that might help narrow it down: Are you using macOS native fullscreen at any point, or just resizing manually? Does the behavior persist if you resize the undocked window to a smaller size without ever entering fullscreen mode? If you toggle the setting off and back on, does the behavior change? If possible, could you confirm your exact macOS version? That would help us reproduce it more precisely. Best regards,

Published a day ago

SSH connection via HAProxy (TCP + TLS, custom OpenSSL command) broken since 2025.3.x

Hello, Thank you for being so patient! I'm pleased to inform you that a new version of RDM (2026.1.10.3) has been released, featuring the fix for your issue. Latest Version: Download RDM Please let us know if this works or if you encounter any issues. Best regards,

devolutions-automation

Published a day ago

Version 2026.1.10.3 (March 30, 2026)

FIXES Minor update

Richard Markiewicz

Published a day ago

Embedded RDP sessions are not working on MacOS

Hello again Adding a screenshot for clarity [image] Kind regards,

Richard Markiewicz

Published a day ago

Embedded RDP sessions are not working on MacOS

Hello That's strange. You might check in System Settings > Privacy and Security > Local Network. Both Remote Desktop Manager and (if you have "Sandboxing" enabled in the RDP session advanced options FreeRDPSandboxed should have local network access. If they are both enabled, try closing RDM completely and toggling those settings "Off" and then "On" again. Something else to check: is RDM able to "Ping" the server? Right-click the entry, and choose Macros / Scripts / Tools > Ping. Let me know if that helps Thanks and kind regards,

Published 3 days ago

Configured Shortcuts Do Not Work Inside RDP Session

Is it a feature or a limitation that I cannot use configured shortcuts inside an RDP session? I have configured a hotkey for the action “Type Clipboard” and a few others. They don’t seem to work when I’m inside an RDP session; they only work when the main RDCM window is selected as active. I’m using the latest available RDCM version on macOS Tahoe 26.4. Thanks.

Published 3 days ago

Embedded RDP sessions are not working on MacOS

Hi Richard, I am using the IP address to connect. The Windows app works, RDM does not, with the same IP address. This started about 2 weeks ago, the RDM settings had not changed at that time.

Richard Markiewicz

Published 4 days ago

Embedded RDP sessions are not working on MacOS

Hi angelo1 Actually you have a separate issue. Your log shows us connecting to an internal IP address; did you provide the IP address on the connection or a hostname? The connection to the IP and port (typically 3389 unless you changed it) was refused or unreachable; i.e. a network failure before any RDP protocol involvement. Can you double-check the address? Can you connect with the Microsoft client (Windows App)? Thanks and kind regards,

Published 4 days ago

Embedded RDP sessions are not working on MacOS

I run into this same issue since about a week. At first I thought it was due to a Windows update on the target machine, but nothing checked out. If it helps solving, here's my most recent session log. after updating to latest RDM (2026.1.9.5) [18:39:08:083] [21671:6e8a7001] [DEBUG][com.winpr.timezone] - [winpr_get_timezone_from_link]: tzid: Europe/Rome [18:39:08:083] [21671:6e8a7001] [DEBUG][com.winpr.timezone] - [winpr_get_timezone_from_link]: tzid: Europe/Rome [18:39:08:084] [21671:6e8a7001] [DEBUG][com.winpr.timezone] - [winpr_get_timezone_from_link]: tzid: Europe/Rome [18:39:08:084] [21671:6e8a7001] [DEBUG][com.winpr.timezone] - [winpr_get_timezone_from_link]: tzid: Europe/Rome [18:39:08:087] [21671:6e8a7001] [DEBUG][Remote Desktop Manager] - [Connect]: HomePath /Users/angelo/Documents ConfigPath /Users/angelo/Documents/.freerdp [18:39:08:091] [21671:6e8a7001] [INFO][Devolutions.Rdp.Credentials] - [Parse]: parsing "a*****", "" (None) => "Username: "a*****" Domain: """ [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.core] - [freerdp_connect_begin]: resetting error state [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx rdpdr [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx rdpsnd [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx RDMJump [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx RDMCmd [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx RDMLog [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.channels.cliprdr.client] - [cliprdr_VirtualChannelEntryEx]: VirtualChannelEntryEx [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx cliprdr [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.channels.drdynvc.client] - [drdynvc_VirtualChannelEntryEx]: VirtualChannelEntryEx [18:39:08:094] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx drdynvc [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.settings] - [log_monitor_configuration]: [BEGIN] MonitorDefArray[1] [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.settings] - [log_monitor]: [0] [primary] {0x0-1792x1042} [0] {1000x1000, orientation: 0, desktopScale: 100, deviceScale: 100} [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.settings] - [log_monitor_configuration]: [END] MonitorDefArray[1] [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx rdpdr [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx rdpsnd [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx RDMJump [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx RDMCmd [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx RDMLog [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.channels.cliprdr.client] - [cliprdr_VirtualChannelEntryEx]: VirtualChannelEntryEx [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx cliprdr [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.channels.drdynvc.client] - [drdynvc_VirtualChannelEntryEx]: VirtualChannelEntryEx [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.client.common.cmdline] - [freerdp_client_load_static_channel_addin]: loading channelEx drdynvc [18:39:08:095] [21671:6e8a7001] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [18:39:08:095] [21671:6e8a7001] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [18:39:08:095] [21671:6e8a7001] [ERROR][com.freerdp.channels.virtual.channel] - [virtchan_virtual_channel_init_event_ex]: Unhandled event type 0 [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.primitives] - [primitives_autodetect_best]: primitives benchmark: only one backend, skipping... [18:39:08:095] [21671:6e8a7001] [DEBUG][com.freerdp.primitives] - [primitives_autodetect_best]: primitives autodetect, using optimized [18:39:08:095] [21671:6e8a7001] [WARN][com.freerdp.codec.nsc.neon] - [nsc_init_neon_int]: TODO: Implement neon optimized version of this function [18:39:08:096] [21671:6e8a7001] [DEBUG][com.freerdp.codec] - [openh264_library_path_from_environment]: no environment variable 'FREERDP_OPENH264_LIBRARY_PATH' [18:39:08:096] [21671:6e8a7001] [DEBUG][com.freerdp.codec] - [openh264_init]: No FREERDP_OPENH264_LIBRARY_PATH set, using default search [18:39:08:096] [21671:6e8a7001] [ERROR][com.winpr.library] - [LoadLibraryA]: failed with dlopen(libopenh264.dylib, 0x0005): tried: 'libopenh264.dylib' (relative path not allowed in hardened program), '/System/Volumes/Preboot/Cryptexes/OSlibopenh264.dylib' (no such file), '/Applications/Remote Desktop Manager.app/Contents/Frameworks/FreeRDPSandboxed.app/Contents/MonoBundle/libopenh264.dylib' (no such file), '/usr/lib/libopenh264.dylib' (no such file, not in dyld cache), 'libopenh264.dylib' (relative path not allowed in hardened program) [18:39:08:096] [21671:6e8a7001] [WARN][com.freerdp.core.codecs] - [freerdp_client_codecs_prepare]: Failed to create h264 codec context [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn][0xa6b30ce00]: ************************************************* [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn][0xa6b30ce00]: This build is using [runtime-check] build options: [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn][0xa6b30ce00]: * 'WITH_VERBOSE_WINPR_ASSERT=ON' [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn][0xa6b30ce00]: * [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn][0xa6b30ce00]: [runtime-check] build options might slow down the application [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn][0xa6b30ce00]: ************************************************* [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0xa6b30ce00]: ************************************************* [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0xa6b30ce00]: [SSL] {Cipher} build or configuration missing: [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0xa6b30ce00]: * des-ede3-cbc: RDP security FIPS mode will not work [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.rdp] - [log_build_warn_cipher][0xa6b30ce00]: ************************************************* [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_set_negotiation_enabled]: Enabling security layer negotiation: TRUE [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_set_restricted_admin_mode_required]: Enabling restricted admin mode: FALSE [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_set_RCG_required]: Enabling remoteCredentialGuards: FALSE [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_enable_rdp]: Enabling RDP security: TRUE [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_enable_tls]: Enabling TLS security: TRUE [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_enable_nla]: Enabling NLA security: TRUE [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_enable_ext]: Enabling NLA extended security: FALSE [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.nego] - [nego_enable_rdstls]: Enabling RDSTLS security: FALSE [18:39:08:098] [21671:6e8a7001] [WARN][com.freerdp.core.nego] - [nego_enable_aad]: This build does not support AAD security, disabling. [18:39:08:098] [21671:6e8a7001] [DEBUG][com.freerdp.core.rdp] - [rdp_client_transition_to_state][0xa6b30ce00]: CONNECTION_STATE_INITIAL --> CONNECTION_STATE_NEGO [18:39:08:099] [21671:6e8a7001] [DEBUG][com.freerdp.core] - [freerdp_tcp_is_hostname_resolvable]: resetting error state [18:39:08:099] [21671:6e8a7001] [DEBUG][com.freerdp.core] - [freerdp_tcp_default_connect]: resetting error state [18:39:08:099] [21671:6e8a7001] [DEBUG][com.freerdp.core] - [freerdp_tcp_default_connect]: connecting to peer 192.168.1.3 [18:39:08:099] [21671:6e8a7001] [ERROR][com.freerdp.core] - [freerdp_tcp_default_connect]: ERRCONNECT_CONNECT_FAILED [0x00020006] [18:39:08:099] [21671:6e8a7001] [ERROR][com.freerdp.core] - [freerdp_tcp_default_connect]: failed to connect to 192.168.1.3 [18:39:08:099] [21671:6e8a7001] [ERROR][com.freerdp.core.nego] - [nego_connect]: Failed to connect [18:39:08:100] [21671:6e8a7001] [DEBUG][com.freerdp.core.rdp] - [rdp_finalize_reset_flags][0xa6b30ce00]: [CONNECTION_STATE_NEGO] reset finalize_sc_pdus [18:39:08:100] [21671:6e8a7001] [DEBUG][com.freerdp.core.rdp] - [rdp_client_transition_to_state][0xa6b30ce00]: CONNECTION_STATE_NEGO --> CONNECTION_STATE_INITIAL

Published 4 days ago

Find Quickly Window No Longer Working Reliably

Hello Caleb, Thank you for your feedback. I get a similar behaviour, except that the popup occurs on the lower right corner of my MacBook screen. The next RDM Mac version should contain a fix for this behaviour Best regards,

Published 5 days ago

SFTP cd to dir on remote server

[image] I'am running the lateset RDM for Mac (2026.1.9.5) and startying from previous relese (2026.1.8.7) stop working change directory on SFTP session Now RDM shown only user home dir and not allow change it (event for root user) Direct sftp to remote server works fine Now in UI in the path if i can type any existing directory on remote server after Enter nothing happen And in local side SFTP broser now showing / instead home dir

Maran Michele - FactorySolver srl

Published 5 days ago

PROXMOX Console: keyboard language issue

Hello Jonathan mac keyboard layout is italian. For example the @ digit become number 2 like a numeric pad. Thanks

Jonathan Lafontaine

Published 5 days ago

PROXMOX Console: keyboard language issue

Hi, Thank you for the feedback on the interaction between our VNC console and keyboards on macOS. I assume that when the mapping doesn't align, the keyboard is set to something other than US? I don't have any ideas at the moment. I'll need to do some testing. That being said, VNC as a protocol is extensible, and we don't use their VNC client, so it's possible that we are missing some edge cases specific to their implementation. I'll report back once I've investigated further. Regards

External resources

Devolutions Documentation

Technical SupportEmail : service@devolutions.netPhone : + 1 844 463.0419