Clipboard sharing works Director→Client but not Client→Director (W10 Pro Director / W11 LTSC Client, v2.4)

[Andy K]

Hi, I'm running Input Director 2.4 (latest) with the following setup:

• Director: Windows 10 Pro 22H2 (CorsairOne)
• Client: Windows 11 LTSC 24H2 (Kamrui mini-PC)

Symptom: Copying text or file names on the Director and pasting on the Client works fine. Copying text on the Client and pasting on the Director does not work — no error message appears, it simply pastes whatever was last copied on the Director itself (i.e., it appears the Director never receives a "clipboard changed" notification from the Client, so pressing paste just falls back to its own existing clipboard content).

What I've already checked/ruled out:

• Both instances of Input Director are running non-elevated (not admin) — same on both machines
• "Share Clipboard" is enabled in Global Preferences on both machines
• File copy/paste mode is set to "file copy/paste" (not network shares) on both
• "Use cached IP addresses" — tried both on and off, no change
• Each machine has a single network adapter (no multiple NICs/VPN adapters causing interface confusion); Preferred Network Interface is set correctly on each (Realtek USB 2.5GbE on the Client, Realtek PCIe 2.5GbE on the Director)
• No clipboard managers, macro tools, RGB utilities, remote access tools, or screen recorders running in the background on either machine — only Opera, Firefox, IDM, MPC-BE, SABnzbd, and Plex running on both
• Windows Clipboard History and Cloud Clipboard sync are not a factor (Client is LTSC, which doesn't expose "Sync across devices" the way standard W11 does)
• No firewall error or Input Director error dialog appears when pasting fails — it's a silent fallback to the Director's local clipboard, not a timeout or explicit failure
• Couldn't locate log files under ProgramData or AppData — not sure if 2.4 logs by default or if logging needs to be enabled somewhere I'm missing

• Question: Has anyone seen clipboard sharing fail specifically in one direction with a Windows 11 LTSC Client? I'm wondering if LTSC's stripped-down build is missing something Input Director relies on for the Client-side clipboard-change detection/notification (as opposed to the Director-side "set clipboard" push, which works fine). Any pointers on how to get more verbose logging out of 2.4 would also help me dig further on my end.

  Happy to provide more details (exact build numbers, network config, etc.) if useful.

  Thanks!