Sudden encryption error after update.
Hi, a couple updates ago, I started receiving this message. It is intermittent and when it happens it boots me from my session. Nothing has changed with my environment. If I use traditional RDP I do not get the message. Only when I use your product... which I really like btw! I updated to the latest version hoping it would be fixed but no luck. If I can't resolve this, I'll have to go back to traditional RDP.
Devolutions RDP Manager Error.png
All Comments (6)
Hi,
Can you tell me which RDP engine is configured for your connection entry?
Also, what is the version of Windows you are connecting to?
Best regards,
Marc-André Moreau
a95a8eb0-dd86-4948-b7fd-8be22f19be34.png
Hi,
The RDP Version is "Latest".
I am connecting to an Azure VM. Windows 10 Pro. OS build 19044.2965
Thanks for any help!
Hi,
Can you try launching the RDP session in external mode with mstsc? I would be curious to see if it will disconnect in the same way, and if the error code will be the same. Please take a screenshot of the error from mstsc if it happens.
Best regards,
Marc-André Moreau
I'm having the same issue. It happens random and then usually repeatedly, and then will finally connect and work for a random amount of time before dropping the connection again with that error. I'm on Win11 23h2 connecting to a Win2019 server. Only happens with this one server, other servers i connect to work fine. RDP version is also on Latest. I can connect with MSTSC from my laptop without issue, only happens in RDM. I'm running RDM 2024.1.29.0
Hi,
This sounds like a potential network issue, which is often related to RDP UDP. Can you try disabling RDP UDP on the client machine to see if the problem goes away?
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client' -Name 'fClientDisableUDP' -Value 1
Best regards,
Marc-André Moreau
I already had a key for fClientDisabledUDP' with value of 1, i added fClientDisableUDP with a value of 1. I'll test and see if this helps
Update: i spoke with a colleague that had this same issue. He changed his vault to the Hub and fixed his issue. I did that yesterday and so far haven't had any of these data encryption disconnect errors that would happen numerous times a day usually. So maybe there's something with using a local vault like I had setup.