Windows rotated one zone down numerically on second virtual desktop after monitor change

[WazBurrows]

Microsoft PowerToys version

0.71.0

Installation method

PowerToys auto-update

Running as admin

No

Area(s) with issue?

FancyZones

Steps to reproduce

• I have different monitor configurations for my laptop for work and home. 2 x 4k monitors at work and 1 x huge 4k at home. I don't use the laptop primary display at all at either location, only the external monitors at each place.
• I've created a second windows virtual desktop (by clicking Win + Tab and hitting the + button to add the second desktop) that I use for both work and home, and I keep those desktops up because I have a lot of windows open in each.
• The FancyZones zone layout is different for all 4 virtual desktops (work 1 & 2, home 1 & 2), so I have 4 hotkeys that I use to reinstate the appropriate layout whenever I go from home to work and vice versa.
• When I change locations, I don't shutdown the laptop just reconnect the monitor(s) to the laptop at the new location.
• After I login I use the appropriate hotkey pair for the location (home or work) to restore the windows to their zones for that location. I do this for each virtual display.

✔️ Expected Behavior

I expect that when I hit the hotkey for each virtual window display at the new location, that the behavior is that any windows that are out of place should move to the positions that I setup for those hotkeys.

❌ Actual Behavior

The expected behavior works only for the first virtual desktop. For the second virtual desktop however, the windows are moved to zones that are one zone down (numerically) of where I originally set them to be. I say "down" because if I select each window and use the Win + right arrow key combo the window will move to the zone it was originally supposed to move to. This seems to be related to the zone number. So, if the window was supposed to move to zone 5 on the second desktop when the I hit the hotkey then its actually moved to zone 4 instead. So then by hitting Win + right arrow I manually move it from zone 4 to zone 5. This is consistent for all windows on the second desktop as if they have all been moved one zone down, numerically.

Additional note: using the hotkey to move the windows on the second screen back into position after a monitor change did work at one time but I noticed that it stopped working a few of FancyZones back. I don't exactly which version this problem for the second virtual desktop started happening.

Other Software

No response

[TheJoeFin]

Is this issue still relevant in v0.74.1? /needinfo

[WazBurrows]

I just got back from vacation and haven't been in the mode of working between home and office which is where the behavior was exhibited. I've also just recently updated to the latest version of the tool. I'll be going into the office again next week at which point I'll be able to confirm whether the problem still occurs.

[WazBurrows]

Hi @TheJoeFin I was still able to reproduce the issue on the two displays at work today. When I connected the displays and woke the laptop, I was presented with the two displays showing windows virtual desktop 2 but the windows were out of place and the wrong size, since I had just come from my single 47" display (also with 2 virtual desktops) at home. When I hit the hotkey to switch to the window configuration for the virtual desktop 2 that I use at work the windows moved into zones within the zone configuration but not to the zones they have always been assigned to. In contrast, after a reboot, any apps that I open will automatically load into the right zone. As noted previously and in more detail above, I was able to use the FancyZones "window move" key sequence to move them into their correct zone but needed to move them all "right" by one. Today I noticed the same issue with virual desktop 1 as well - which normally doesn't suffer from this problem.

[cinnamon-msft]

/dup #15285

[microsoft-github-policy-service]

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!