Troubleshooting

Troubleshooting

Symptom	Likely cause	Fix
Clicks/keys do nothing in one specific app	That app runs elevated; UIPI blocks input from a non-elevated sender	Run KeepPressing.exe as administrator
A game ignores the input entirely	The game reads Raw Input directly or is anti-cheat protected	Not solvable from the app side — see Known Limitations #5
A key stays "stuck down" after a crash	The process was force-killed mid-Hold, so the release never ran	Press the physical key/button once to clear it (Known Limitations #2)
The first clicks hit the KeepPressing window	Started with the on-screen button in current cursor position mode	Start with the hotkey, or use fixed coordinates
"… couldn't be assigned because another app is using it"	Another app already registered that global hotkey	Pick a different toggle key (F5 / F6 / F7 / F9 / F10)
The toggle key doesn't react	Some other app grabbed it after launch, or focus is on a fullscreen exclusive app	Choose another key; for emergency stop, mash Esc while running
Typing into a text field doesn't repeat in Hold mode	Hold sends a single key-down, not OS auto-repeat	Use Repeat mode instead (Known Limitations #3)
The actual press rate is lower than expected	OS timer resolution limits very small intervals	Treat ~10 ms (≈100/sec) as the practical floor
Characters/clicks land in the wrong spot	"Current cursor position" follows the live cursor	Switch to fixed coordinates and capture with F8

Reading a crash dump

If KeepPressing crashes, Windows Error Reporting may write a dump under:

%LOCALAPPDATA%\CrashDumps

(For example C:\Users\<you>\AppData\Local\CrashDumps\KeepPressing.exe.<pid>.dmp.) Attaching this file to a bug report helps a lot. The bug-report form (new issue) asks for it.

Reporting a bug

Open an issue with the Bug report template and include your KeepPressing version, your Windows version/build, clear reproduction steps, and a crash dump if you have one.

---

Related: Known Limitations · Hotkeys · FAQ