github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1476] Win10 barrier Server, Win11 barrier client Version 2.4.0 (both) #1125

New issue

Open

opened 2026-05-05 07:30:39 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:30:39 -06:00

Owner

Originally created by @Pi-Mania on GitHub (Dec 11, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1476

What happened?

Mouse would get lost trying to switch to Win11 machine. Keyboard would be active on Win 11 machine. If i persisted and waited long enough it would eventually come back to Win10 machine and work fine. Rolling win10 barrier version/server back to 2.3.4 Fixed issues. (Win11 still on 2.4.0)

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Github d/l

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

Windows

What OS versions are you using?

win10/win11

Relevant log output

No response

Any other information

No response

Originally created by @Pi-Mania on GitHub (Dec 11, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1476 ### What happened? Mouse would get lost trying to switch to Win11 machine. Keyboard would be active on Win 11 machine. If i persisted and waited long enough it would eventually come back to Win10 machine and work fine. Rolling win10 barrier version/server back to 2.3.4 Fixed issues. (Win11 still on 2.4.0) ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? Github d/l ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? win10/win11 ### Relevant log output _No response_ ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:30:43 -06:00

Author

Owner

@sylph520 commented on GitHub (Dec 11, 2021):

What happened?

Mouse would get lost trying to switch to Win11 machine. Keyboard would be active on Win 11 machine. If i persisted and waited long enough it would eventually come back to Win10 machine and work fine. Rolling win10 barrier version/server back to 2.3.4 Fixed issues. (Win11 still on 2.4.0)

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Github d/l

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

Windows

What OS versions are you using?

win10/win11

Relevant log output

No response

Any other information

No response

In my case, I'm using windows 11 as the barrier server, ubuntu as the barrier client, Version 2.4 seems not working, either. Once i move the cursor to ubuntu side, the cursor is lost and gone, and can't return back to windows 11 using the mouse of windows 11. Seeing your post, I try to downgrade to 2.3.4 on Windows 11, and it's working again, thanks, mate!

@sylph520 commented on GitHub (Dec 11, 2021): > ### What happened? > Mouse would get lost trying to switch to Win11 machine. Keyboard would be active on Win 11 machine. If i persisted and waited long enough it would eventually come back to Win10 machine and work fine. Rolling win10 barrier version/server back to 2.3.4 Fixed issues. (Win11 still on 2.4.0) > > ### Version > v2.4.0 > > ### Git commit hash (if applicable) > _No response_ > > ### If applicable, where did you install Barrier from? > Github d/l > > ### What OSes are you seeing the problem on? (Check all that apply) > Windows > > ### What OS versions are you using? > win10/win11 > > ### Relevant log output > _No response_ > > ### Any other information > _No response_ In my case, I'm using windows 11 as the barrier server, ubuntu as the barrier client, Version 2.4 seems not working, either. Once i move the cursor to ubuntu side, the cursor is lost and gone, and can't return back to windows 11 using the mouse of windows 11. Seeing your post, I try to downgrade to 2.3.4 on Windows 11, and it's working again, thanks, mate!

gitea-mirror commented

2026-05-05 07:30:44 -06:00

Author

Owner

@Ray-B commented on GitHub (Dec 17, 2021):

You can also check your scaling options for both your windows and non-windows machines. There is a known issue where having scaling beyond 100% can cause weird behaviour like this.

Once I set everything to 100%, my mouse stopped "going missing".

@Ray-B commented on GitHub (Dec 17, 2021): You can also check your scaling options for both your windows and non-windows machines. There is a known issue where having scaling beyond 100% can cause weird behaviour like this. Once I set everything to 100%, my mouse stopped "going missing".

gitea-mirror commented

2026-05-05 07:30:46 -06:00

Author

Owner

@gstru commented on GitHub (Dec 20, 2021):

I think I had the same problem. I have two machines with 125% scaling. The mouse cursor moved from one screen to the other super fast. To solve it I first tried with the script in powershell to adjust the mouse speed on the client but it didn't help. When I read the answer @Ray-B I modified the zoom and everything works now. At this point I tried another way to get the same zoom. I simply set a "custom resize" to 125% and it works great now. Thanks @Ray-B

@gstru commented on GitHub (Dec 20, 2021): I think I had the same problem. I have two machines with 125% scaling. The mouse cursor moved from one screen to the other super fast. To solve it I first tried with the script in powershell to adjust the mouse speed on the client but it didn't help. When I read the answer @Ray-B I modified the zoom and everything works now. At this point I tried another way to get the same zoom. I simply set a "custom resize" to 125% and it works great now. Thanks @Ray-B

gitea-mirror commented

2026-05-05 07:30:48 -06:00

Author

Owner

@Taknok commented on GitHub (Jan 13, 2022):

I confirm that the bug is also presents with Win 10 server 125% and Win 10 client 100%. The mouse is not missing, it is just locked in 0,0 (bottom right near notifications) which is like invisible. You can click on Windows 10 when the mouse bug and "is not visible (0,0)" the desktop is shown (which is the effect of bottom right button).

Affected version: 2.4.0
Last working version: 2.3.4

@Taknok commented on GitHub (Jan 13, 2022): I confirm that the bug is also presents with Win 10 server 125% and Win 10 client 100%. The mouse is not missing, it is just locked in 0,0 (bottom right near notifications) which is like invisible. You can click on Windows 10 when the mouse bug and "is not visible (0,0)" the desktop is shown (which is the effect of bottom right button). Affected version: 2.4.0 Last working version: 2.3.4

gitea-mirror commented

2026-05-05 07:30:50 -06:00

Author

Owner

@wxharry commented on GitHub (Jan 21, 2022):

I am having the same problem. I am using a win 11 as the server and a win 10 as a client. Both of the two machines are 125%. The mouse is stuck at the right bottom of the screen. When I set the scaling 100% on win 11 (the server), it works. Also, rolling back Barrier on the server works for me.

@wxharry commented on GitHub (Jan 21, 2022): I am having the same problem. I am using a win 11 as the server and a win 10 as a client. Both of the two machines are 125%. The mouse is stuck at the right bottom of the screen. When I set the scaling 100% on win 11 (the server), it works. Also, rolling back Barrier on the server works for me.

No labels

Rows
Columns