Remotedesktop RDP slow/laggy, but only from one specific client to one specific host and only with one specific userprofile

Question

Hi,

im getting really mad at the moment as i got a very weird problem:

When i connect from my home laptop to my work PC via RDP into my personal profile (server saved user profile) its super laggy and unresponsive.

If I RDP to the same PC with the domain admin profile (no server saved profile) its super smooth.

Also if I first rdp onto our Terminalserver with domain admin account and then rdp from there to my work PC in the same network with personal profile, its also super smooth.

So its just this specific case, form my laptop directly to work PC with personal profile which is laggy but i dont know what to search for anymore.
Cant be the laptop, as its fast to other hosts, cant be the work PC as its fast when connecting from other machine then my laptop, cant be the user profile as its fast when using this when connecting from other machine.....

Just in this very specific constallation it gets laggy.

Anybody any idea?

Thx in advance!!!!

*** Moved from Windows / Windows 11 / Accounts, profiles, and login ***

Answer 1

Hello,

When using RDP (Remote Desktop Protocol) in Windows, if one account experiences slow connection and system performance while another account works normally, the possible causes might include:

1.The user profile for the slow account might be corrupted or have incorrect settings, leading to slow resource loading. Try creating a new user profile for the affected account to see if it resolves the issue.

2.The account might have restricted access to certain system resources or be allocated too many resources, causing performance degradation. Check the resource usage of the computer backend when logging in to the problematic account (such as whether there is high CPU, high memory, high disk usage, etc.).

3.Perhaps your problematic account contains too many self starting software, which consumes a large amount of system resources during login and slows down RDP connections. Check if there are a large number of self starting projects in the problematic account. You can confirm the current software status of the user by checking the process name under the problematic account in the user tab of the task manager.

I hope this information helps.

Best regards,

Jingjing Wu

Answer 2

First thanks for your answer.

I understand what you have written but how does it come, that this only happens if i login on this PC with this user account via RDP directly from laptop?

It doesnt happen if i login with same account via RDP from terminal server to which i connected before from laptop via RDP.

Same profile, so i think it isnt corrupted, same privilges, so i think no permissios issue.

Same self starting software. Well that point is in some kind regardless anyway, because the machine is allready running under this account and so it doesnt start anything if i just newly connect via RDP.

So its only slow in this exact combination of source machine, destination machine and user profile.

If just one thing changes, everything is performant.

same source, same destination, different profile: performant
different source, same destination, same profile: performant

same source, different destination in same network: performant (yes with different profile)

Answer 3

So at the weekend I tried if it works better with a new clean profile.

I backed up my existing profile, renamed server saved profile directory and cleaned local copy from my workstation.

Then logged on and a new empty profile was created. And WOW, it worked again smoothly when i first logged in from my laptop to my workstation.

Did some settings, App logins and so on. Then DISCONNECTED (not logged out!) the RDP session.

Next Day i wanted to connect again and... again it was laggy. After a few tries I found out, that its only laggy when I try to RDP login and resume into an already existing session on my workstation. That gets laggy.

If I really "Log out" the user when I’m done, which then also ends the RDP session, that doesn’t occur. If I then start a new RDP session a new user session on the workstation is created instead of joining an old session and everything is working smooth.

So far its more or less "OK" because I now know a way how to handle it in "a way" but this way is not really satisfying. Especially because it worked until a week ago.

And sometimes RDP sessions crash, normally that’s no problem you just reconnect and resume the session. Now i would have to connect with the domain admin account, end my user session via task manager and do a "fresh" login with my user profile. Even worse if I got anything non saved, then I first have to connect with admin to terminalserver and from there with useraccount to workstation, save everything, log out user and log in again with new session.

That leads to another weird point, that resuming an existing user session from terminal server is no problem, just from my laptop. Why?!

Answer 4

new insights:
its regardless if I try to resume a session with my personal profile or with domain admin login (without server saved profile).

everytime i try to resume a allready existing session on the wirkstation its unuseable.

everytime i login and user isnt loged in already, so a new session is created, everything works smooth.

just resuming session dont work

Answer 5

came with win update.

"network detection on the server" has to be disabled

heres the solution:
https://www.windowslatest.com/2025/02/21/windows-11-24h2-rdp-hangs-on-login-rdp-session-connecting-issues-reported/