RDM window goees to background when a RDP error occurs
Hi,
This is 2026.3.12, but the issue started I think a couple releases ago, but now has become very annoying to me.
When an RDP session is canceled due to:
lack of credentials
lack of permissions for my account to connect to the target server
maybe other reasons I didn't encounter,
the RDP window goes to back. It shouldn't be doing that.
Look at the attached screencast. It is RDM in front of a Notepad, to show the issue.
I'm trying to connect to a server, then cancel the credentials prompt, and on that moment RDM disappears.
A second later it blinks briefly, but I then need to do ALT+TAB or find the window using other means.
With the second screencast you can see I added a credential, but I have no permissions to log in to this server. When displaying that notification - the main RDM screen also disappears into background, for no reason...
Please fix it. Thanks in advance.
Recommended Answer
Hi,
Have just updated to 2026.3.15.0, and an hour in it does seem to have cured the problem. Please pass on my thanks for sorting this out :o)
RDM version: 2026.3.15.0 64-bit - local 'standalone' install
Dot Net Runtime: .NET 10.0.12
Client OS: Microsoft Windows 10.0.26200 (W11 25H2)
Client environment: On-prem VSphere v8.0.3.0 VM
RDP version: Set to 'Latest'
All Comments (9)
Hello,
The good news here is we already have a fix for this and it will be available with 2026.3.13.0. The build is currently in internal QA testing, so we're hoping to release it before the end of the week if all goes well. If the issue isn't resolved for you after this release, please let us know so we can ensure we address it in high priority.
Regards,
Hubert Mireault
2026.3.13 here. Same issue as before. After logging out of a RDP-Session, the last active App gets in focus again (for example chrome).
If Chrome was directly in the background of RDM, it covers RDM completely.
Very annoying and frustrating that this issue is still not fixed.
Using RDP-Engine "Aktuell" (I think "Current" in English).
This issue does not occur when using FreeRDP as the engine but has other issues as well.
Remote Desktop Manager 2026.3.13.0 64-bit (PreJIT)
Laufzeit: .NET 10.0.12
Plattform: Microsoft Windows 10.0.26200
Workspace: Azure SQL
2026.3.13 here. Same issue as before. After logging out of a RDP-Session, the last active App gets in focus again (for example chrome).
If Chrome was directly in the background of RDM, it covers RDM completely.
Very annoying and frustrating that this issue is still not fixed.
Using RDP-Engine "Aktuell" (I think "Current" in English).
This issue does not occur when using FreeRDP as the engine but has other issues as well.
Remote Desktop Manager 2026.3.13.0 64-bit (PreJIT)
Laufzeit: .NET 10.0.12
Plattform: Microsoft Windows 10.0.26200
Workspace: Azure SQL
cc @xelso
@Hubert Mireault : I also just updated and not fixed for me either. My rdp version is set to "Latest".
Hi, having the same problem here. Closing a remote desktop session causes the RDM window to drop behind other windows. Also running 2026.3.13.0 (upgraded this morning). Noticeably, if you try to immediately switch back to RDM, by selecting it on the taskbar for example, it loses focus again; so you sometimes have to click it 2-3 times to actually get it back in focus.
RDM version: 2026.3.13.0 64-bit - local 'standalone' install
Dot Net Runtime: .NET 10.0.12
Client OS: Microsoft Windows 10.0.26200 (W11 25H2)
Client environment: On-prem VSphere v8.0.3.0 VM
RDP version: Set to 'Latest'
I just upgraded to RDM 2026.3.13.0 64-bit (PreJIT) and for me it also DID NOT fix the issue reliably. Initially it seemed like RDM stays on top, but then after few trials and switching between apps it again started to hide behind other windows. All 3 scenarios are reliably reproducing the issue:
connection to an RDP without credentials and cancelling the credentials prompt
connection to an RDP using a user that has no permissions to connect
signing out of an RDP session by using "Sign out" inside the connected session.
Hope it can get fixed soon, fingers crossed.
Hello,
We have reopened the ticket for investigation and will keep you updated on any progress.
Best Regards,
Michaël Beaudin
Hello,
After discussion with the dev that fixed the issue, it seems there was an error on our part when reporting this as fixed as it didn't make it in the 2026.3.13.0 but will rather be in the upcoming 2026.3.14.0.
We apologize for the inconvenience. If the issue persists even in that version, please do let us know and we will reopen the ticket.
Best Regards,
Michaël Beaudin
Thank you for additional details. Fingers crossed for the fix!
Hi,
Have just updated to 2026.3.15.0, and an hour in it does seem to have cured the problem. Please pass on my thanks for sorting this out :o)
RDM version: 2026.3.15.0 64-bit - local 'standalone' install
Dot Net Runtime: .NET 10.0.12
Client OS: Microsoft Windows 10.0.26200 (W11 25H2)
Client environment: On-prem VSphere v8.0.3.0 VM
RDP version: Set to 'Latest'