Doug_Schneider

Join Date 09/2001

Start 11 issues with menu location

Frustrated as &$#@/**!,

I have 5 different computers, all running Start11. They all have the same frustrating issue. At some point, the start menu starts jumping to the top of the Home Screen when the start menu button is pressed. It works normally at first, then at some point in the session it moves. I have no gap set for the menu and it doesn’t matter which style I use.

Each computer has a minimum of 16gb ram and they have different processors and video cards.

AMD 5600G and Intel 12400 each have on chip video, the 12600kf has a Radeon RX 6600, the 5600X has an nVidia 1030 and the 3700X has an nVidia 1650. It happens on 1080P monitors and 4K.

I thought it might be messing up because of my top screen Objectdock or CursorFX, but it happens regardless if they are running. I installed it on my newest bare computer and it still happened. I can’t believe no one else has experienced it.

I have been a subscriber to Objectdock for over 20 years, while you have dropped Objectdock support and whittled down your selections of usable programs to (3) in my view, Start11, CurserFX and Groupy. They are good enough for me, but Start11 has to work correctly. I can’t bear to use it with this bug, the menu should reliably stay where it is wanted. It adds nice features to Windows 11, I want to keep using it.

Help a transplanted Plymouth brother out…

Doug in Ohio.

start menu products

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

basj

Join Date 03/2001

+1684

Hello,
Sorry to hear you are having issues. I believe this is known compatibility issue with ObjectDock. Which, as you know, is not supported on Windows 10 and 11. I don't think its a bug on Start11. But, I have forward your problem to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thanks

Basj,
Stardock Community Assistant

Successfully updated karma reason!

RedneckDude

Join Date 04/2009

+2223

I thought it might be messing up because of my top screen Objectdock or CursorFX, but it happens regardless if they are running.

So, if ObjectDock is not running and you are using the Start 11 start button, it still happens? The ObjectDock start menu button is no good. And as Basj said, ObjectDock isn't supported on 10.

The ObjectDock service is still running even if the program is not.

Uninstall ObjectDock and your issue should go away.

Successfully updated karma reason!

I built the 2 Intel computers in quick succession. I think I tested Start11 on the last one before even adding Objectdock. I will disable the service and/or uninstall to test it. It’s shame if I have to pitch Objectdock. It was one of your best programs. It’s much better than NextStep. It’s easy to customize with the text based startup files. It’s also a lot cleaner than Fences. Fences just seems to be a different version of Microsoft’s standard “show icon”desktop. It has worked for years on Windows 10 with no issues. I wish that you could support it. Once Microsoft ditched tiles for the touchscreen, it seemed like perfect timing for a new version.

Thanks for your quick response.

Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

Also, just to be clear, I would always delete the Objectdock based start menu shortcut whenever I would create a dock.

Successfully updated karma reason!

Apparently your newest update 1.11 took care of the problem.

I don’t run Objectdock in auto start so I compared the menu before and after running Objectdock and I verified it only had the issue when Objectdock was running. I noticed there was a version update to Start11 and I read in the release notice that it addressed some of the moving menu issues. I installed it and reran the experiment. It now works fine with Objectdock.

Successfully updated karma reason!