This issue has shown up with some applications that also use mouse hooks. We contacted Microsoft about it, and it turns out that because our hooks run at high integrity, Windows won't pass the hook messages to the program with lower integrity hooks after we're done with them, for security reasons. Apparently a program that runs hooks at high integrity could modify the messages before passing them to the low integrity program.

We've contacted Stardock to see if we can work together to find a solution for this issue, but for now there are a few workarounds:

• Make sure ObjectDock starts up after DisplayFusion. It works this way, because the hooks chain is Last In, First Out, and lower integrity hooks can pass the messages to higher integrity ones. So, if ObjectDock is started after DisplayFusion, it will get the mouse hook messages first, then pass them to DisplayFusion.
• Disable the Mouse Management options on the DisplayFusion Settings > Window Management tab (not ideal if you need those features)
• Disable UAC (also not ideal, from a security standpoint)

Sorry for the long-winded technical explanation, hopefully it makes sense. Please let me know if you have any other questions at all.

Thanks!

No problem, Lance. Glad to hear it!