FancyZones forgets Virtual Desktop layouts

[thunderousleader10]

ℹ Computer information

• PowerToys version: 0.230
• PowerToy Utility: FancyZones
• Running PowerToys as Admin: Yes
• Windows build number: 2004 (19041.508)

📝 Provide detailed reproduction steps (if any)

1. Apply specific custom layouts to different virtual desktops on Windows 10

✔️ Expected result

The layouts I applied to be maintained on each virtual desktop

❌ Actual result

The unique layouts are maintained for a while but eventually (and I have no idea why) the layout from one desktop gets applied to all other virtual desktops, removing any existing layouts that were applied there.

📷 Screenshots

[enricogior]

@thunderousleader10
did you delete and recreate the Virtual Desktops?
Can you please upload %localappdata%\Microsoft\PowerToys\FancyZones\zones-settings.json?

[tmarki]

I have the same problem, it's annoying that I have to set the proper custom zone setup for desktop #2 all the time. My file is attached.
zones-settings.zip

[enricogior]

@tmarki
you didn't specify if this is after the layout setting was lost or after you re-applied.
Also you have two monitors, did it happen for both or just for one and in case on which one?

[tmarki]

Found that it resets when the monitor goes to sleep or is disconnected on the laptop, so essentially display switching.

I'm attaching 3 files:

zones-settings-bad-pre - initial state, it was reset (both desktops on TopGrid A)
zones-settings-good-set - when I set the good config (TopGrid A and TopGrid B for desktop 1 and 2)
zones-settings-bad-after - disconnected the monitor and reconnected after a few seconds which caused the reset to the first state

I hope this helps!
zones-settings-bad-after.zip
zones-settings-bad-pre.zip
zones-settings-good-set.zip

[enricogior]

@thunderousleader10 @tmarki
if for you it's acceptable to install a private unsigned build, I've attached a build that may fix the issue.
We understand if you prefer to not install an unsigned build.

PowerToysSetup-0.23.1-x64.zip

[ScarabMonkey]

I confirm this also occurs for me since updating to 0.23 ... it was working fine with 0.21.

[ScarabMonkey]

@thunderousleader10 @tmarki
if for you it's acceptable to install a private unsigned build, I've attached a build that may fix the issue.
We understand if you prefer to not install an unsigned build.

PowerToysSetup-0.23.1-x64.zip

This seems to solve it.

[tmarki]

Yup, the fix works. Will this auto-update to the official version when the fix is released, or will I need to manually reinstall?

[enricogior]

@tmarki
thanks for testing it.
It should auto-update to 0.23.2.

[crutkas]

Fixed in https://github.com/microsoft/PowerToys/releases/tag/v0.23.2

[Jon999999]

@enricogior

Unfortunately, this bug appears to have come back for me with v.0.25.0.

[crutkas]

@Jon999999 please create a new issue

[Jon999999]

@Jon999999 please create a new issue

Already working on it with @enricogior over at #7790 .