PowerToys: "Keep windows in their zones when the active FancyZones layout changes" or "Keep windows in their zones when the screen resolution changes" doesn't work properly anymore.

Environment

Windows build number: [Version 10.0.19041.388]
PowerToys version: v0.19.2
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Create a separate layout for landscape and portrait orientation on a Surface/Windows tablet, then snap a window in one of the zones, rotate the screen to portrait orientation, and back to landscape orientation.

Expected behavior

Windows should stay in their assigned zones, just like in the older v0.18.2 build.

Actual behavior

Windows don’t stay in their assigned zones between portrait and landscape orientation changes.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 32 (15 by maintainers)

Most upvoted comments

@CorneliousJD what PC are you using, is it a Surface? These features are working as expected beside some specific hardware configurations.

Nope just a Windows 10 desktop PC. I’m using a super-ultrawide @5120x1440 along with another regular resolution screen attached as well. When the ultrawide goes into sleep mode since it’s DisplayPort the PC just assumes it’s disconnected and when it gets hooked back up, windows do not open back to their last known zones, and instead open in the top left corner. – With 0.18.x installed they would open back up to their correct zone assignmens.

CorneliousJD on Aug 4, 2020

Same here. I’ve a UHD Display (5120x1440). I’ve to layouts:

Screen divided in three zones/columns of same size
Priorty grid with three columns

Expected: If I change between both layouts, windows will resize

Reality: Nothing happens. In older versions it worked.

Here my configuration:

DrSebastianPauli on Oct 1, 2020

@crutkas UPDATE - problem solved easily. What I can’t explain is why the symptoms only occur using my integrated Intel UHD 630 graphics but not using my dedicated nVidia GPU given both via DisplayPort. Evidence online suggests this problem has been around for years, but then so has Intel IGD and Windows so seems crazy it’s not been addressed.

Cause: Windows capturing a dummy GraphicsDriver entry in registry (inmy case ‘NOEDID_8086…’) configured with a low resolution 1080x768 each time my monitor goes into a sleep cycle. On monitor wake this is loaded and applied rather than the other ‘live’ entry which contains the correct resolution (5120x1440).

Solution: Follow instructions in links below to regedit Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration dummy driver entry (in my case ‘NOEDID_8086…’) and set the correct resolution values.

markeman on Sep 21, 2020

@CorneliousJD what PC are you using, is it a Surface? These features are working as expected beside some specific hardware configurations.

enricogior on Aug 4, 2020

Is this sitll not currently fixed with the 0.20 release? 😦

CorneliousJD on Aug 4, 2020