Agent
Splashtop Attended Access isn't allowing access with the error: “The user at the computer refused the connection”
We’ve identified the root cause. A recent Windows update (CVE-2026-26151) changed how systems handle incoming remote connections when an active RDP session is already in progress. When Attended Access is enabled, the system now automatically rejects the Splashtop connection rather than prompting the end user, resulting in the “user at the computer refused the connection” error.
Users are most likely to be affected if their assets frequently have active RDP sessions and have the Attended Access “Require Client Permission For Remote Access” policy setting enabled.
We have opened a High Priority Resolution Tracker post with more detail on the workaround and next steps as we work on a fix: https://community.syncromsp.com/t/attended-access-splashtop-remote-sessions-may-timeout-on-systems-with-active-rdp-connections/19400
We are currently investigating reports of connection issues when using Splashtop with Attended Access enabled.
Symptoms
Users have reported that when the Attended Access setting is active, the end-user on the remote machine is not receiving the required prompt to allow the connection. This causes the session to time out, resulting in the following error message for the technician:
“The user at the computer refused the connection”
Workaround
To restore remote access functionality, users can temporarily toggle off the Attended Access requirement. To do this, uncheck the ‘Require Client Permission For Remote Access’ checkbox within the Policy settings. Once the asset syncs, this will allow connections to proceed without the end-user prompt. Please note that if you utilize this workaround, you’ll need to re-enable this setting after the permanent fix is deployed.
Next Steps
Our engineering team is actively diagnosing the root cause. We apologize for any inconvenience this may cause your team and your clients, and we will provide further updates as they become available.