Sep 19 2019 08:06 AM - edited Sep 19 2019 09:19 AM
Hi Team,
My windows 10 users keep getting this error message many times when they try to log into RDP sessions.
They get this error for about 7 times then logged in.
I've looked around but don't have a good answer or findings.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
Were on 1903
Sep 19 2019 03:29 PM
Is there anything in the Eventlog on the machine they are RDPing to?
Is the machine they are RDPing to also Windows 10 1903 or are they connecting to and RDSH server?
Sep 20 2019 07:51 AM
@PaulaSillarsWindows server 2008 SP1
Sep 21 2019 03:24 AM
Sep 22 2019 09:42 PM
@jvalois Is it a virtual server or physical?
Is the issue related to loading of users onto the server?
Also, try changing the remote desktop setting on the server to allow connections from a computer running any version of Remote Desktop (less secure) to see whether the issue still exists. I did see this a few months back with an update.
May 27 2020 04:18 AM
1. Click the Windows or Start button and type "certmgr.msc". This will start the Certificate Manager.
2. Click on Action | Find Certificates and type "Safeguard" in the Contains field and click on the Find Now button.
3. The results should be displayed below, expand the Issue To column and select (to highlight) SafeguardCluster.
4. Right-click and select Delete.
5. Click Yes on the questions.
May 28 2020 07:00 AM
@jvalois had similar issue on Terminal server (2008R2) logging in from Win 10 1903. found out it was being caused by the RDP certificate. regenerated the Certificate and issue was resolved for us.
Sep 09 2020 12:12 AM
I found solution as IP conflict remote machine with other VM.
Jun 01 2021 08:42 AM
The steps you are providing: are you doing this on the RD server or on the Windows 10 client?
Jun 01 2021 08:48 AM
Apr 25 2023 07:45 AM
@jvalois I faced the same issue but I could get over the issue by following the below steps :
In the remote desktop connection dialogue box, Click on Experience and uncheck 2 options
- Persistent bitmap caching
- Reconnect if the Connection is dropped
Clearing the cache would solve the issue.
Worth giving it a try...!