This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After applying the March 2021 updates to my Windows 10 20H2 home computer, I am unable to reconnect to my office computer which is also running Windows 10 20H2 and also received the March 2021 updates. I get the Remote Desktop Error "You have been disconnected because another connection was made to the remote computer"
This problem started yesterday morning. I generally connect to my office computer in the morning and disconnect in the evening. This has been working flawlessly for a year now. The problem only just started.
Yesterday, I found that I could reconnect sometime in the afternoon. I completed some work and disconnected again in the evening. This morning, when I tried to reconnect, I got the same error. Based on the message, it seems like part of the session is being held until it times out. I will see if I can reconnect again this afternoon.
My office PC is an AD Domain participant. My home PC is not. I typically use the Remote Desktop MS Store App to connect, which is up to date. However, I also tried connecting with the built-in Remote Desktop application and could not connect either.
I rebooted my home PC before attempting to reconnect. I also rebooted my remote PC yesterday, after I was able to reconnect in the afternoon. (I reconnected, rebooted, and reconnected again. Later that evening, I disconnected. This morning, I could not reconnect.)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 60%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETR%3C/text%3E%3C/svg%3E)
This has been happening to me, too.
There are two computers I connect to regularly, on different networks and with different configurations.
It happens with both. Until recently, it happened with neither.
It occurs when the connection is dropped due to an unreliable connection.
Normally, I get the "Attempting to reconnect to your session" message, attempts are made to reconnect, and after a few seconds everything is fine.
Not any more!
With this new issue, when a reconnection attempt is successful, it is usually followed by the "You have been disconnected because another connection was made..." message.
I checked the event log, and the only remote desktop logins have been from me.
This is definitely a new Microsoft bug.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 24%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
I had this same error when trying to RDP to a newly installed Windows Server 2019. It turned out error "You have been disconnected because another connection was made to the remote computer"" can be very misleading.........in my case it was generated not because of an existing session but because I had not yet set the IPv4 address, etc. on the network adapter, i.e. the server was not connected to the outside world. Even at my age I seem to live and learn!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 75%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
A solution in in my environment, change the PC name to ipv4 address of the remote windows machine. It seems picks the ipv6 address by default that caused the issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 91%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Possible, but on my Ip4 network, I have several machines that connect just fine. They're all running Windows 10 (latest version) and you'd think I'd have issues with all of them for the reason you mentioned. I had one machine with this problem and solved it by fixing a port forwarding issue (in an earlier post here). So, if using the Ip address works, it might simply be a NetBIOS issue on your network where it's not resolving the name-> IP properly.