Also, after the initial connection is made, I can close the connection and reconnect using another machine entirely without experiencing the long delay. I've tested the remote desktop clients on Windows 7, 8.1, and 10, and all experience the same slow initial connection to the Windows 10 machine, so I believe the problem lies on the server side. I used an app which monitor the mouse polling rate to test and If I connect to a full desktop RDP session, it caps the mouse polling rate to about 60hz and I can use it fine. But on Remoteapps it shows between 600 and 1000hz. Handling almost a thousand requests per second on a TCP connection probably is the cause of the extreme slowness. Things I've checked: allowing services through Windows Firewall (Bonjour, WMC services, etc.) Allowing remote. Network & Sharing: slow remote desktop when using VPN to work PC Hey, I am having problems where the connection and overall feel of the computer is very slow when running windows remote desktop to connect to my work PC via VPN. Remote Desktop Connection extremely slow and choppy I visited the thread at the bottom of this post and attempted both fixes that were proposed but I am still having slowness issues. I am using Windows 10 Pro on my desktop at home and I am using it to access a work webpage that has the ability to remote into my work PC which has Windows 7.
- Microsoft Remote Desktop Laggy
- Microsoft Rewards
- Mac Microsoft Remote Desktop Slow
- Microsoft Remote Desktop Slow Download
- Macos Microsoft Remote Desktop Slow
Time out, delay, Securing Remote Connection |
Randomly it does seem to happen that the Microsoft RDP software for Windows shows a popup with the text:
Securing Remote Connection
This popup is shown 'forever' or for an annoying long time. Sometimes after a long time, there is a successful RDP connection. However, sometimes the popup is shown 'forever' and there is no successful RDP connection with the server.
The cause of this problem is not exactly known to us, but it seems to happen randomly across the world.
It is not an exclusive AADServer problem. For example, see this link on the Microsoft website:
or some generic googling on this problem:
Microsoft Remote Desktop Laggy
The problem seem to happen randomly while attempting to connect to Windows Terminal Server running on Windows 2008 or 2012. Unfortunately it does also randomly happen when attempting to connect to an AADServer.
Based on the information on the Microsoft website , there are 3 possible fixes. These fixes do need to be done on the Client PC. This problem and this FAQ is about MS-RDP on the Client PC. It is not about AADServer or Microsoft Windows Terminal Server. If you have 10 Client PC's with this problem, you will need to do the fix 10 times. You need to do the fix on each of the 10 Client PC's.
If possible we would recommended Fix 1 or Fix 2 . It is only recommended to choose Fix 3, if the Client PC that will be used to connect to the Terminal Server, if this Client PC has no working internet connection, and therefore this Client PC will never be able to automatically install Windows Updates, including not being able to automatically update Root Certificates.
Fix 1
Use the AADS Client Software on Windows. It does not have this problem that MS-RDP has.
Fix 2
Step 1
Safe the RDP file that is used for the connection:
The Save-button will result in a file called Default.rdp in your Document folder.
Step 2
Start Notepad, File Open, and be sure to select 'All Files' such that the file 'default.rdp' will be shown:
Using Notepad to edit the .rdp file and add the following:
enablecredsspsupport:i:0
Save the file 'default.rdp', and the fix is applied.
Fix 3
Make the following changes in your group policy on the Client PC.
Microsoft Rewards
Configure the setting for 'Turn off Automatic Root Certificates Update': set it to Enabled.
© 2012-2021 AADS WorldWide. Terminal Server | Application Server | Remote Desktop solutions | Firewall |
This article addresses several common issues that users can experience when they use remote desktop functionality.
Mac Microsoft Remote Desktop Slow
Intermittent problems with new Microsoft Azure virtual machines
Microsoft Remote Desktop Slow Download
This issue affects virtual machines that have been recently provisioned. After the user connects to the virtual machine, the remote desktop session does not load all the user's settings correctly.
To work around this issue, disconnect from the virtual machine, wait for at least 20 minutes, and then connect again.
To resolve this issue, apply the following updates to the virtual machines, as appropriate:
- Windows 10 and Windows Server 2016: KB 4343884, August 30, 2018—KB4343884 (OS Build 14393.2457)
- Windows Server 2012 R2: KB 4343891, August 30, 2018—KB4343891 (Preview of Monthly Rollup)
Video playback issues on Windows 10 version 1709
This issue occurs when users connect to remote computers that are running Windows 10, version 1709. When these users play video using the VMR9 (Video Mixing Renderer 9) codec, the player shows only a black window.
This is a known issue in Windows 10, version 1709. The issue doesn't occur in Windows 10, version 1703.
Desktop sharing issues on Windows 10
This issue occurs when the user has a read-only user profile (and associated registry hive), such as in a kiosk scenario. When such a user connects to a remote computer that is running Windows 10, version 1803, they can't share their desktop.
To fix this issue, apply the Windows 10 update 4340917, July 24, 2018—KB4340917 (OS Build 17134.191).
Performance issues when mixing versions of Windows 10 if NLA is disabled
This issue occurs when Remote Desktop client computers running Windows 10 connect to remote desktops that run different versions of Windows 10 while NLA is disabled. Users of Remote Desktop clients on computers running Windows 10, version 1709 or earlier experience poor performance when they connect to remote desktops running Windows 10, version 1803 or later.
This occurs because, when NLA is disabled, the older client computers use a slower protocol when they connect to Windows 10, version 1803 or a later version.
To resolve this issue, apply KB 4340917, July 24, 2018—KB4340917 (OS Build 17134.191).
Macos Microsoft Remote Desktop Slow
Black screen issue
This issue occurs in Windows 8.0, Windows 8.1, Windows 10 RTM, and Windows Server 2012 R2. A user launches multiple applications in a remote desktop, then disconnects from the session. Periodically, the user reconnects to the remote desktop to interact with the applications, and then disconnects again. At some point, when the user reconnects, the remote desktop session only shows a black screen. To get the session to display properly again, the user then has to end their session from either the remote computer's console or the RDSH server console and stop their session's applications.
To resolve this issue, apply the following updates as appropriate:
- Windows 8 and Windows Server 2012: KB4103719, May 17, 2018—KB4103719 (Preview of Monthly Rollup)
- Windows 8.1 and Windows Server 2012 R2: KB4103724, May 17, 2018—KB4103724 (Preview of Monthly Rollup) and KB 4284863, June 21, 2018—KB4284863 (Preview of Monthly Rollup)
- Windows 10: Fixed in KB4284860, June 12, 2018—KB4284860 (OS Build 10240.17889)