Master password is being mangled on save

Hi bboatright,

Thanks for the clear report and the screenshot, and especially for the note that the correct password comes back after you restart Remote Desktop Manager. That detail is the key one: it tells us the password is being saved correctly to your data source. What you see right after saving looks like the entry editor showing a stale value on screen, not the stored password actually changing. So your credentials should be safe.

To understand the behavior better and, if needed, report it accurately to our development team, could you help with three quick things?

1. Right after you save (before restarting RDM), please launch one of the RDP sessions that inherits this credential. Does it connect normally with the correct password? This tells us for certain whether the issue is only the on-screen display or something more.
2. Your exact RDM Windows version (Help > About).
3. The data source this folder lives in: Devolutions Server (DVLS), SQL Server, or Devolutions Hub / Cloud.

With those answers we'll have a much better understanding of what's happening here.

Best regards,

To understand the behavior better and, if needed, report it accurately to our development team, could you help with three quick things?

******Right after you save (before restarting RDM), please launch one of the RDP sessions that inherits this credential. Does it connect normally with the correct password? This tells us for certain whether the issue is only the on-screen display or something more.
No, the RDP session fails with an 'incorrect credentials' type of message

*******Your exact RDM Windows version (Help > About).
2026.2.7.0 64-bit (JIT)

********The data source this folder lives in: Devolutions Server (DVLS), SQL Server, or Devolutions Hub / Cloud.
SQLite, local data source

My workstation is Win11 25H2.

Also notable, I can no longer run sessions configured to run ISE, CMD, etc. with the inherited credentials. This is after I've performed the workaround (enter new password, save, exit RDM, restart RDM) and also after RDP sessions successfully connect.

@Eduard Sepúlveda López

Hi bboatright,

Thanks for testing this and for the details. Since the RDP session actually fails to connect, this is a real issue with this version of RDM, not just something on screen.

Could you try this?

1. Back up your data first. Since it's a local file, just make a copy of it (or use File > Backup in RDM).
2. Update RDM to 2026.2.8.
3. Open the affected credential, re-enter the password if it looks wrong or empty, and save.
4. Test an RDP session and one of your ISE/CMD sessions, and let us know if they work.

If the issue is still there after updating, just let us know and we'll open a ticket for our development team to investigate further.
One last thing for context: did this start right after you updated to 2026.2.7.0, and do you remember which version you had before?

Best regards,

I've updated to 2026.2.8 and I noticed my favorites sorting is back to my preference.

The password-mangling is still happening. Workaround of saving password, exiting/restarting app still works.

Still getting "unable to execute application" message when attempting to run my ISE/CMD sessions.

Hi bboatright,

Thanks for testing and confirming. Since 2026.2.8 didn't resolve it, we're going to open a ticket for our development team to investigate further, and we'll keep you posted on their findings.
To help them, one quick question: do you recall which RDM version you were on before this started, and whether it began right after an update? If you remember, great; if not, no problem.

Thanks for your patience.

Best regards,

I'm not sure what the last working version number was, but I use PatchMyPC so I stay updated daily.

I updated to 2026.2.11.0 64-bit (JIT) and I've discovered it's not just the password not saving unless I promptly exit RDM and restart: I'm getting new, more-informative errors:

I don't believe I ever needed to fill out the working directory in the CMS and ISE sessions previously. But, just for the grins, I used the working directory (after a save-and-restart) to the 64-bit powershell.exe:

Hi bboatright,

Thanks for digging into this and grabbing that error message. That extra detail actually helps a lot. It indicates the problem occurs when RDM tries to launch your command sessions using the inherited credentials, and it aligns with a change we've seen in the 2026.2 releases that affects exactly that part. So this isn't something you're doing wrong on your end.

And your instinct was right, you shouldn't have to fill in a working directory for those sessions, so go ahead and clear that field again.

I'm passing this along to our team to dig into it properly, and I'll keep you in the loop as I hear back. Thanks for bearing with me through all the testing, it's been genuinely useful.

Best regards,