[GH-ISSUE #677] Windows Lock screen shortcut (win+L) causing program to stop working #535

Open
opened 2026-05-05 06:37:33 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @ThinkSalat on GitHub (May 19, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/677

Operating Systems

Server: Windows 10 v1909

Client: MacOS Catalina

So, the win+L shortcut is registering on my server even though I'm locked into my Mac. I use that shortcut to open the address bar in chrome, and it seems like every time I do it, it locks my server, which causes the keyboard shortcut to switch back to my mac to stop working.

I use only one monitor and switch between them, so this makes me go back to my windows machine, unlock it, and then hit the keyboard shortcut again. It's a really annoying experience.

Are there any workarounds to this? Or any options that can prevent it?

Originally created by @ThinkSalat on GitHub (May 19, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/677 ### Operating Systems ### Server: Windows 10 v1909 Client: MacOS Catalina So, the win+L shortcut is registering on my server even though I'm locked into my Mac. I use that shortcut to open the address bar in chrome, and it seems like every time I do it, it locks my server, which causes the keyboard shortcut to switch back to my mac to stop working. I use only one monitor and switch between them, so this makes me go back to my windows machine, unlock it, and then hit the keyboard shortcut again. It's a really annoying experience. Are there any workarounds to this? Or any options that can prevent it?
gitea-mirror added the
doc
label 2026-05-05 06:37:33 -06:00
Author
Owner

@hiuwo commented on GitHub (May 19, 2020):

Yes there is a workaround way on your windows to just disable the workstation lock keyboard shortcut:

(source: https://www.itprotoday.com/windows-78/how-can-i-disable-lock-workstation-when-i-press-ctrl-alt-del)

  1. Start the registry editor (regedit.exe)
  2. Move to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System.
  3. From the Edit menu select New - DWORD value.
  4. Enter a name of DisableLockWorkstation and press Enter.
  5. Double click on the new value and set to 1. Click OK.
  6. Close the registry editor.

Hope this helps

PS I hope the above will suffice. There is also away to prevent certain keys to be sent to server/client but I don't remember where it is set, might be command line or some obscure settings, or you could try Configure Server > Hotkeys (tab) New (Keystroke), OK> New (Actions), OK > Press and relase a hotkey > check Only on these screens and choose which screen.

<!-- gh-comment-id:630722101 --> @hiuwo commented on GitHub (May 19, 2020): Yes there is a workaround way on your windows to just disable the workstation lock keyboard shortcut: (source: https://www.itprotoday.com/windows-78/how-can-i-disable-lock-workstation-when-i-press-ctrl-alt-del) 1. Start the registry editor (regedit.exe) 2. Move to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System. 3. From the Edit menu select New - DWORD value. 4. Enter a name of DisableLockWorkstation and press Enter. 5. Double click on the new value and set to 1. Click OK. 6. Close the registry editor. Hope this helps PS I hope the above will suffice. There is also away to prevent certain keys to be sent to server/client but I don't remember where it is set, might be command line or some obscure settings, or you could try Configure Server > Hotkeys (tab) New (Keystroke), OK> New (Actions), OK > Press and relase a hotkey > check Only on these screens and choose which screen.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 22, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

<!-- gh-comment-id:696466431 --> @github-actions[bot] commented on GitHub (Sep 22, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

I think this should be at least documented. Until this is not done, this bug should stay up.

<!-- gh-comment-id:757535149 --> @p12tic commented on GitHub (Jan 10, 2021): I think this should be at least documented. Until this is not done, this bug should stay up.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#535
No description provided.