Mouser version
3.6.0
How are you running Mouser?
Official GitHub release asset
Build / asset details
Windows installer from v3.6.0
Operating system
Windows 11
OS version details
25H2
Mouse connection type
Bluetooth
Logitech Options+ status
What happened?
When trying to set Win+Shift+S as a custom button shortcut, Windows intercepts the key combination before Mouser's shortcut capture dialog can register it, opening the Snipping Tool instead.
Expected behavior
The shortcut capture dialog intercepts the key combination before Windows processes it, allowing system-level shortcuts like Win+Shift+S to be assigned.
Steps to reproduce
- Click a button to assign a custom shortcut
- Press
Win+Shift+S in the capture dialog
- Windows Snipping Tool opens — shortcut is not recorded
Device info JSON
Log file contents
Screenshots or screen recordings
No response
Additional context
This affects any shortcut that Windows intercepts at the shell level. A workaround is to temporarily set DisabledHotkeys = S under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced in the registry and restart Explorer, which allows the shortcut to be captured. The value can be deleted afterward.
A proper fix would be to use a low-level keyboard hook in the capture dialog so Mouser receives the input before Windows does.
Mouser version
3.6.0
How are you running Mouser?
Official GitHub release asset
Build / asset details
Windows installer from v3.6.0
Operating system
Windows 11
OS version details
25H2
Mouse connection type
Bluetooth
Logitech Options+ status
What happened?
When trying to set
Win+Shift+Sas a custom button shortcut, Windows intercepts the key combination before Mouser's shortcut capture dialog can register it, opening the Snipping Tool instead.Expected behavior
The shortcut capture dialog intercepts the key combination before Windows processes it, allowing system-level shortcuts like
Win+Shift+Sto be assigned.Steps to reproduce
Win+Shift+Sin the capture dialogDevice info JSON
Log file contents
Screenshots or screen recordings
No response
Additional context
This affects any shortcut that Windows intercepts at the shell level. A workaround is to temporarily set
DisabledHotkeys = SunderHKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advancedin the registry and restart Explorer, which allows the shortcut to be captured. The value can be deleted afterward.A proper fix would be to use a low-level keyboard hook in the capture dialog so Mouser receives the input before Windows does.