I recently upgraded my Homelab to Server 2025 and when I try to RDP into the 2025 VMs that have a GUI installed the RDP session freezes immediately and displays a static image of Windows trying to log me in.
If I connect to a Server 2025 Core machine it works fine.
If I run xfreerdp by hand (via terminal) I can connect to Server 2025 GUI no problem.
Recommended Answer
Looks like the March 2025 updates fixed this for me connecting to Server 2025 VMs (Core and GUI)
Hello,
Thank you for reaching out to Devolution Support.
Could you please clarify which operating system or application you are referring to? I believe the 2025 beta version of our product has not been released yet.
Best regards,
Carl Marien
Sorry, my machine is Ubuntu 24.10 running Remote Desktop Manager 2024.3.2.5.
I am connecting via RDP to a Windows Server 2025 Standard Edition (with GUI) machine.
Hello,
I was unable to replicate the issue on my end.
Could you please try recreating the entry to see if the issue occurs again? Additionally, could you check if the issue persists on a Windows machine?
These tests will help us pinpoint the root cause of the problem.
Best regards,
Carl Marien
Create a new entry, same issue on Server 2025 with a GUI.
Server 2025 running Core works consistently every time.
Correction to my previous post, I am running Kubuntu 24.10.
Could be a FreeRDP bug?
https://github.com/FreeRDP/FreeRDP/issues/10864
Hello,
It is indeed a possibility. I have requested internal access to a Windows Server 2025 Core to attempt to recreate your issue on my end. I will let you know as soon as I have news.
Best regards,
Carl Marien
I am experiencing this same issue. I am connecting from a Windows 2016 VM (AWS Workspace) to a Windows 2025 Datacenter with RDManager 2024.3.29.0 64-bit (with latest update). I noticed this with some new AWS EC2 instances I just deployed and configured yesterday but can also verify that I see the same behavior on instances I deployed last week that had been accessible in a normal way.
An interesting note is that while I'm unable to RDP with a network user, I can connect with the local admin account. Also, I have a Win2025 instance I deployed late last year for initial testing that has not received any Windows Updates over the last month and it is accessible via RDP with a network user.
I tried changing the registry settings to disable bandwidth detection for Terminal Server but that didn't work for me, however, if I uncheck "Detect bandwidth automatically" in the Experience tab of Properties, I can connect. 
Screenshot 2025-02-18 at 12.12.49 PM.png
Yeah, I found a few Reddit posts about "Continuous Network Detect" being the cause when connecting to fully patched Windows 11 and Server 2025 machines.
I used GPO to disable it across my Windows Server VMs: Computer Configuration -> Policies -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections
Under 'Select network detection on the server' set 'Select Network Detect Level' to 'Turn off Continuous Network Detect'
In the environment where I was experiencing the problem, I don't have access to GPM, so I made the changes in the registry directly on the instances, which didn't work. Unchecking that option in RDM did, though.
In the environment where I was experiencing the problem, I don't have access to GPM, so I made the changes in the registry directly on the instances, which didn't work. Unchecking that option in RDM did, though.
Thanks so much Alex , that did it... I can confirm it.
We a re few using this tool, so I don't want to change something too all Server having this option direct in to the Tool.
Connecting rom W11 26100.3194
To Server 2025 26100.3194
Br
Mela
I tried changing the registry settings to disable bandwidth detection for Terminal Server but that didn't work for me, however, if I uncheck "Detect bandwidth automatically" in the Experience tab of Properties, I can connect.
Just installed two new datacentre 2025 with GUI servers and both immediately had this issue.
Using this trick immediately fixed the issue.
Thanks for posting!
Hello,
Thank you for all your testing efforts.
I attempted to reproduce the issue but was unfortunately unable to do so. Could you provide details on any specific setup or configuration on your end that might be contributing to this issue?
When you say you encountered this issue immediately, do you mean that you didn’t set up anything beforehand?
Best regards,
Carl Marien
I think the fix for this is in the Windows 11 Preview Update for March 2025 released a week or so ago.
I suspect this will be resolved in the Windows Updates released this month (March 11, 2025).
Hello,
Thank you for the information. That might be the case. Would it be possible to let us know if the next update resolves the issue?
Best regards,
Carl Marien
Looks like the March 2025 updates fixed this for me connecting to Server 2025 VMs (Core and GUI)
Hello,
Happy to hear that the March 2025 updates have resolved the issue.
If you encounter any further issues or need additional assistance, feel free to reach out.
Best regards,
Carl Marien