FancyZones sometimes does not detect taskbar height on windows startup and snaps windows 'under' the taskbar

[tobymartyn]

Microsoft PowerToys version

0.59.1

Running as admin

• [ ] Yes

Area(s) with issue?

FancyZones

Steps to reproduce

1. Re-start Windows 10 or Windows 11 PC.
2. Snap a window (e.g. Edge browser) to a zone that goes full height of the desktop (e.g. the shipped 'Priority Grid' layout).
3. Observe where window snaps-to

✔️ Expected Behavior

The bottom of the window aligns with the top of the taskbar.

❌ Actual Behavior

The bottom of the window aligns with the bottom of the screen and part of the window is hidden behind the TaskBar.

Disabling and re-enabling FancyZones, then re-snapping the window results in the correct behaviour. It appears that during windows startup, FancyZones might be establishing the available window height before the taskbar has been fully initialised. If FancyZones happens to establish the available window height after the taskbar has been initialised on startup, the behaviour is not observed.

Other Software

No response

[mplessis]

Same issue here, after quit and reload PowerToys, FancyZones runs correctly

[hennys]

Can confirm that this happens on Windows 11 as well.

[trevrobwhite]

Fancy zones has been driving me crazy by clipping off the bottom of the window and the only way around it was to either manually size the window or hide the taskbar and un-hide it again (this works until you move the window again)

I'm running on a laptop with an ultra wide monitor, I like splitting this in two when I'm not working with wide apps.

As mentioned the bottom of the app would always be clipped, when using Excel this is especially a pain because you cannot switch sheets easily.

On checking my Windows settings after reading #5935, I could see the windows are clipped on the top edge:

Changing this so the monitor is clipped on the lower edge fixed the issue immediately (on Windows 10 x64)

Reloading Fancy zones does work as a workaround but this seems to fix it permanently so maybe that helps pinpoint the bug in working out the window heights.

For the record I do prefer my Window to be aligned at the top as generally my mouse is near the top of the screen and now it gets stuck in a dead zone

[torbennehmer]

I do have the same issue intermittently, using 2 simple Full HD (1920x1080) displays without any fancy scaling. Restarting PT does fix it as well here. An unconfirmed guess is that it is related to display configuration changes, as I'm too using a notebook, but on a docking station and with the internal display disabled, just using the two displays via the dock. Right now, the system had rebooted after windows update and started the session in the background (as Windows 10 does these days). Maybe this is related to it, I could imagine that the taskbar is not yet rendered if the user session launches in the background?

[kstange]

Same issue here, after quit and reload PowerToys, FancyZones runs correctly

I don't have to fully restart PowerToys, just turning off and back on FancyZones from the PT settings panel seems to do the trick for me.

[Sylvanas-1977]

Still an issue today

[docrinehart]

Still an issue on 0.64.0, running as admin on Windows 11 Pro. Toggling FancyZones off and back on works.

I haven't fully verified, but it does seem to happen most often on reboot or possibly when waking from sleep. I'd also suspect that zones might be jumping ahead of the taskbar getting initialized.

[Cube707]

Same issue. I think its related to me having to log in on my laptop and than closing it (so deactivation the display) to only use my two monitors

[Aronjlove]

This issue has persisted on both my personal and work device through the last two updates. I've even uninstalled and reinstalled it, but I imported backed-up settings instead of starting fresh.

[Aaron-Junker]

/dup #10903

[microsoft-github-policy-service[bot]]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!