wzyue

Would there be any way to get an option to choose which monitor the Start Menu opens when pressing the Windows key when using the enhanced Windows 10 taskbar? For example, an option to choose between always opening on the main monitor and the current behavior (opening on the monitor last interacted with). The default behavior (not using the enhanced Windows 10 taskbar) is for the Start Menu to open on the main monitor always when pressing the Windows key.

Yep, I've recorded doing the same thing but this time with both displays visible so you can see the actions I'm taking. The game I was using to demonstrate this behavior was Garry's Mod (as you pointed out afterwards), but I've confirmed that other games like Counter Strike: Source, Counter Strike: Global Offensive, Call of Duty: Modern Warfare, and more cause this behavior. I might have been using "exclusive fullscreen" incorrectly. I probably should have been referring to it as just "fullscreen" -- I wanted to differentiate between "borderless windowed" and "fullscreen" as explicitly as possible since this doesn't seem to happen when using "borderless windowed" mode. Also, I was incorrect when I initially reported the behavior. I stated that the working area on all displays break, but it seems that the primary display's working area actually does not. You can see in the video linked below I demonstrate that maximizing the Notepad window on the primary display works just fine after opening the game, whereas maximizing it on the secondary display causes the window bounds to exceed the taskbar area. You can also see that this does not happen when StartAllBack is uninstalled. Perhaps this has something to do with the mismatched resolution of my primary and secondary displays (1440p vs 1080p)? Note that I start the video with the latest RC of StartAllBack installed, open the game, demonstrate the maximize behavior, uninstall StartAllBack, open the game again, and then demonstrate that the erroneous maximize behavior does not occur when StartAllBack is uninstalled. https://streamable.com/i2wnaf

Yeah, that's exactly it. I enter a fullscreen application on my primary display (1440p display at 100% scaling) and the working area on all displays break (the primary display along with two additional 1080p displays at 100% scaling). I've taken a recording showing that the working area breaks (both windows maximize over the taskbar) when opening the fullscreen application when StartAllBack is installed (the first half of the video, the application is opened when the recording flickers). I then uninstall StartAllBack and open the same application and show that the working area does not break by repeatedly maximizing the Settings window.

Is there any workarounds to this that would stop the taskbar from breaking whenever I open a game/fullscreen application? I'm also using multiple displays with varying resolutions, maybe that could cause issues? This only happens with StartAllBack running, whereas without it the taskbar area is respected.

I'm running into an issue where opening any application that enters Exclusive Fullscreen (i.e. a video game) causes the taskbar to not be "respected" by other applications. Basically, other open applications will maximize over the taskbar even though the taskbar is not set to be hidden. Additionally, the Windows 11 Start Menu will open partially underneath the taskbar as if the taskbar size is smaller than what is displayed. This bug happens for both the Windows 11 taskbar and the "enhanced classic" StartAllBack taskbar. The only way I've found to fix the behavior is to either restart explorer.exe or toggle the "Automatically hide the taskbar" setting in Taskbar Settings, otherwise the behavior will continue even after the Exclusive Fullscreen application is closed. This does not happen when StartAllBack is disabled or uninstalled. Below are two GIFs demonstrating this behavior with both the Windows 11 taskbar and StartAllBack's "enhanced classic" taskbar when opening an Exclusive Fullscreen application. I'm wondering if anyone else has run into this issue other than me. I tried searching this thread and online for any mention of it but was unable to find anybody else reporting this behavior.