4

I remote desktop to my Window 10 Surface laptop via LAN (to use Outlook from the laptop) allowing me to create send/emails on the Surface laptop via remote desktop from my desktop PC. This has been working fine for 2+ years. Recently the Surface 10 has started ending the remote desktop session randomly perhaps 2 or 3 timeS per day. The worst parts is that it also terminates all running applications so when I can finally remote desktop back in my Outlook sessions have been lost. This is frustrating as I have lost a lot of drafted emails. (I’ve setup Outlook to save every 1 minute but still I want to fix this).

If I try to immediately log back in via RDP I sometimes get:

The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.

I wait and try again and I can log back in but all my applications have been terminated. Perhaps the user session is being logged out and back in – I can’t tell.

There are no failed attempts in System Event Log Security, only forced log off. I noticed over 100 Audit Success security events at same time:

Credential Manager credentials were read.
Subject:
    Security ID:        DOMAIN\My Name
    Account Name:       My Name
    Account Domain:     DOMAIN
    Logon ID:           0x1A293A3D8
    Read Operation:     Enumerate Credentials
This event occurs when a user performs a read operation on stored credentials in Credential Manager.

This is then followed with:

An account was logged off.
Logon Type:         3

This event is generated when a logon session is destroyed. 
It may be positively correlated with a logon event using the Logon ID value. 
Logon IDs are only unique between reboots on the same computer.

Windows System Events at arounds this time shows a number of Errors:

The server {AAC1009F-AB33-48F9-9A21-7F5B88426A2E} did not register with DCOM within the required timeout.
The system is exiting connected standby 

Reason: Input Keyboard.
A timeout was reached (30000 milliseconds) while waiting for the Sync Host_1a14de225 service to connect.
A timeout was reached (30000 milliseconds) while waiting for the Windows Push 

Notifications User Service_1a14de225 service to connect.
The Clipboard User Service_1a14de225 service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
A timeout was reached (30000 milliseconds) while waiting for the Clipboard User Service_1a14de225 service to connect.

The Connected Devices Platform User Service_1a14de225 service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
A timeout was reached (30000 milliseconds) while waiting for the Connected Devices Platform User Service_1a14de225 service to connect.

The Clipboard User Service_1a14de225 service terminated unexpectedly. 
It has done this 1 time(s). 
The following corrective action will be taken in 3000 milliseconds: 
Restart the service.

The Sync Host_1a14de225 service terminated unexpectedly. 
It has done this 1 time(s).
The following corrective action will be taken in 10000 milliseconds: 
Restart the service.

The Windows Push Notifications User Service_1a14de225 service terminated unexpectedly.
It has done this 1 time(s).
The following corrective action will be taken in 10000 milliseconds:
Restart the service.
18
  • This post suggests that RDP is disconnected upon periodic Group Policy updates. The suggested fix is to set under registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server the value of fDenyTSConnections to zero. I checked, and this entry still exists on Windows 10.
    – harrymc
    Sep 29, 2019 at 14:58
  • Thank you for suggestion, however, fDenyTSConnections is already set to zero on the system being connected to. Sep 30, 2019 at 17:04
  • Have you checked group policies under Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits? Is it possible that two persons are using the same login and one is kicking the other out?
    – harrymc
    Sep 30, 2019 at 18:29
  • Technically it's not the remote session (connection) that terminates and causes the apps to close. The user session terminates (regardless if the user used RDP or logged in directly) which means the user gets logged off which then terminates all open applications started by that user. Did you set some kind of timeout or anything (e.g. to terminate the user session if the remote connection stays disconnected for a certain amount of time)? Did the termination take place while you were logged on remotely / actively doing s.th. or was the system idle and/or not connected via a remote connection?
    – Albin
    Oct 1, 2019 at 16:29
  • 1
    @PimpJuiceIT - thanks for the suggestion - I've applied those changes and will let you know if this fixes (problem normally occurs only 1-2 per day) Nov 26, 2019 at 21:33

5 Answers 5

2

I believe this issue has been fixed in Windows 10 build 19018 (20H1), which is available to Windows Insiders. You should be able to get this if you're willing to switch to the Slow ring in your Windows Insider Settings.

I've been experiencing it as well and it seems to have gone away after upgrading.

2
  • This sounds promising but I could not find any mention of a fix for this issue in the "What's new" documentation. Is there any documentation of a related fix anywhere? Also, did you have to upgrade both PCs (i.e. the client and server or just one)? Dec 5, 2019 at 12:36
  • 1
    The page above lists "includes the fix for the issue resulting in black screens and disconnects over remote desktop in the last couple of flights" and feedback I submitted via the Feedback Hub was resolved. You only need to upgrade the host, not the guest.
    – Chris P.
    Dec 6, 2019 at 6:34
1

This link shows that it is possibly group policy updates although the solution provided does not always work.

Although this might work for you:

The best workaround I found is to increase the interval between group policy refreshes. I set it to 8 hours (480 minutes) for domain controllers and now I get at most one RDP reset a day.

Quoted from this page.

EDIT:

It could possibly be this:

Or Most probably you have switched on "Dynamic lock". This detects if you are using the computer or not and locks it if you seem to be away.

You can find this at: Settings (Windws+i) -> Accounts -> Sign-in options -> Dynamic lock

Qouted from this page.

Try doing Win+R and mstsc.exe /admin and staying logged on like this. Then see if it shows a "Logging off..." message when the error happens.

5
  • Thanks for suggestion. I changed the group policy refresh rate to a very regular 1 minute (down from the default 90 mins) to see if this would reproduce the issue so that I could be sure this was the cause. This change has not impacted the frequency of the problems so it is not clear this is related. Oct 3, 2019 at 8:34
  • Please see my new edit if this possibly solves your problem.
    – DDiamond
    Oct 3, 2019 at 9:29
  • Thanks again but Windows Dynamic Lock is not on. Oct 4, 2019 at 20:08
  • 1
    Connecting with mstsc.exe /admin to see if there is any difference Oct 4, 2019 at 20:14
  • Problem persists with connecting with mstsc.exe /admin Nov 15, 2019 at 16:05
1

I faced the same issue. The solution eluded me until I noticed the clock was off. I update the time server and still had problems until I restarted the server.

1
  • Thanks for suggestion - however on my systems all clocks are correct and in sync so still seeing the issue. Mar 26, 2020 at 11:50
0

Consider the following registry settings:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"TcpMaxDataRetransmissions"=dword:00000010

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"KeepAliveInterval"=dword:00000001
"KeepAliveEnable"=dword:00000001

Some settings are defined in the article Things that you may want to know about TCP Keepalives:

KeepAliveInterval
This parameter determines the interval between TCP keep-alive retransmissions until a response is received.

TcpMaxDataRetransmissions
This parameter controls the number of times that TCP retransmits an individual data segment (not connection request segments) before aborting the connection

7
  • Thank you for suggestion but these changes made no difference. The problem persists and causes data loss daily. Nov 15, 2019 at 16:06
  • Did you try making them on both the computer and the Surface?
    – harrymc
    Nov 15, 2019 at 16:12
  • Previously only tried on Surface but have applied changes to both PCs and will report back if this resolves it. Nov 15, 2019 at 16:24
  • I tried the settings on both PCs and unfortunately problem remains with daily random disconnection and all apps terminated. Nov 18, 2019 at 11:38
  • Strange. This should have worked. Is it possible that the problem is inbetween?
    – harrymc
    Nov 18, 2019 at 12:32
0

Two years later, I have the exact same symptoms as the OP, with the exact same errors in event viewer.

This is making my work-from-home life a bit tedious, with the session being destroyed frequently and randomly.

If a good heart had any idea that has not already been proposed to the OP (as it did not work for him, it did not for me)...

2
  • As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.
    – Community Bot
    Jan 7, 2022 at 11:33
  • This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. To get notified when this question gets new answers, you can follow this question. Once you have enough reputation, you can also add a bounty to draw more attention to this question. - From Review
    – Dave M
    Jan 7, 2022 at 12:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .