In the later versions of Windows 11, what support there was has been broken and newer Start11 builds have a workaround for this but our workaround does not handle autohide because so few people use on top taskbars with autohide and it adds a great deal of additional complexity to be handled which was out of scope for a quick update to allow taskbars to still be at the top of the screen.
Thanks for this Neil. Much appreciated. However, this does leave me with what he used to call a V-8 Moment. Why? I go back with Stardock to the very beginning of the company (used to know Brad when I owned a major QA company that did testing for him) and was a big fan of WB, but gave it up as, ultimately, I found I spent more time dealing with clashes between what WB wanted to do and what MS was doing.
Start10 seemed to be an exception to this reality and I never had any more than a short minor hiccup with it. I only moved to Windows 11 because of the reliability of Start10 and my desire to keep the taskbar and Start button at the top. Now that I've migrated I have to accept that I don't really have the benefit I thought I'd have with Start11.
I totally get that your data shows few people use my setup, but frankly from my perspective that hardly matters. hehe Again, no animosity there. Just frustration. My real annoyance is with MS who just can't fathom that some people think pull-DOWN menus should be opened from the top down (and I'm not a Mac user/fan).
My only real solution now is to either give up auto-hide (no thanks) or just get used to things on the bottom. Ugh. Here's hoping things change for this feature. Perhaps my best bet is to just give up entirely and stick with vanilla Windows options. THAT is the option Stardock absolutely shouldn't be hoping is the answer.