AuxMax001

Updated to .12. Significantly better at RDP screen white-outs. However, I'm still having these whiteouts on occasion. Far less than previous versions.

I upgraded to 2026.3.10 on Friday. While not as frequent, I still have the blank screens.

@AuxMax001

Actually...the more I'm using it this morning...the more pronounced the issue becomes.

I upgraded to 2026.3.10 on Friday. While not as frequent, I still have the blank screens.

Started after RDM was upgraded to 2026.3.5. I noticed almost immediately that active RDP session tabs would occasionally go blank. Most of time, it happened when I switched tabs. When I switched back to an inactive RDP tab, it would be a white screen. I basically had to use the cursor to reveal of the desktop, very much like using a coin on a scratch off lottery ticket.

Sometimes the screen will restore fully after a few swipes....other instances I need to reveal more of the screen before the desktop restores.

It's annoying but certainly something that didn't exist in 2026.2.x

RDM 2025.3.30.0 installed.

Using SQL server backend.

This issue isn't related to the current release...it's been an annoyance for a while.

I create templates where the parent folder is the physical location of the site, subfolders with equipment/connection types, and the actual connections under each relevant connection subfolder.

The default color I use for the folder and connection icon is forest green. This is the primary corporation color. However, I have two secondary companies which are separate from the primary company. I use gray and pink for each secondary company, respectively.

Both secondary companies use the same primary company templates. I just need to modify the icon color to match the established color scheme. I use batch edit at the parent folder, edit entries (general settings), and override the color on the general blade.

When I make this change, the color does change on all entries, but the folders remain forest green. I'm forced to manually update each folder to the correct color.

While I understand this batch edit is technically for "entries", I don't see a way to override folder color as a batch edit process.

I don't know if this is a bug or feature request.

Any updates on this issue with Bitwarden?

Yeah...dead in the water as well this morning. This is getting irritating.

Thanks for the reply. I found the problem. It was misconfiguration on small number of heavily used connection entries. I forgot to undo some of my trial and error settings when the initial Bitwarden problems started. Sorry for the fire drill.

I continued to troubleshoot this morning. Some further discoveries.

• I deleted all references to Bitwarden and created a brand-new entry, located in a different folder with a different name.

• Obviously, this will invalidate my saved entries, so I updated one connection with the new credential entry. It was an RDP connection. The Bitwarden error does not appear, but the RDP connection is prompting for a username and password, despite being linked to the credential entry.

• Initially, I had the API configuration as part of my "My Account Settings", using the checkbox to reference these settings. I've also tried entering the same API information into the credential entry. I'm still getting prompted for a username and password.

• As noted before, I have each connection entry setup as a Linked (Vault), referencing the Credential entry, and selecting the correct authentication from the Bitwarden Vault entries.

Thank you for the continuing assistance

I've tried to delete and recreate the Bitwarden entry. No change. The application log error was pulled from RDM. It is the only error message being returned.

I've updated to 2022.3.33. Still having issues. New error message now. Error message is PasswordManagerAccess.Common.BadCredentialsException: Client ID or secret is incorrect.

I've checked, rechecked, and even changed my API key. The irony is that I can query my Bitwarden vault to select a login, but when I attempt to make the connection to RDP server, website, etc., it fails.

This is the full error.

PasswordManagerAccess.Common.BadCredentialsException: Client ID or secret is incorrect

at PasswordManagerAccess.Bitwarden.Client.LoginCliApi(String clientId, String clientSecret, String deviceId, RestClient rest)

at PasswordManagerAccess.Bitwarden.Client.OpenVaultCliApi(String clientId, String clientSecret, String password, String deviceId, String baseUrl, IRestTransport transport)

at PasswordManagerAccess.Bitwarden.Vault.Open(ClientInfoCliApi clientInfo, String baseUrl)

at Devolutions.RemoteDesktopManager.Managers.BitwardenManager.InitializeAPIKey(String clientId, String clientSecret, String password, String customUrl, Boolean isSilent)

------------------------ extended stack ------------------------

at Devolutions.RemoteDesktopManager.Managers.LogManager.LogError(Exception e)

at Devolutions.RemoteDesktopManager.Managers.BitwardenManager.InitializeAPIKey(String clientId, String clientSecret, String password, String customUrl, Boolean isSilent)

at Devolutions.RemoteDesktopManager.Business.CredentialBitwardenResolver.Execute(Connection credConnection, Connection owner, CredentialRepositoryDestination destination)

at Devolutions.RemoteDesktopManager.Managers.CredentialTypeManager.ResolveCredentials(Connection connectionCredential, Connection owner, CredentialRepositoryDestination destination, CredentialResolveMode credentialResolveMode, Boolean resolveSensitive)

at Devolutions.RemoteDesktopManager.Business.CredentialPersonalCredentialResolver.Execute(Connection credConnection, Connection owner, CredentialRepositoryDestination destination)

at Devolutions.RemoteDesktopManager.Managers.CredentialTypeManager.GetCredentialResolved(Connection connection, String credentialConnectionID, CredentialRepositoryDestination destination, CredentialResolveMode credentialResolveMode, Connection inheritingConnection, OpenConnectionParameter openConnectionParameters, CredentialsResult credentialsResult)

at Devolutions.RemoteDesktopManager.Managers.CredentialTypeManager.PrepareCredentials(Connection connection, String credentialConnectionID, CredentialRepositoryDestination destination, String privateVaultSearchString, CredentialResolveMode credentialResolveMode, Connection inheritingConnection, OpenConnectionParameter openConnectionParameters, CredentialsResult credentialsResult)

at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.Prepare(Connection connection, Boolean applyCredentials, Boolean applyAlternate, Boolean applyVPN, Boolean copy, Boolean applyOverrideCredentials, Boolean isOverrideCredentials, CredentialResolveMode credentialResolveMode, OpenConnectionParameter openConnectionParameters, CredentialsResult credentialsResult, Boolean isClosing)

at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.OpenConnection(Connection connection, OpenConnectionParameter parameter)

at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.OpenConnections(Connection[] connectionList, OpenConnectionParameter parameter)

at Devolutions.RemoteDesktopManager.Managers.ActionManager.DoOpenConnection(Connection[] currentConnections, OpenConnectionMode openConnectionMode, IConnectionSource source, Dictionary`2 openingAttributes)

at Devolutions.RemoteDesktopManager.Managers.ActionManager.OpenConnections(Connection[] currentConnections, OpenConnectionMode openConnectionMode, IConnectionSource source, Boolean checkOpenedConnection)

at Devolutions.RemoteDesktopManager.Frames.ConnectionViews.FreConnectionTreeListView.OpenOnDoubleClick(Boolean isEmbedded)

at Devolutions.RemoteDesktopManager.Managers.ThreadManager.PushTimer_Tick(Object sender, EventArgs e)

at System.Windows.Forms.Timer.OnTick(EventArgs e)

at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

at Devolutions.RemoteDesktopManager.Program.Main(String[] args)

I will not speculate on the impact, but this issue is quite painful for me. I have a couple dozen passwords, with a few rotating ones. I have thousands of configurations, all pointing to a my BW vault. I'm stuck using Quick Connects for everything now.

Any indication if this is software release fix or something on Bitwarden's side? I've opened a ticket with Bitwarden as well.

After I posted the message, I found this KB: https://kb.devolutions.net/rdm_missing_navigation_pane.html

This worked. Thanks.

The problem initially was I lost the Quick Connection box, at the top of the screen, after upgrading from 2022.2.29.0. I performed a Windows layout reset. Bad idea. The whole interface disappeared, short of the menu at the top and status bar at the bottom. I closed and reopened the application. No change. I deleted the LYT files. No change.

I can see the entry count is accurate, but I'm unable to expose the navigation pane. I've disabled/enabled Navigation under layout. I also tried Alt-F8. Nothing. I can see my entries under the filter dialog box.

Suggestions?

I've got it working now.

Either one of 2 possibilities.

1. In all of my previous data sources, I had "$" in lieu of spaces. I setup a data source without $ in the names

2. I installed 2022.1.27.0, created the data source, and it loaded without issue. Then upgraded to the latest version.

Sorry for late response. I've sent the logs to support.

In addition, I've done some additional troubleshooting.

First, I decided to do a Windows reset and load the basics only. I reinstalled SQL Server 2019 Dev and reinstalled RDM. I created a new blank DB. The tests for host and DB data sources were successful. Unfortunately, the same problem (RDM crashing), with the same recorded error occurred.

Today, I installed and setup debugdiag on RemoteDesktopManager64.exe. I captured the log files from this. Not sure if this has any value or if I should post it here.

One item I did forget to mention. The default local data source, SQLite I think, does open. When I switch to the SQL Server data source, it crashes.

I tested with the portal version and the SQLite open, but crashes on the SQL Server data source.

Yes. I've run the .Net repair. I'm currently running 4.8.04084.

Brand new computer, Windows 10 21H2, running using a SQL Server 2019 Developer data source. SQL Server 2019 is the latest version

I've decided to start from scratch and build a new setup for RDM.

When I add a new data source for SQL server, it creates and passes the host and database checks. Unfortunately, when I switch to the new data source, RDM crashes every time.

Windows Error Reporting

Fault bucket 2011615227848693139, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: RemoteDesktopManager64.exe

P2: 2022.2.16.0

P3: cb7c43cc

P4: clr.dll

P5: 4.8.4515.0

P6: 624ce98e

P7: c00000fd

P8: 0000000000052e03

P9:

P10:

Faulting application name: RemoteDesktopManager64.exe, version: 2022.2.16.0, time stamp: 0xcb7c43cc

Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e

Exception code: 0xc00000fd

Fault offset: 0x0000000000052e03

Faulting process id: 0x1690

Faulting application start time: 0x01d897b41422a5c7

Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe

Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

Report Id: aac71775-1377-4351-a81a-112c1bf4408a

Faulting package full name:

I've run sfc repairs and DISM health checks. I've changed the authentication from integrated to database. I've reinstalled SQL. Same errors.

What am I missing?

Thanks for the replies.

Unfortunately, this odd error message was foreshadowing a larger hardware issue. I started getting BSODs, which devolved into simply freezing just attempting to boot into Windows. While a base Windows reinstall stabilized the system, the system crashes when attempting to load any drivers. RAM and storage tests didn't show problems.

Unfortunately, I've been poking and prodding. I deleted the data source and recreated it. Now, I suspect the new data source is now set as the default, so it opens and crashes now. I deleted cfg file and relauched. I added license information and then it crashed again. The same scenario as before. How do I change the default data source without RDM?

I have an odd problem.

I have 7 SQL databases to segment different companies and such. I can open 6 of 7 data sources without issues. When I open the 7th one, RDM hangs and then closes/crashes. This is recorded in the Application log on Event Viewer.

Faulting application name: RemoteDesktopManager64.exe, version: 2022.2.14.0, time stamp: 0xf9c131ad

Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e

Exception code: 0xc00000fd

Fault offset: 0x00000000001f01b9

Faulting process id: 0x44d4

Faulting application start time: 0x01d88717689f5df7

Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe

Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

Report Id: 928399b1-0e79-44ae-8847-96cdf2b240bd

Faulting package full name:

Faulting package-relative application ID:

Now, I didn't need to connect to this database until today, but I know it worked prior to the 2022.2.12.0 released this week.

All of the other databases prompted for an upgrade prior to connecting, with the exception of number 7. So...I launched RDM on one of the working data sources and performed a manual upgrade on the data source. I checked connections and database connections. All reported successful. Yet....when try to connect to DB #7, it crashes and generates the same error in the application log.

So...I assumed a database error. I restored the database from backups from both last week and last month. Performed the same manual upgrade tasks, but the application continues to crash. Next, I created a new database and restored the latest backup to the new database. Performed the same manual upgrade tasks but still continues to implode.

Ugh.

Ideas?

I have 3 separate credentials, which are saved in Bitwarden. I've activated the RDM plugin and authenticate seamlessly on my RDP connections. However, a large chunk of my RDP connections require any of the 3 saved credentials. I was looking an option to select which save credential would be utilized for the session.

For example, I have a RDP session. Most of the time, I use the basic user-level account. Occasionally, I need to login with server admin level credentials. Once in a while, I would need to use the enterprise admin credentials. I'm looking for a way to select the correct save credential, prior to making the RDP connection.

I suppose I could create one RDP connection per login, but I don't wish to triple the number of connections, which number over 2,000.

Ideas?

Up until this morning, I usually had a chrome session and a few RDP sessions. However, last night, I decided to close all open tabs. It was frozen this morning. This is screen capture of the RDM process....

Nothing was recorded in the event viewer. After I killed the processes, this error was generated in the event viewer.

The program RemoteDesktopManager64.exe version 2020.3.26.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 24470

Start Time: 01d6f00b5f9063f7

Termination Time: 4294967295

Application Path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe

Report Id: ea4e173f-ef9a-48a0-96d6-606277d99721

Faulting package full name:

Faulting package-relative application ID:

Hang type: Top level window is idle