server 2025 rdp loading the virtual machine

Question

i am facing server 2025 rdp loading the virtual machine this issuse from yeasterday

Answer 1

Hello Mani,

When you say “Server 2025 RDP loading the virtual machine,” I need to clarify whether the issue is that Remote Desktop Protocol (RDP) sessions are hanging at the “loading virtual machine” stage, or if the VM itself is stuck during startup when accessed via RDP. In most cases with Windows Server 2025 preview builds, this behavior is tied to either Hyper-V integration services not responding properly, or RDP session broker misconfiguration.

First, confirm whether the VM can be accessed directly through Hyper-V Manager or via console connection. If the VM boots fine there, the issue is isolated to RDP. In that case, check the RDP listener configuration under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp and ensure the port is still set to 3389. Also verify that the firewall rule Remote Desktop - User Mode (TCP-In) is enabled.

If the VM itself is hanging during startup, check the Hyper-V event logs under Applications and Services Logs > Microsoft > Windows > Hyper-V-Worker for errors. A common cause is integration services mismatch after updates. Running sfc /scannow inside the VM or updating the VM configuration version via Set-VM -Name <VMName> -AutomaticCriticalErrorAction Pause can help isolate the fault.

Since Server 2025 is still in Insider Preview, there are known issues with RDP sessions freezing after cumulative updates. Microsoft has documented that disabling UDP transport for RDP can stabilize connections. You can enforce this via Group Policy: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client > Turn Off UDP On Client. Apply the same on the host if necessary.

If none of these steps resolve it, I’d recommend checking whether the VM is patched with the latest Insider build, as several fixes for RDP session hangs were rolled out recently. Without the latest cumulative update, the issue may persist regardless of configuration.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

HP.