Remote Desktop Sessions Disconnecting Improperly

In one of the past few RDM releases, whenever a Microsoft RDP session is closed, there is a high chance that the next time I try to RDP into it, I'll get the following error shown below.

If I click Yes, it logs out of the current session I want to connect to and starts a new RDP session. If I click No, it kills the attempted RDP connection. On the Windows side, it still thinks that there is an active RDP session even though it was closed in RDM. If I go to Task Manager and view the user, it doesn't show the user as disconnected. When it's in this state, I either have to wait for an unknown amount of time before Microsfte registers that it's disconencted and will allow me again to RDP in, or I have to do the following hack to force it out of its fake connected state.

# Connect remotely to the locked PC
Enter-PSSession -ComputerName <computerHostname>
# Get a list of the RDP connections
query session
# Force disconnect the "active" connection that needs to be disconnected
tsdiscon <sessionID>

If I don't execute the command above, I'm unable to RDP into the current RDP session as the OS still thinks it's connected and has somehow gotten into this state. If I wait for a while, I can log in again, but I'm not sure when the PC I want to RDP into decides it's OK again to log in. This is happening on multiple VMs and desktops that I'm trying to RDP into.

Current RDM: 2026.2.4.4