chaddb

The team made a mistake, owned up to it, and have released several versions since fixing issues as they were reported. Devolutions isn't the first company to release a bad update. They certainly won't be the last. The team was very active on the forum and open about the fact there were issues. They were quickly fixing issues and shipping releases. There aren't a lot of other enterprises applications where you can engage directly with the team and the CEO on a public forum. 

@chaddb

They routinely, by the admission of everyone in this forum, make these mistakes. That's not acceptable in my opinion. The way they responded to it, was also not acceptable in my opinion. Saying that everyone makes these mistakes, so it's okay, to me, is validating the behavior. MSFT is a great case in point. They are so comically bad at updates its a running joke. That's been my point. Be better than MSFT.

@rdearman

I've been using RDM for probably 10 years. I can't think of another time when something like this happened with their updates. Sorry you're upset with them. Maybe you should stop using their software it it's so upsetting. 

The team made a mistake, owned up to it, and have released several versions since fixing issues as they were reported. Devolutions isn't the first company to release a bad update. They certainly won't be the last. The team was very active on the forum and open about the fact there were issues. They were quickly fixing issues and shipping releases. There aren't a lot of other enterprises applications where you can engage directly with the team and the CEO on a public forum. 

@Richard Markiewicz So far the issue seems fixed in 2026.3.16. I haven't noticed any issues today after updating EOD yesterday. Lot of fixes included in .16. Thanks for sticking with it.

Hello everyone,

Following up on my previous message, looking back at 2026.3, the root cause is clear to us: we were too ambitious. We changed too many things in a single release, and we missed a lot of use cases we took for granted, like how people rely on tabs and the navigation pane every day. Your feedback in this thread helped us see exactly where we got it wrong.

The team has kept working on it, and 2026.3.15.0 is now available with many performance improvements and bug fixes. I’d like to invite you to give it a try. If you’d rather not touch your current installation, the portable version lets you test it on the side without any risk.

If something still doesn’t behave the way you expect, please post the details here. Precise reports like the ones in this thread are what help us fix things the fastest.

Regards,

You made a mistake and corrected it. And going forward I'm guessing (and hoping) it won't happen again.

2026.3.13.0 seems worse than 3.12.

@chaddb Could you send me a video of the issue happening, it may be a slightly different issue than what the other user is reporting, i think we do have some repaint issues. Also the specific settings of your RDP connection would also help. You can post them here or send them to me privately as a Direct Message if you are not comfortable sharing it publically.

@Paul Dumais

Yep, I'll DM you.

2026.3.13.0 seems worse than 3.12.

Agreed. .12 is significantly better. Its not perfect but it's much better.

I'm still seeing issues in .12 where you have to leave the tab to redraw the window.

Is this the known issue where existing Remote Desktop sessions are forced to reconnect and redraw the display whenever you switch between them? This significantly impacts usability when working across multiple sessions.

I'm also seeing the same behavior with only a single session open. The client appears to perform a full reconnect when returning to the session, which shouldn't be necessary.

@mclanglois

Yes, it's known. They thought they had it fixed in 2026.3.10 but it's still happening. 2026.3.11 is supposed to ship any day. Hopefully it's fixed in .11.

Hello,

I haven't managed to reproduce on my end since the changes made in the 2026.3.10.0. We have some improvements to harden the fix in the upcoming 2026.3.11.0 later this week but I can't guarantee it will impact you as I can't reproduce the issue at all on my end anymore.

Do you have anything special on your setup or is it simply multiple RDP sessions opened at once?

Something like

1. Thumbnail view

2. Tab groups

3. Performing dock/undocks

4. Being on a Windows Server operating system

5. Something else?

Best Regards,

@Michael Beaudin

It seems to happen more with the more tabs I have open. With only one tab open I don't notice it. But once you get more than two it seems to happen pretty consistently.

No performing any docks/undocks. It's happening on my workstation.

Hello,

Thank you for being so patient!

If possible, could you update your RDM to the latest version (2026.3.10.0) and see if the problem persists? This version should resolve your issue.

Latest Version: Download RDM

If the problem persists after the update, please let us know so we can inform our development team.

Best regards,

@Maxim Robert

I spoke too soon. Still seeing this in 2026.3.10.

I spoke too soon. Still seeing this in 2026.3.10.

Anyone else seeing in 2026.3.x the Windows Security login modal always goes to the top left corner? Other apps open the Windows Security modal in the middle of the screen. RDM used to open there too before the 2026.x release.

Confirmed this is still occuring on the latest version 2026.3.9, which is very annoying. I had to move my cursor to minimise a opened windows to reveal the entire screen.

@JL9800

Try updating to 2026.3.10. A lot of the issues I was seeing are fixed in that release.

Hello,

Thank you for being so patient!

If possible, could you update your RDM to the latest version (2026.3.10.0) and see if the problem persists? This version should resolve your issue.

Latest Version: Download RDM

If the problem persists after the update, please let us know so we can inform our development team.

Best regards,

@Maxim Robert

So far this seems fixed in 2026.3.10.

Hello,

I completely understand, and we are working hard to improve the stability. We have already made a lot of fixes in 2026.3.9.0, and we are working on more, coming soon.

Regards

@David Hervieux

It seems 2026.3 was rushed. There are so many problems that should have been caught in testing.

How did this get into production? It's really bad. If you haven't updated to 2026.x don't. It's not ready to roll yet.

I'm seeing the same behavior in 2026.3.8.0 as well. The 2026.3.x release of RDM is almost unusable. I've never seen such a bad update for RDM.

The new UI is really buggy. I've noticed RDP sessions are noticeably slower in RDM vs. Windows RDP. This wasn't an issue in the old UI.