System
- Windows 11 24H2 (26100.3775) Pro
- Start11 v2.52.3
- 2 Monitors
- Primary (1): 3840 x 1600 (On right)
- Secondary (2): 3840 x 2160 (On left)
- RTX 5080 GPU
- Enhanced Taskbar
- Taskbar on top
- Taskbar (Start11) Auto-hide
- Start Menu left aligned
- Custom Start Button
Another minor, but annoying issue.
Sometimes, with the above configuration, Windows will manage to get into a state where a 1px gap is present above all maximized windows, through which one can see the desktop wallpaper like so (here the wallpaper is a solid red color for clarity):

This seems to happen almost at random, and remains this way for a while; you can resize, maximize, minimize, and restore any window, even ones that have not yet been opened, and they will all remain effected by this bug; although, eventually there is some kind of action one can take that will get it to go away until the problem is triggered again at a later time. The exact reason it gets in and out of this state is unclear, and may be affected by explorer refreshing due to program changes, or monitors being connected/disconnected; however, I was able to determine one reliable way to trigger the bug.
- Not strictly necessary, but best to work from a fresh restart when the system is settled
- Open a window and maximize it (unless it already opens maximized)
- Without touching the first window, open a second window and maximize it
- Restore either of the windows
- Minimize or restore the remaining window
- Maximize either of the windows (or the remaining one if you minimized the other)
- There will now be the 1px gap at the top of the screen until the state is somehow exited
Here is a sequence of me simply triggering the issue as fast as possible, such that it fits into a gif. Notice how at first the windows maximize correctly and take up the entire screen. NOTE: This was done in a minimal, single monitor VM for ease of reproduction, hence why there is a separate desktop wallpaper off to the right, but the issue also affects the host system):

And here is a video showing a reproduction of the issue, which also more thoroughly demonstrates how initially the bug is not present: