Windows 10 Remote Desktop Session Randomly Unexpectedly Terminates

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.