Credentials linked to PWSafe vaults no longer function
RDM can no longer pass through logon information for any PWSafe linked credentials. It reads the data fine -- I can view the usernames and passwords without issue, but opening an RDP session causes a native RDP logon popup to occur -- there's no passthrough. I've tried new credential entries -- which create fine, but still aren't used to authenticate for RDP sessions. I've tried new data sources, but nothing changes. This vault plugin is the only paid feature I use, so a fix would be appreciated. I'm using the current version of RDM, but this started effecting the older 2025 version, so I upgraded, hoping it was fixed. I don't know what started it, but it started this week. I would consider a complete reinstall, but I would think the upgrade would have fixed any corruption in the install.
All Comments (2)
Hello,
Thank you for reaching out to us regarding this,
Could you please specify the version of RDM you are currently using?
What type of data source are you using?
Does your RDP Entry work as expected if you use the "Username/Password" option for the credentials and enter the credentials directly in the entry Properties?
Let me know,
Best regards,
Samuel Dery
Latest build: 20126.1.15.0
Previously 2025.2.32.0
SQLite connection DB
Both exhibited the issue, I upgraded in an attempt to fix it. Also installed .Net Core 10 as part of that update.
Username/Password directly defined on the RDP session works fine, so does a Username/Password credential entry.
Only credential entries for the PWsafe plugin stopped working when linked to an RDP session. Happens for old and newly created PWsafe credential entries. When I edit a PWsafe credential entry, I'm able to choose the database and credentials after being prompted for the master password (held in memory for the session only), with no errors. However, when I try to launch an RDP session with it linked, I do not get the expected, one-time master password entry for the RDM session, and I get a "normal" RDP username password logon popup.
I see no corresponding error logs in the app logs. I only see this periodically:
[3/26/2026 11:05:55 AM - 2026.1.15.0 - 64-bit] Error silent: System.TimeoutException: The operation has timed out.
at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToken, Int32 startTime)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Devolutions.RemoteDesktopManager.Business.NowAgent.NowProtoPipeTransport.Connect(String pipeName, Nullable`1 timeout, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Business.NowAgent.NowAgent.Connect(Guid sessionId, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Frames.Embedded.FreEmbeddedRDP.<>c__DisplayClass172_0.<<ConnectNowAgent>b__0>d.MoveNext()
It feels like something got corrupted and now it refuses to work with the plugin normally. I would consider a full reinstall, but are there any additional steps to make sure there's no remnants left behind after an uninstall?