A recent AVG and Avast antivirus update is preventing DisplayFusion 9.9 from launching on some systems. If you're running into this issue, please update to the latest DisplayFusion 10.0 Beta.
I understand that DisplayFusion on Windows 10, from version 7.3.2 onward, disables any keybind combinations that incorporated Windows + E (Open Windows Explorer), and other Windows system reserved key combinations introduced in the November 2015 Windows update.
There is a registry edit for Windows 10 that will disable specific hotkeys. Under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced, create an Expandable String Value called DisabledHotkeys and enter as values the hotkeys to be disabled. E.g.,
Is there a way to take advantage of this registry workaround in order to use system reserved keybinds in DisplayFusion, either natively or through another workaround?
Interesting! I wasn't aware that you could do that. At the moment those hotkeys are hard coded to be ignored in DisplayFusion, but I will put this on our list and see what we can do.
I wanted to see if there was a chance to permit this workaround, perhaps by changing the hard code ignore for Win+E shortcuts into a warning so that we could use the registry edit.
This issue should be fixed up in the latest beta, available here: https://www.displayfusion.com/Download/Beta. Please let me know if you still run into any trouble after updating.
Yes, but there's a bit of an asterisk on it. DisplayFusion used to not allow you to even attempt to set the key combinations that we knew were Windows key combinations. It now will allow you to attempt to, if it finds that registry value.
However, our key combinations still use Windows Global Hotkeys, so we say "please let us register this hotkey" and Windows either returns a success or a fail.
For some of the Windows key combinations, even if they're "disabled" with the registry value, Windows is still holding on to them and not allowing other apps to register them, it's just not doing anything when they're pressed.
That's interesting and frustrating, because every new Windows release seems to usurp a Win key combination I'm using either here or with Autohotkey. The latest one was Win+Alt+B, which I map in AHK, and I uninstalled Game Bar to get it back. That was before I ran across this forum thread, which I came across when trying to use Win+B in DisplayFusion to map "Send to Back". I haven't tried the registry hack yet and may stick with Ctrl+Win+B, but I wonder if using the registry for "B" would have worked for Win+B and also made Windows surrender Win+Alt+B... lol
BTW, the inverse of "Send to Back" appears to be Alt+Tab. Some people say Alt+Esc works for "Send to Back", but when I use Alt+Esc, some apps brought to the front such as Outlook register Alt as being held down and show their Alt key shortcut tooltips. The DisplayFusion function doesn't have this side effect.
Hey! Was wondering is here any progress? I'm now trying DisplayFusion trial, but I cannot set hot keys. For example Win + 0 ir Win + Shift + 0. This hot keys are used for applying window layouts in my AutoHotkey script.
AutoHotkey has not issue to set up these hotkeys, but DislayFusion struggles with the message: "The Key Combination you have specified is reserved by Windows and can't be used."
Thus, it's obviuosly possible to set up these keys, it's just DisplayFussion seems to not try
P.S. I obviuosly exist AutoHotkey script, before trying to setup these hot keys. And windows indeed take over, and win + 0 for whatever reason displays me spotify window (because it's number 10 in taskbar)
The reason it works in AutoHotkey is because AHK uses keyboard hooks. We use Windows' global hotkeys to prevent conflicts.
If we're able to add an option to use keyboard hooks in the future, we'll be sure to let you know.
Thanks!
Thank you! I guess life is always a compromise: DisplayFusion is for sure better at setting windows positions, while AutoHotkey is better with hotkeys. I think I need an AutoHotkey script which triggers DispalyFusion script
I guess life is always a compromise: DisplayFusion is for sure better at setting windows positions, while AutoHotkey is better with hotkeys. I think I need an AutoHotkey script which triggers DispalyFusion script 
