Bug with Start11 & Autohotkey

from Stardock Forums

Good morning,

I have used Start11 for a while now, and I'm generally happy with it.  I'm also using a lot of autohotkey bindings -- and many of these are bindings that use the windows key.  I'm also using synergy to use my desktop keyboard on a secondary machine: this is supposed to make all keys go to that client machine.

Recently I started having issues where an autohotkey binding brings up the start menu instead of doing what it's supposed to be doing.  There was also one occasion where using such a binding via synergy made the start menu popup on the desktop (which is also using start11) -- and that's the first time that I saw this kind of failure.

I finally decided to look more into this, and saw this blurb in the recent blog post:

... enhancements to how the Windows key functions including the ability to enable a block when a full-screen application is running and enhancements for when the foreground app is elevated.

So my guess is that this new change (which seems like it's correlated with when I started having these problems) is responsible for these problems -- probably the key grabbing that Start11 is doing is at a low-enough level that it snatches it away from autohotkey and (more surprisingly) from synergy.

Is there a way to disable this new functionality?

stardock software
2,930 views 5 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

Quick addition -- what I'm asking about is a way to disable the more aggressive binding of the windows key, not to disable it completely.

I do want to continue using the following setup:

Star Control: Origins
Reply #3 from Stardock Forums Top

You need to ensure you are using the very latest build as this should no longer be an issue.

If it continues please uninstall, reboot and then install the latest version from your downloads.

Reply #4 from Stardock Forums Top

I am on 1.47, and after a fresh boot, and it just happened again -- is there a newer build to try?

Reply #5 from Stardock Forums Top

Have you tried Neil's suggestion above? It is important to reboot immediately after uninstalled. And try downloading the installer again from your account. Install it, reboot immediately again. Retest it.

Thank you,

Basj,
Stardock Community Assistant