Windows 10: Slow RDP (Prior to Connection) and Task Manager

Hi There,

I've burnt a hole in google's bottom line search for answers for this, but I have come up negative on all counts.

Hence I have to change from been a lurker to a poster.

Machine: 4 year old, Intel 2 core hardware (3GHz ish), 8G RAM, - All running off 250GB SSD. Normally - for desktop apps and general run of the mill stuff - this thing is blisteringly quick.
Did a fresh install of Win10_64. Thumbs up, all sweet. Went to set up RDP links for the services that this machine has to access - uh oh. Open task Manager uh-oh.

Now - to explain. Notepad - launches in less than a split second - chrome, IE, etc (the heavier apps) take < 1s for a window to appear. A little longer and the window is populated.

Task Manager (right click off explorer) maybe 10 seconds, before it will show itself.

RDP - now we are in a different league. Windows knows something is fishy, because it politely tells me that the program is unresponsive by redrawing it's taskbar. When it gets to typing an address into the RDP, it can take upto 5 seconds prior to a keystroke echoing on the screen. I have TaskMan open at this point, the system is idle. Nothing is being stressed, especially not the RDP App. Establishing a saved RDP session can be 20 seconds, establishing a new one takes minutes. Once the RDP session is open this problem is gone.

Thoughts? My best guess is there is some sort of GUI lockup somewhere. I managed to diagnose one of these for a friend last week - it turned out to be OpenGL Resource starvation across multiple apps when it looks like global locks were not being handled correctly. This only took me about 15 min to figure this out. This RDP issue I have spent considerably longer on, and since this is all native windows apps, and they work on all other setups in the same environment, I'm a bit stumped.

Oh - the machine previously had Win7_32 on it and there was no issues.

Has anyone seen this before? - any pointers?

Before anyone asks - there is nothing but default AV on there, so nothing hooking the OS in inappropriate places.

Thanks

:)

 

Slow remote desktop after windows 10 updates

I am also experiencing similar problem.

I used laptop with windows vista , RDP is good while connecting my office desktop having Windows 7.

Now I purchased new laptop with Windows 10, but RDP is very slow by connecting to my office desktop.

There must be some problem in Windows 10 RDP graphic display.

 

remote desktop via gprs

Sorry but the answer is no, you will need to establish the GPRS connection first then connect the RDP session. The previous version of RDP mobile worked with the connection manager to initiate the internet/vpn connection but not in Windows Mobile 6.

 

What is your graphics hardware? Needless to say, I had some big issues with the taskbar taking forever to load. The window would come up, but nothing would show inside, for like 10 seconds or so. One of the services wasn't showing up correctly causing task manager to hang. NVIDIA Geforce GT 630 Driver version 331.82. Updating the drivers fixed that problem. No issues now.

Now, Remote Desktop Connection is much different. I haven't played with it on Windows 10, but used it on Windows 8.1 and had no issues with it.

Have you by chance opened an elevated command prompt and do sfc /scannow
Just to check to make sure there are no system errors.

Win7 32 or 64 bit had no issues with remote desktop.

Funny, now I'm wanting to check that out now

 

Hi Imaneke,

Thanks for the suggestions.

These faults were present immediately after a fresh build. Yes - sfc /scannow came up with issues - but they revolved around directory ownership. I can't see that being an issue.

DXDiag says it is a GeForce GT 620 running 10.18.13.5891 - which I am pretty sure are the latest set of WQHL released drivers for that HW.

Yep - it stinks of graphics card conflicts - but I just can't think why.

Thanks

 

There should have been no conflicts after a fresh install. That is kind of odd.

 

System file corruptions are odd too after a fresh install. I've never seen that before.

 

Thanks for your musings. A reasonably expert user has been using this system for about 2 months, after which time I have performed the scan. I wouldn't have expected to see any faults, either, and didn't think to check at that time.

I've also noticed that Win+X, admin shell is also slow to launch. When I get back there today, I'll see if it happens to non admin, as well.

Thanks

 

Ok - I just had a look at that machine. Command Prompt (User mode) comes up quick, as you would expect.

Admin command prompt behaves as follows;
1. Instantly clears the desktop and throws up the security warning.
2. Click Ok - dialog disappears, and the desktop doesn't return. for about 3~4 seconds.
3. Desktop returns, command prompt app doesn't appear.
4. 5 seconds later (desktop is fully functional), then the Admin command prompt pops up.

For me - and I program as well; the fault's DNA suggests it has to be on the windows event loop, but a call made to the GUI subsystem, that blocks, but does not wait - so no CPU time is being registered against any particular task.

Hmmm - I might try bleeding edge display drivers.

 

Latest driver is 361.43

 

Thanks for that - I'll try that tomorrow.

 

I've got a bit warmer:

Microsoft Visual Studio 2010 Tools for Office Runtime : 10.0.50903 - removing this fixed the issue on one machine, however not the original machine with the issues.

I've managed to clone a few VMs and I have seen this issue now on two of 3 of them.

So it isn't hardware.

I'll keep poking.

 

Hold that thought. what I previously posted was incorrect. But I have discovered how to speed it up;

These machine are part of a Samba Domain - if I log in as a local account - these issues go away - if I log in on a domain account these issues plague these machines.

Does anyone know where I should poke next?

 

Well - this took a while to fix, but it reared it's ugly head in another guise where another member of the domain couldn't create a profile in outlook 2013.

The fix is as follows;

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb]
"ProtectionPolicy"=dword:00000001



Yes, just one key.