Menu Start 11, incorrect positioning of a shortcut menu.

from Stardock Forums

I added a new item in the shortcuts a custom position and declared that it will have to be displayed as a menu, the problem is that the menu comes out to me on the other monitor, while if I declare the item it displays as a menu "recent items" the menu appears correctly where it starts the menu!

The situation occurs when there are two screens and the main one is not the laptop's native one, i.e. the custom position menu appears on the laptop's native monitor, while if you work with only 1 monitor, or with only the native one, the problem does not exist.

Lastly, the problem occurs regardless of whether "Show taskbar on all screens" is enabled.

Windows 11 Pro italian (22H2)
Start 11 (V.1.31)

start menu products
4,663 views 5 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Need more information.

  1. Windows 11 full version number please. Use Winver.exe.
  2. Please post a video or a screenshot of this issue.

Thanks.
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

 

On the left is the secondary, but native monitor of the laptop, on the right the external monitor set as primary, as can be deduced from the system tray and menu.

Shortcuts personal position

Galactic Civilizations III
Reply #4 from Stardock Forums Top

Hi mp62,

If you change the order of the icons and move it over to the right, does it display on the correct screen?

Paul Scroggins
Associate Technical Support Analyst

Reply #5 from Stardock Forums Top

So I put the recent items first and then the custom links, at this point the recent items menu opened in the secondary, while the custom items menu opened in the correct screen.

So I placed another link before the recent items and at this point both menus appear on the correct screen, i.e. the primary.

So the rule is if you want the menu to be displayed on the correct screen, you have to place the icon starting from the fifth position.
It's still a mistake, baby....maybe fix it in the next release. ;)