Start11 1.46 Release Issue Report Thread
With the Start11 1.46 release, we are creating this thread so that users can report any observed issues.
Thank you for your interest and any time you put into making Start11 a better product.
With the Start11 1.46 release, we are creating this thread so that users can report any observed issues.
Thank you for your interest and any time you put into making Start11 a better product.
Known issues
While we appreciate all feedback, please remember that we offer no official support for beta \ preview \ developer channel versions of Windows. If you report issues while in any of those early release channels, you should not expect them to be addressed unless it still exists in a retail version of Windows.
***Reserved***
Sorry Sean, I posted this in the wrong thread. It's for this version (1.46):
Quick-hide does not work on this version. It works once, then I have to uncheck "Show desktop icons" (Fences enables it) to hide the Fences again. Happens all the time, so I rolled back to previous version since this is the most important feature for me - to keep the desktop clean.

Windows 10 22H2 19045.3086
Jan, this thread is for Start11, not Fences. Did you mean to post here?
https://forums.stardock.com/521098/fences-417-beta-feedback-thread
Sean Drohan
Stardock Product Lifecycle Manager
Inconsistent Start Button behavior.
Windows Version: 22H2 Build 22621.1848
In Start11 settings, I have chosen 'Start11 menu' for all options.

However, I see different things depending on whether I click the Start button with my mouse or press the Windows key.
Clicking the button brings up the expected Windows 10 style start menu. Pressing the Windows key brings up the Windows 11 style start menu, regardless of whether I am in a full screen or desktop application.
If I change the setting to 'Windows Menu' I see the Windows 11 menu. This was happening with the previous update of Start 11 and continued after the update to 1.46

Uninstall Start11, reboot (important), reinstall 1.46.
Better?
I am still having troubles with the taskbar on additional monitors as per the picture. The main screen is fine, the other two monitors show as attached. If I change the main display to another monitor the taskbar on the screen is fine and the other two look like the picture. I have looked at old threads but nothing I have tried has worked.
Surface Pro 9
OS: Win11 22H2 (OS Build 22621.1848)
Stardock version: 1.46
Stardock enhanced taskbar: On
Taskbar buttons combined: Always
Optimise taskbar for touch interactions: Off
Autohide taskbar is on


So the issue only happens on Secondary monitors?
If you disable autohide does the problem go away (after a sign out)?
And if you turn that 'feature' off, log out \ in of Windows, does it still happen?
Sean Drohan
Stardock Product Lifecycle Manager
Version: 1.46 (1.4.6.0 file version)
[...]
[...]
I am sorry to report that the issue is not yet resolved; I still encounter it on my three Win 11 22H2 installations (all fully updated).
As mentioned before I already encountered it on v1.31 and reported it:
[...] When the system boots up and the login animation is running, the taskbar looks exactly as I want it (i.e. the Windows default). But after 1-2 sec., Start11 kicks in and you can see some slight changes in color and transparency, the clock shows seconds (which is okay, because that is the one feature I actually want) and the border/line at the top of the bar disappears. [...]
It actually got fixed in v1.32 (beta only) and made it to the 1.36 release:
[...]
Tweak to resolve an issue with the line on the taskbar in 22H2 being too transparent when in dark mode
[...]
After that, I did not update Start11 for some time, so I did not notice the re-appearence of this bug before v1.45. My observation is exactly the same as I described it in my original report. As soon as Start11 is loaded (which is clearly visible when the taskbar clock starts to show seconds), the line disappears.
So, what I want to say is that you already managed to solve it, but somehow it sneaked its way back into your product. My guess is that you "simply" have to reproduce that fix from 1.32+.
What is the actual version number (winver.exe)? Are you running any other similar products?
Paul Scroggins
Associate Technical Support Analyst
What is the actual version number (winver.exe)? Are you running any other similar products?
Paul Scroggins
Associate Technical Support Analyst
My version is Windows 11 22H2 (build 22621.1848).
I use dark Windows mode + light App mode. I have no other customizing installed. Appearence settings of the taskbar in Start11 are left at default.
But I noticed something interesting just now. When I turn off Start11's automatic color switch in the taskbar settings and then turn it back on, the line actually appears, but it is way too dark (or maybe too transparent?).
After booting and loading of Start11 (buggy; line is missing completely):

After turn-off/turn-on of auto-coloring (buggy; line is drawn, but too dark):

How it should look like (line is clearly visible):

What do I mean with "automatic color":

Maybe this helps in tracking it down.
With the new Win key changes it makes any muti-key shortcuts containing the windows key un-usable as the start11 menu over-rides it... for example I have Microsoft PowerToys run set up with the key combo ctrl+win+left as well as others that I'm now unable to use without setting the win key to open the default windows 11 start menu inside start11, which kinda defeats the purpose.

The menu you see for a brief second is PowerToys Run, the thing I was trying to load using the aforementioned key combo... It stays loaded up until I release the win key (at which point the start11 menu over-rides it), which isn't much use as I can't use it while holding the win key.
Winver: 22621.1848
If there's a way to revert the windows key setting back the non-elevated mode, I would like to know how, as I've gotten very accustomed to my ctrl+win key combos at this point... I have found a temporary solution, by setting the win key to open the default windows 11 menu (doesn't over-ride it, nor show at all if I use the windows key as part of key combo... aka pre-Start11 update behavior), allowing me to use my key combos, but making it so I need to hit my windows key twice to get up the start11 menu.
Edit: Default key-combos using windows key behave correctly, but not my custom ones (ctrl+win+arrow keys)
And if you turn that 'feature' off, log out \ in of Windows, does it still happen?
Sean Drohan
Stardock Product Lifecycle Manager
Hi Sean,
It looks like autohide is the culprit. When autohide is turned off the taskbars are fine. Is there any plans to fix this as I prefer to use autohide for my taskbars.
Cheers
Chris

In what order are you pressing those keys?
It isn't reproducing here with ctrl + win+ arrow?
I believe that we have a fix in the works for this, stay tuned
Paul Scroggins
Associate Technical Support Analyst
After updating to 1.46 and restarting, I still get Close All Windows, and I don't see a config option to choose otherwise. What am I missing?
Do you have the taskbar buttons uncombined?
Paul Scroggins
Associate Technical Support Analyst
Yes, of course.
I'm not sure what would be up with that. I would suggest uninstalling, reboot, reinstall and see if that takes care of it

Also, are you running any other similar products?
Paul Scroggins
Associate Technical Support Analyst

In what order are you pressing those keys?
It isn't reproducing here with ctrl + win+ arrow?
In order of press holds, ctrl, left win, d-pad left... then on releasing win it instantly pops up start11, regardless of other keys still being held, this is not the case for inbuilt windows key combos, but does it for every arrow key
How do I do that without losing all of my start menu customization?

Just make sure you do not check the "remove settings" option when uninstalling
Paul Scroggins
Associate Technical Support Analyst
Welcome Guest! Please take the time to register with us.