Win key modifier not recognized when held down on slave

19 views
Skip to first unread message

Ram Rachum

unread,
Dec 20, 2025, 3:16:36 AM12/20/25
to Input Director
Hi everyone

I'm experiencing an issue where modifier key combinations don't work correctly when controlling a slave computer.

Setup:
- Input Director v2.3
- Master: Windows 10 (Turing)
- Slave: Windows 10

Problem:

When I transition to the slave and hold down the Win key,  sometimes together with ctrl or alt, while pressing another key (e.g., Win+Ctrl+E, Win+shift+Arrow,), the key works, but if i keep the modifiers pressed and re-press the key, it gets sent without the modifiers.

This is particularly problematic because I have many AutoHotkey/hotkey scripts that use Win as a modifier.

The issue doesn't occur when using the keyboard directly on either machine—only when controlling the slave through Input Director.

Any suggestions? Is there a setting that affects how modifier key states are transmitted?


Thanks,
Ram.

Shane

unread,
Dec 29, 2025, 9:32:23 PM12/29/25
to Input Director
Hi Ram,

Input Director reacts to key up / down events and sends those to a client system when its being controlled. Holding down a modifier key and keeping it held whilst pressing other keys won't resend the modifier key unless its released and pressed down again.

The issue doesn't occur when using the keyboard directly on either machine—only when controlling the slave through Input Director.

Are you transitioning away and back again to the client or does control remain with the client when this occurs?

Regs,

Shane.

Ram Rachum

unread,
Dec 30, 2025, 8:17:45 AM12/30/25
to input-d...@googlegroups.com
Hi Shane,

Thanks for your quick response.

Control stays with the client when this happens. No transitioning involved.

I think the issue isn't about whether the modifier key-down event gets sent. It's about whether subsequent keypresses include the modifier flags. When I press arrow while holding Win+Ctrl, that arrow keypress should carry the Win and Ctrl flags with it. After the first keypress, later ones (sometimes) seem to lose the modifier info even though I'm still holding the keys.

Is there a difference between how the initial modifier key-down is handled vs. how modifier state gets attached to other key events?

Thanks,
Ram

--
You received this message because you are subscribed to a topic in the Google Groups "Input Director" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/input-director/WapFzhrQYxE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to input-directo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/input-director/d42491b3-0240-4cab-be4d-174b5d0d8724n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages