1. Enter the appropriate (x64 or x86) directory.

2. Run HotkeyDetective.exe as administrator.

3. If the window pops up without errors, press the stolen hotkey and Hotkey Detective will show you a path to the guilty process.

When you Google "show hotkey process", you’ll surely get many results that propose using Hotkey Explorer to solve your problem. This is a powerful tool, I used this many times, but on Windows 7. Apparently Hotkey Explorer doesn’t work very well on Windows 8 and later.

The core of the problem is probably the way how Hotkey Explorer finds out what program holds which hotkey. It essentially tries every possible combination and checks what program will react. Apparently Windows 7 had a possibility to inhibit the keystrokes, but it’s no longer valid for Windows 8+, and all keystrokes are sent to the system and other programs. Can you imagine the effect?

Hotkey Detective uses a similar approach, it hooks to every process and waits for it to receive a hotkey command. The biggest difference is that Hotkey Detective doesn’t force trying all hotkeys. You must press the stolen hotkey and Hotkey Detective will show you what process received the command.

Try running both versions (x86 and x64) when you are using x64 Windows. If you are unsure about your system’s platform, still try both of them, x64 won’t run on x86 platform anyway.

Remember to always run it with administrator privileges.

Make sure the hotkey you are trying is truly global. By "truly" I mean it’s registered with the system and can be triggered even when the owning application is in the background.

A good example is Ctrl + T in browsers, this works only when the browser is in the foreground. Hotkey Detective will not recognize this keystroke as it’s not registered with the system, only the browser knows about this combination.

The system loads the DLL shipped with Hotkey Detective into every process in order to spy on hotkeys. When Hotkey Detective is closed, the DLL is still present in the processes, and you simply can’t remove something the system is using.

Unloading the DLL from foreign processes is tricky and I’m currently working on it. For the time being, as a workaround I can only suggest restarting your system.

Added a warning message when trying to run Hotkey Detective as a non-admin user. This will greatly improve user experience, especially among users not reading readmes (I’m not reading them too, though).

The first major that brings up a basic but friendly UI in place of the scary console.

The very first version of Hotkey Detective, a simple console application.