What you see, why, and what to do.

"Windows protected your PC" when running the installer

The installer is not code-signed yet. Click More info, then Run anyway. If your antivirus quarantines the file, restore it and add an exception for the DeskStitch folder: a KVM installs a keyboard hook and injects input, which scanners treat as suspicious until the publisher has a reputation.

The two PCs never connect (pill stays grey)

• Both windows list what they see: Discovery on the host, Host on LAN on the client. If both say "no beacon", the network blocks broadcasts between the PCs.
• Firewall: the first start asked to allow DeskStitch; if you declined, allow it in Windows Security → Firewall → Allow an app for private networks.
• VPN: NordVPN and others block local traffic by default. Enable "Allow LAN access" (or pause the VPN to test).
• Guest Wi-Fi or "client isolation" on the router keeps devices apart; use the normal network or a cable.
• Different pairing codes: the host's Settings must contain the code the client shows.
• Fixed IP as a fallback: host Settings → Other PC → type the client's IP instead of auto.

The cursor lands in the wrong place on the other PC

The desk map does not match the desk. Open Edit layout on the host and drag the tile to where the screen really stands; edges snap, arrow keys nudge by a millimetre. If a monitor reports a wrong physical size (rare, shows in the tile), edit widthMm/heightMm in layout.json (Help → Edit layout.json).

The cursor stops at an edge instead of crossing

Nothing lies across that edge on the desk map (a dead zone, like Windows between mismatched monitors), or you are within the corner block distance of a corner. Look at the map; drag screens so the edges you use overlap. Background: why the cursor jumps between a 4K and a 1440p monitor.

Typing gives wrong characters on the other PC

Keys travel as physical scan codes, so the other PC's keyboard layout decides what a key produces. Set both PCs to the same layout (Windows Settings → Time & language → Language). The optional "match keyboard layout" setting under Advanced can switch the other PC's focused window automatically, but it is experimental.

Shift or Caps Lock behave oddly on the other PC

Check the keyboard layout first (above). Then check Windows' accessibility shortcuts on that PC: holding right Shift for 8 seconds turns on Filter Keys, pressing Shift five times turns on Sticky Keys. Turn those shortcuts off under Settings → Accessibility → Keyboard.

Input does not reach an administrator window, a UAC prompt or a game

DeskStitch runs as administrator so input reaches admin programs; if you declined the prompt it runs without and cannot. UAC prompts on the secure desktop and games in exclusive full screen never accept injected input; switch the game to borderless window mode.

Movement feels too fast, too slow or "floaty" on the other PC

Settings → Speed multiplier adjusts the other PC only. Movement → relative lets the other PC apply its own pointer settings, which many people prefer.

A Snap-layouts box or a tooltip appears on the host while I work on the other PC

Fixed in 0.3.0: the host parks its hidden cursor under a tiny window of its own so nothing underneath reacts. If you still see it, send diagnostics.

The cursor is invisible after a crash

Start DeskStitch again (it restores the system cursors), or Windows Settings → Bluetooth & devices → Mouse → Additional mouse settings → Pointers → OK.

"Trial ended" although I entered a key

The key is checked on the host only. Open License on the host and paste it there; the client never needs one. A key issued for an earlier version of DeskStitch is rejected with "signature mismatch": ask for a re-issue.

Where things are