Support

Hello, I am using Remote Desktop Manager 2024.3.16.0 (64-bit) on Windows with a local SQLite data source. When I use the older version, all my connections, usernames, and passwords are available and work correctly. After upgrading to a newer version, the connections are displayed, but the usernames and passwords are missing or empty. If I return to version 2024.3.16.0, everything comes back immediately. The local data source contains a file named Connections. The RDM configuration folder also contains the following files: RemoteDesktopManager.cfg RemoteDesktopManager.stv RemoteDesktopManager.stb RemoteDesktopManager.enc RemoteDesktopManager.enb RemoteDesktopManager.bak I tried exporting the settings and importing them into the newer version. The connections were imported, but the credentials were not. I also tried Export vault (.rdm), but initially the passwords were not included. During the tests, some entries were duplicated, so I stopped making changes and restored the older version. I would like to know: 1. Which exact files and encryption keys are required to migrate the credentials from the old version to the new version? 2. Is the local SQLite database encrypted with a master key or with a key tied to the Windows user profile? 3. Should I use File > Export > Export vault (.rdm) with Include credentials enabled? 4. Is it possible to migrate this local SQLite workspace to Devolutions Cloud while preserving the usernames and passwords? 5. What is the safest way to remove the duplicated entries without affecting the original database? Please let me know which diagnostic information is safe to provide. I do not want to upload the SQLite database or any file containing credentials publicly. Thank you.

Yes I am bringing this up again. this needs to be matured. this weekend we had to get into a device to troubleshoot. We needed to do a second connection but didn't need to log but you can only do the first two options as cancel drops the connection. I have asked to have cancel to just NOT log the session. This question is about logging. Logging cannot only apply to one session to the same file. [image] [image]

Hi, We are trying to use PuTTY colorization settings with an SSH session in Remote Desktop Manager. When we launch PuTTY directly, the colors work correctly. In PuTTY we configured: Window > Colours > Colorization > Enable Colorization and the terminal output is displayed with the expected colors. In RDM, we configured the same PuTTY installation under: Settings > Application > Paths > Configure installation path > PuTTY RDM detects the application correctly and shows Application is ready . However, when we launch and authenticate to our SSH session from RDM, the PuTTY colorization settings are not applied. I found this previous topic: https://forum.devolutions.net/topics/42416/colors-are-not-transferred-from-putty-to-ssh The feature/request there is marked as Implemented , so I assume there is now a way to transfer or use the PuTTY color settings in an RDM SSH session. Could you please explain exactly how this should be configured? Our goal is simply to have the SSH session launched from RDM display the same colors that we see when launching PuTTY directly. Thanks! Fernando Bueno

I have just updated to 2026.2.16 and have found that none of my Shrewsoft VPN now connect and Shrewsoft now longer appears in the list of VPN providers. Is there anyway to get this functionality back? Regards, Gary

Identity in favorites updates don't propagate and cannot edit identities after restart but before open previous version 2026.2.17.0 64-bit (JIT) Since updating to 2026.2.16 and 17 I am having several issues I have an id that changes password daily so I placed it in my favorites. However now when I edit it and save it still shows the old password in favorites but when I switch back to the vault it shows the new password and then when I save there it finally propagates to favorites. It is as if the favorites view is holding on to a cached copy. If I restart RDM I used to be able to open the navigation panel and edit my admin id to change the password and then answer yes to the open previous sessions. Now the panel just beeps when I click it and will not open forcing me to cancel the open previous sessions

Hello, I am trying to use a FIDO2-backed OpenSSH key together with an OpenSSH user certificate in Remote Desktop Manager for Windows. Environment: Remote Desktop Manager: 2026.2.17.0 OpenSSH for Windows: 9.5p2 Key type: sk-ssh-ed25519@openssh.com Certificate type: sk-ssh-ed25519-cert-v01@openssh.com Certificate issuer: OpenBao SSH CA Hardware authenticator: YubiKey-compatible FIDO2 security key The FIDO2 key itself works in RDM when I select its OpenSSH private key handle file, as described in your existing FIDO2 support topic. The same key and certificate also work correctly with OpenSSH for Windows: ssh -i <key-handle-file> -o CertificateFile=<certificate-file> user@host OpenSSH requests the FIDO2 PIN and/or touch and successfully connects. However, when I configure the same private key handle and certificate in an RDM SSH Shell entry, RDM rejects the certificate with this error: Unknown type for certificate key: sk-ssh-ed25519-cert-v01@openssh.com The certificate itself is valid and can be inspected → The certificate is also parsed successfully: ssh-keygen -Lf <certificate-file> Expected behavior: RDM should load the sk-ssh-ed25519-cert-v01@openssh.com certificate, use the matching sk-ssh-ed25519@openssh.com key handle, and request the FIDO2 authenticator to sign each SSH connection. Actual behavior: RDM recognizes the base FIDO2 key but rejects its OpenSSH certificate type before authentication. Could you please confirm whether OpenSSH certificates for FIDO2/SK keys are currently supported? If they are not supported yet, could support for the following certificate types be added? sk-ssh-ed25519-cert-v01@openssh.com sk-ecdsa-sha2-nistp256-cert-v01@openssh.com This combination is important because the SSH CA provides short-lived authorization, while the FIDO2 authenticator enforces physical user presence or verification on every connection.

For all SSH sessions, I used one universal setting and it worked. Waiting for `password` works even for distros that have no text at all. But with Ubuntu 26, this stopped working because the text changed. This also works for RHEL. But however you look at it, waiting for a specific word is a very hacky method. Can't you make a smart password input based on console readiness / line change? [image] ubuntu24, keyword `password` sudo -i [sudo] password for name: ubuntu26, keyword `password` sudo -i name@name:~$ sudo -i [sudo: authenticate] Password: ubuntu26, keyword `sudo` sudo -i [sudo: authenticate] Password: debian 11+, no keyword: sudo -i [sudo] password for awx: Sorry, try again. xen: sudo -i # ^C

Hello. Our users are complaining about a "Your RDM is outdated" message on the "getting started" dashboard. We upgraded to 2026.2.11.0 before we went on summer vacation and newest version now is 2026.2.17.0. That's not a huge difference? Has something changed in the release model, how long can we expect a version to be considered supported? Also is there a registry key to disable the page, I cannot find one here: Apply policies (GPOs) | Devolutions RDM | Product guides & reference [image]

Is it possible to add websites that are protected by Azure http proxy? I've added the office365 credentials which autofills correctly. The site has its own built-in username and password which doesn't autofill. Is there a way to set both login screens to autofill?

Hello Support, Hello Richard Markiewicz (pinging you as requested), we are facing a problem that whenever we reconnect our jumphost (in order for example to resize the window), our Main RDM loses connection to the agent and doesn't allow new connections. The current open Session/s is/are locked as well. We are running the following versions: Remote Desktop Manager (Main + Jumphost): 2026.1.24.0 Extended maintenance from June 29, 2026 Remote Desktop Agent: 2026.2.4.0 Steps to reproduce the error (Screenshots are from LAB Machines and therefore not sensible data) 1.) Connect to the jumphost or any server through the jumphost Sidenote: Here the Agent Status when after connecting [image] And Devolutions Agent is running [image] 2.) Right Mouse Button on the Jumphost Tab and click Reconnect [image] 3.) Try open any other Jump or entry that goes through that jumphost. You will get the waiting window for the Devolutions Agent and afterwards the error that Devolutions Agent is not available [image] [image] Devolutions Agent is still running on the Jumphost but connection to the main RDM is lost [image] [image] Workaround: What fixes the problem, would be to disconnect from the jumphost and reconnect with it close. But that does bring the problem, that it always opens as a tab again and moving just this window to smaller monitor becomes (wihtout changing the entry settings) impossible. And what the reconnect doesn't fix, is the next step. 4.) Now about the locked session that I mentioned. In result of the lost agent connection, when you either close or log off the session on the Jumphost, main RDM still recognizes it as connected. Even after closing the Jump Host completely a.) Close the session [image] b.) Session still showing opened [image] c.) Close or log off Jumphost [image] d.) Confirm to close all opened sessions [image] e.) Jump Host closed, but previously connected session still shows as open [image] Workaround: You could still right-click and select reconnect on the entry to connect again, but it still keeps the session locked. Only way to release the session from this connection lock is to close RDM and open it again. Hope this helps. Wanted to send a debug report, but for some reason it didn't record. If not reproducible by your side, I can create the Debug Report. Thanks in advance and BR Mauricio

Hello Support, we are facing a problem that all websites in our RDM are being opened embedded in in the Jumphost RDM when the setting is set to extern. We are running the following versions: Remote Desktop Manager (Main + Jumphost): 2026.1.24.0 Extended maintenance from June 29, 2026 Remote Desktop Agent: 2026.2.4.0 The settings are correct in my pov. You can leave the settings this way... [image] ...or this way [image] Either setting, opens the Web Adress as an tab in RDM on the Jumphost. [image] If you aren't able to reproduce the scenario in this version, please let me know of files or screenshots that might help you. Thanks in advance and BR Mauricio

[image] This whole navigational menu is always blank. How do I get connections to start apearing here? On version 2026.2.13.0 64-bit.

If you put the cursor to the right of 10.152.0 and back space twice it adds the 0 back. I would suggest stop auto filing these fields. Very annoying. [image]

When duplicating a session in Remote Desktop Manager (RDM), the logging functionality does not work correctly for the duplicated session. Even when manually changing the logging path within the duplicated session, no logs are being recorded. Is there a known fix or workaround for this issue?

I'm writing a PowerShell script to fully automate the install and configuration of RDM. I've gotten it to perform the installation and I'm now trying to automate the process of importing the cfg, setting the master key, etc. Is it possible to automate all of this? The intent is to completely automate the setup, including settings like the dark theme, UX settings like if status bars are shown, etc.

Hello, RDM has been working excellently for me. Thank you for building such a great product. After installing 2026.2.17.0 I can no longer log in with a Microsoft Account into my Windows 11 RDC. It shows the user and a password, but of course I do not have a password as it is a passwordless account. Is there a new setting I can apply to make this work with my passwordless account? Everything has been working for months now without this issue, and I just ran into it today. Thank you for any assistance you can provide, Michael

[update: if I save, and then exit RDM and restart it, the password is now the expected one.] I use inherited credentials for the RDP sessions under a master folder. For years I've updated the password when it expires without problem. Today, for some reason, the password is getting mangled after I save it. Halp! ( these passwords are no longer valid, of course ) [image]

I have Key agent with my ssh key in it and autostarts on launch. Recent version(s) have been now prompting me for key password: [image] It never used to prompt for this, just wondering what has changed and how can I get it to stop prompting but store it. Not sure if its related but in ssh Key manager it shows the ppk is insecure: [image]

In RDM I use an SSH Tunnel to a Windows 2025 Server running the native sshd service, and then run many sessions over it. It has worked perfectly fine with Password auth, I was looking to switch to Private/Public Key Auth. However, even though I have gotten it to accept the auth the SSH Tunnel session immediately closes/crashes, and in the Windows Event log you can see. "sshd: ssh_dispatch_run_fatal: Connection from 10.215.246.227 port 63558: invalid format" This entry is immediately after "sshd: Accepted publickey for"..... SSH Shell with the same key works perfectly fine, and again using Interactive/password auth for the tunnel works. Any Ideas? Windows Server 2025 fully updated, it is AD Joined (since shell and password work dont think ad matters but who knows) The username does start with a ! (i.e !firstlast ), might be unrelated, but just noting.

Hello, prior 2026.2 the connection Button was available on the Hyper-V Dashboard. (picture 2) since 2026.2 connecting to the HV Host u need now connect to HV Dashboard and then u have connection Button for the Host. [image] Is there a way to add him back . [image] wbr Alex

Hello support, after installing the new version of RVTools 4.8.1, RDM (version 2026.2.17) is unable to pre-fill the data into this excellent tool, i.e., neither the IP address nor the login name and password. The documentation, available here: https://downloads.dell.com/RVTools/Rvtools.pdf states that a new parameter, -BypassSSLCheck, has been introduced, and its absence could be the cause of this behavior. Perhaps the parameters for command-line invocation have also changed, but I’m not sure. Everything you need can be found in the above-mentioned document starting on page 117. Please fix this, or at least provide an option to ignore the untrusted certificate. Thank you very much. P.S. I can’t imagine doing my work without RDM...

Hello, I open the SSH sessions in quick succession, and they immediately start jumping back and forth. Version 2026.2.12.0 I have to close the sessions via right-click because I'm not able to type anything in command line. Thank you, Markus

Hello, I have a Vault setup and my users are not able to add things to the Vault root, only administrators. I changed the Vault Settings - Inherited permissions - Add to root from Workspace to Allowed and I also changed Administration - System permissions - Entries - Add to root from Default (Allowed) to Allowed. My user reported that at first they were able to add to the Vault root after I made those changes, however after they closed and re-opened RDM they reported they are no longer able to add items to the root. I'm running RDM 2026.2.9.0 and server 2026.2.9.0

Hello, I am using a Command-Line (External Application) entry that is configured to launch an application under a different user account. Before the application starts, I need to execute a script that performs some user-specific modifications. I configured the script in the "Before opening" event, but it appears to run in the security context of the user who launched Remote Desktop Manager, rather than the user account configured for the external application. Is it possible to execute the "Before opening" event script in the security context of the external application's configured user account?

See video here: https://knoweth0127.s3.us-east-1.amazonaws.com/Recording+2026-07-16+214241.mp4 (not sure how else to show this). Note that for the first 9s the right tab is the only one selected. Simply hovering the mouse over the left one causes the screen flicker. Obviously not desired! This is not consistent. It does seem most likely to happen when more than 1 tab in a separate window and then computer locked for a while.