PowerToys
PowerToys copied to clipboard
Fancyzones Excludes Taskbar from Window Height
Microsoft PowerToys version
0.62.0
Running as admin
- [x] Yes
Area(s) with issue?
FancyZones, FancyZones Editor
Steps to reproduce
After the most recent Windows system update (see below), Fancyzones seemed to want to draw the windows at the full height of the monitor, even though the taskbar takes up space at the bottom. This causes the bottom of various windows to be cut off when positioned with Fancyzones. To resolve this, I've had to create custom zones with a "buffer" at the bottom of the boxes the height of the window. What's strange is that this has happened periodically to me before, but this is the first time I've had it happen consistently, even after a restart.
Sample of the layout I've had to create, with bottom padding:

Result of snapping windows to fancy zones:

Windows version information:
Version 21H2
Installed on 1/27/2022
OS build 22000.978
Serial number 015403103157
Experience Windows Feature Experience Pack 1000.22000.978.0
✔️ Expected Behavior
Sizing the a zone in the fancyzones editor to the full height of a monitor should not be able to exceed the height of the user space of the display.
❌ Actual Behavior
Snapping a window causes the bottom to be drawn "behind" the taskbar, cutting off the bottom of the window. This is exacerbated in chat applications (slack, messenger, discord, etc) when the input field is at the bottom of the window.
Note that you cannot see the bottom arrows of the scrollbar.
Other Software
No response
Also observed on Windows 10 21H2 Build 19044.2006 Experience 120.2212.4180.0; occurs with taskbar on top of screen as well.
Edit: Occurs sporadically, stopped occurring after undock/re-dock
i've been noticing this for months with every windows update. to fix it each time, i turn fancyZones off and then back on again.
sadly I also have this issue with Powertoys 0.65 and 0.66 any steps that supposedly should fix it don't work for me
/dup #10903
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!