Start11 and Vertical Taskbar

from Stardock Forums

Hello everyone,

I'm experiencing an issue using Start11 and the Vertical Taskbar mod of Windhawk.

Wherever I click on the taskbar, it always pops up the Start11 start menu. To click on the other icons, I have to press CTRL (I suppose to bypass Start11) + click.

If I disable the Start11 start menu (only the start menu feature, not the whole app) and I revert to the standard Windows start menu, everything works fine.

Do you have any suggestion or it's a bug?

start menu products
3,331 views 4 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. But, it look like you on Windows 11 and Start11 do not work with vertical taskbar. It might be compatibility issue.

Thank you.
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

I reported this compatibly bug earlier and I got a response from the developer. It sounds like he will look into it once he circles back around to start 11 and maybe have a fix for it in an update 

For now you will have to assign the start 11 menu to open only with the windows key. (found under "control" in the settings menu)

edit- see reply #165 of posted link

https://forums.stardock.com/506879/page/7/#3948052

+2 Loading…
SoundPackager - Customize the Windows sound scheme
Reply #3 from Stardock Forums Top

Quoting PhoenixRising1, reply 2

I reported this compatibly bug earlier and I got a response from the developer. It sounds like he will look into it once he circles back around to start 11 and maybe have a fix for it in an update 

For now you will have to assign the start 11 menu to open only with the windows key.

I must have missed this one. Appreciate if you could post link to the post that mentioned this.

Thank you,

Basj,
Stardock Community Assistant

Reply #4 from Stardock Forums Top

You're right, thank you.

I currently set to open Start11 start menu only with the keyboard button instead of the mouse click, and it works.

Yes, it still doesn't work using the mouse, but it's enough for now...

I'll wait for the update that will fix this.

Thanks