[GH-ISSUE #1522] Mouse clicks and key presses are captured by VM on server and client machine simultaneously #1151

New issue

Open

opened 2026-05-05 07:32:13 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:32:13 -06:00

Owner

Originally created by @anthroid on GitHub (Jan 15, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1522

What happened?

When moving the mouse pointer from a VMware VM hosted on the Barrier server to a Barrier client:

Key presses are intercepted by the VM (on the server) and are not sent to the client.
Mouse clicks (but not movements) are simultaneously captured by the VM and sent to the client.
Mouse cursor movements are sent only to the client, while the cursor remains stuck in the center on the VM of the server.
Mouse scroll wheel movements are synchronized between the VM and the client.

This causes potentially problematic input to occur in the VM on the server, possibly even unnoticed before damage is done to a file, erroneous buttons could be pressed, or otherwise. I'm not sure if this can even be addressed in Barrier, but wanted to provide the info just in case.

Appears very similar to #880. Let me know if there is any other info I can provide.

Version

v2.3.4

Git commit hash (if applicable)

c43597c

If applicable, where did you install Barrier from?

https://github.com/debauchee/barrier/releases/tag/v2.3.4

What OSes are you seeing the problem on? (Check all that apply)

Windows

What OS versions are you using?

Barrier server:
Windows 10 Home (21H2)
OS Build 19044.1466

Barrier client:
Windows 10 Enterprise (1909)
OS Build 18363.1621

Virtual machine: (running on the Barrier server)
VMware Workstation 16 Pro (16.1.2 build-17966106)
Guest OS: Windows 10 Pro (1909)

Relevant log output

No response

Any other information

No response

Originally created by @anthroid on GitHub (Jan 15, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1522 ### What happened? When moving the mouse pointer from a VMware VM hosted on the Barrier server to a Barrier client: 1. Key presses are intercepted by the VM (on the server) and are not sent to the client. 2. Mouse **clicks** (but not movements) are simultaneously captured by the VM _and_ sent to the client. 3. Mouse **cursor movements** are sent only to the client, while the cursor remains stuck in the center on the VM of the server. 4. Mouse **scroll wheel movements** are synchronized between the VM and the client. This causes potentially problematic input to occur in the VM on the server, possibly even unnoticed before damage is done to a file, erroneous buttons could be pressed, or otherwise. I'm not sure if this can even be addressed in Barrier, but wanted to provide the info just in case. Appears very similar to #880. Let me know if there is any other info I can provide. ### Version v2.3.4 ### Git commit hash (if applicable) c43597c ### If applicable, where did you install Barrier from? https://github.com/debauchee/barrier/releases/tag/v2.3.4 ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? **Barrier server:** Windows 10 Home (21H2) OS Build 19044.1466 **Barrier client:** Windows 10 Enterprise (1909) OS Build 18363.1621 **Virtual machine**: (running on the Barrier server) VMware Workstation 16 Pro (16.1.2 build-17966106) Guest OS: Windows 10 Pro (1909) ### Relevant log output _No response_ ### Any other information _No response_