Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Running Win7 Pro/64. Every time I accidentally hit AltGr + d (AltGr is the right Alt key), the "Fujitsu Display Manager" pops up, a utility that might be useful when it is called for but isn't when unintentionally brought up. This happens whatever program has the focus: browser, command prompt, even GVim. I guess I could solve this by just uninstalling the Fujitsu utility. Unfortunately, I'm the kind of person who wants to have control by understanding how things work. So I'd rather like to know how to disable the hotkey. Any advice?

share|improve this question
Note to self: Formatting keystrokes on SO/SF/SU goes like this: How can I format as keyboard keys? – Lumi May 15 '12 at 13:07

2 Answers 2

I found the answer! While I suspected there to be some registry key that stores all hotkeys (and there actually might be some registry key that does), this is not the approach people seem to follow when dealing with this kind of issue. Rather, it seemed from this and other pages that hotkeys are entered via the properties dialogues of shortcuts (but not straight programs).

So all I had to do to solve this, it seemed, was to locate the start menu shortcut for the Fujitsu Display Manager, open its properties dialogue, and disable the hotkey. And indeed! Using Explorer, I navigated to C:\ProgramData\Microsoft\Windows\Start Menu, further down to the appropriate entry for the program in question, and then opened the properties dialogue. Changing the hotkey setting requires Administrator privileges, so a quick UAC, and problem solved!

I still believe there must be a centralized storage for all those hotkeys, and I still think it's in the registry, so if anyone can point to that that's the answer I'm going to accept.

Update: I stopped believing in the registry theory. It seems that: "It's not stored in the registry. It's calculated at logon and kept in memory." This means file system scanning on every logon, and we all know such scanning is indeed occurring, so this scanning theory matches our experience. I haven't found a convincing explanation of why it is the way it is but the info I have is good enough for now. I still believe it would have been better to store the info in the registry but then I'm not a Microsoft programmer.

share|improve this answer
I couldn't get that vbs & batch/commands to work on your second link. I removed the 'on error' line & got this: "the shortcut pathname must end with a .lnk or .url", Code=80020009. I ran on a .LNK file I knew had a shortcut: FindHotKey.VBS "Snipping Tool.lnk". Since I didn't want to break down the script I looked elsewhere & found RJL Software's Shortcut Key Explorer worked beautifully! – gregg Nov 24 at 22:22

If you've got any programming experience, this isn't as hard as it seems.

You can use SetWindowsHookEx() to register a global hook, then check each callback type. If it's not the hotkey you're trying to block, just call CallNextHookEx() to pass the message along the queue. When you detect the hotkey, silently drop the message and don't call the next hook.

However, I don't know of a solution suitable for non-programmers.

share|improve this answer
Thanks. Interesting API function, but honestly, it sounds like overkill for this specific purpose. You'd patch an unwanted behaviour instead of simply removing it, thus adding complexity (and possibly brittleness, who knows?) to your setup. – Lumi May 15 '12 at 13:04
Fair enough. I just like hacking things! :) – Polynomial May 15 '12 at 13:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.