So I've finally decided to transition to 11, caveats n all. DF as always is part of my must-haves after the format. Upon installing I started noticing some wonky behavior.

Every restart when I clicked the 'show hidden icons' button in the system tray, it would open up in the top left corner of the monitor instead of where it was supposed to.

I had imported my very old DF fusion settings with a very large list of window profiles etc. I thought something set in there may have something to do with it so I uninstalled DF and started fresh. Did nothing but add my license key.

Same behavior.

Just wanted to put this out there. While its relatively minor its certainly annoying. Nobody likes bugs that ruin the polish or makes things appear janky, especially when starting from scratch after ditching 5 years of customization with being fresh/new and presumably bug free being one of the few perks of doing so

It happens the first time i try to click it. second time is okay.

Same thing I reported here:
https://www.displayfusion.com/Discussions/View/win-11-corner-overflow-menu/?ID=14ea2740-a786-490e-a731-3fb8ddd3055e#10

This bug is still present in Beta 17.

Ok, something changed in the latest beta channel version of Windows 11. Now, the first time I open the system tray hidden icons it still appears in the upper left, as reported here.

After that first time, instead of opening in the proper location, above the arrow in the system tray, the hidden icons menu is appearing on my second monitor (no taskbar there).

I believe so, yes.

Here's a screenshot of what I'm seeing now.

This is on Windows 11 22H2 Build 22623.870 by the way.

Here you go!

Huh ... I just got Build 22623.857 and the problem went away. The first time I click the tray icon to open the hidden items it still appears in the upper left hand corner (so that still needs to be fixed) but subsequent clicks it opens in the proper place. Weird. Nevermind I guess!

This seems to be fixed in Beta 18 on Windows 11, but is still happening on Windows 10 (for me anyway).

Still a problem in Windows 10 with Beta 19.