[GH-ISSUE #1624] VMWare Multi-Monitor, 2nd monitor window does not release mouse and keyboard to client #1203

New issue

Open

opened 2026-05-05 07:35:56 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:35:56 -06:00

Owner

Originally created by @abstractlabs on GitHub (Mar 30, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1624

What happened?

This is probably an edge case but when using multi-monitor support with VM Ware the 2nd window if focused will hold the mouse and keyboard. A workaround is to select a window that is not vmware to release keyboard and mouse then switch to barrier client machine.

Version

v2.4.0

Git commit hash (if applicable)

3e0d758b59

If applicable, where did you install Barrier from?

Github

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

Windows, macOS

What OS versions are you using?

Windows 8 Server with VMWare Workstation 16.2.3 build-19376536
Mac OSX Catalina Client

Relevant log output

No response

Any other information

Knowing this is an edge case the issue seems like it may be vmware's issue but wanted to post for anyone else that may run into it. The workaround is annoying but tolerable given the complexity of the configuration.

Originally created by @abstractlabs on GitHub (Mar 30, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1624 ### What happened? This is probably an edge case but when using multi-monitor support with VM Ware the 2nd window if focused will hold the mouse and keyboard. A workaround is to select a window that is not vmware to release keyboard and mouse then switch to barrier client machine. ### Version v2.4.0 ### Git commit hash (if applicable) 3e0d758b59e44e6bb8b5e13cf96c824be44207ac ### If applicable, where did you install Barrier from? Github ### What OSes are you seeing the problem on? (Check all that apply) Windows, macOS ### What OS versions are you using? Windows 8 Server with VMWare Workstation 16.2.3 build-19376536 Mac OSX Catalina Client ### Relevant log output _No response_ ### Any other information Knowing this is an edge case the issue seems like it may be vmware's issue but wanted to post for anyone else that may run into it. The workaround is annoying but tolerable given the complexity of the configuration.

No labels

Rows
Columns