Can't change layout for fanzyZones

[OlaMallaug]

Environment

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

# Steps to reproduce

Using the PowerToys Settings, Select FancyZones, Select Edit zones, Select any zone and hit Apply.

# Expected behavior

Get a new zone layout like the previous version.

# Actual behavior

The zone is staying the default one. The default is Focus.
Tried the hot key. Tried to start as Admin. Tried to make my own zone template. Tried to reboot. Tried to re-install.


# Screenshots

<!-- If applicable, add screenshots to help explain your problem. -->

[crutkas]

@enricogior, i can't repo this.

@OlaMallaug sounds like you did an upgrade. Were you on 0.15.2?

[OlaMallaug]

Upgraded from 0.15.2. I'll try to downgrade and see if it works again.

[crutkas]

@olamallaung, thanks for working through this with us.

[OlaMallaug]

I uninstalled 0.16.0 and reinstalled 0.15.2 and it works fine again. Then I did the upgrade again and it's not working again. I uninstalled 0.16.0 and reinstalled it again, but still not working.
I have only one monitor, but it's a ultra-wide (3840 x 1080) monitor.

[enricogior]

@OlaMallaug
can you please reinstall 0.16, apply a columns template and then upload this file:

C:\Users\%USERNAME%\AppData\Local\Microsoft\PowerToys\FancyZones\zones-settings.json

Be aware it contains the app history section (is the list of apps that you have zoned), feel free to edit to remove it for privacy reasons.
When you upload it, rename to to use a .txt extension or zip it otherwise GittHub will not accept it.
Thank you.

[GeertvanHorrik]

I can confirm this as well on my ultra-wide monitor. Happens to my remote desktop sessions. It probably can't find the monitor device anymore. It works fine on the same monitor on the non-RD sessions.

Here is my remote desktop (virtualized) machine zone-settings.json:

{"app-zone-history":[],"devices":[],"custom-zone-sets":[]}

Here is the same monitor, but attached to real hardware:

    "devices": [
        {
            "device-id": "SAM0F99#5&29836fa9&0&UID261_1680_1050_{00000000-0000-0000-0000-000000000000}",
            "active-zoneset": {
                "uuid": "{17837D3A-33B0-4CE0-B8D2-C2CEE228A872}",
                "type": "columns"
            },
            "editor-show-spacing": true,
            "editor-spacing": 16,
            "editor-zone-count": 3
        },
        {
            "device-id": "SAM0F99#5&29836fa9&0&UID261_1920_1080_{00000000-0000-0000-0000-000000000000}",
            "active-zoneset": {
                "uuid": "{17837D3A-33B0-4CE0-B8D2-C2CEE228A872}",
                "type": "columns"
            },
            "editor-show-spacing": true,
            "editor-spacing": 16,
            "editor-zone-count": 3
        },
        {
            "device-id": "SAM0F9C#7&43b830e&0&UID256_5120_1440_{00000000-0000-0000-0000-000000000000}",
            "active-zoneset": {
                "uuid": "{36CC55BE-1BA6-48B1-90AA-8B6E04D2E73E}",
                "type": "priority-grid"
            },
            "editor-show-spacing": false,
            "editor-spacing": 16,
            "editor-zone-count": 3
        }
    ],
    "custom-zone-sets": []

[GeertvanHorrik]

Extra info:

I opened the zones-settings.json in notepad++. Then I open PT and select a new zone. It says the file has changed (so it has rewritten the contents), but the contents remain the same.

Whenever I re-open PT settings for FZ, the settings show the default (which is expected since the file is empty).

I also tried removing the file, and it creates a new one which is empty again.

[GeertvanHorrik]

If you want I can try to create a PR that fixes this (since I can repro this easily).

[enricogior]

Hi @GeertvanHorrik
we are aware of some problems with remote desktop session, please open a new issue since we can't track tow different problems in the same issue.
Thanks!

[OlaMallaug]

This is the content of my zones-setttings.json:

{"app-zone-history":[],"devices":[],"custom-zone-sets":[{"uuid":"{D7E5F903-6CF5-4BF0-A5E5-8277D0B60B75}","name":"Custom Layout 1","type":"canvas","info":{"ref-width":3840,"ref-height":1040,"zones":[{"X":0,"Y":140,"width":744,"height":624},{"X":744,"Y":140,"width":2304,"height":624},{"X":3012,"Y":412,"width":828,"height":624}]}}]}

[enricogior]

@OlaMallaug
is this still a problem with https://github.com/microsoft/PowerToys/releases/download/v0.21.1/PowerToysSetup-0.21.1-x64.exe ?

[OlaMallaug]

No, I have tested it and it works fine in 0.21.1. Thanks!

[xsirpreisx]

I am on v0.29.3 and I seem to be having the exact same issue. It worked before, but now it doesn't. This is the content of my zones-settings.json:

{"devices":[{"device-id":"PHL092A#5&4d1f448&2&UID257_2560_1440_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{FD063920-1C6E-4374-8677-5B99D9D6AF05}","type":"priority-grid"},"editor-show-spacing":false,"editor-spacing":2,"editor-zone-count":3,"editor-sensitivity-radius":2},{"device-id":"PHL092A#5&4d1f448&2&UID261_2560_1440_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{0273FD9E-19C9-4E56-B571-56F3F3B9AA92}","type":"priority-grid"},"editor-show-spacing":true,"editor-spacing":16,"editor-zone-count":3,"editor-sensitivity-radius":20},{"device-id":"FancyZones#MultiMonitorDevice_640_480_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{80B7905B-79FE-4D99-B371-6FC6521A07BC}","type":"custom"},"editor-show-spacing":false,"editor-spacing":1,"editor-zone-count":3,"editor-sensitivity-radius":1},{"device-id":"FancyZones#MultiMonitorDevice_3840_1080_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{2492FFF8-191A-4197-9AF8-310CA3E20216}","type":"priority-grid"},"editor-show-spacing":true,"editor-spacing":16,"editor-zone-count":3,"editor-sensitivity-radius":20},{"device-id":"FancyZones#MultiMonitorDevice_5120_1440_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{CED83B39-4CFE-47BF-80B2-F06CFB2EE6BC}","type":"custom"},"editor-show-spacing":true,"editor-spacing":0,"editor-zone-count":3,"editor-sensitivity-radius":2},{"device-id":"FancyZones#MultiMonitorDevice_3280_1440_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{F26BEC11-84F1-4CE9-AC5F-1136E66B415E}","type":"priority-grid"},"editor-show-spacing":true,"editor-spacing":16,"editor-zone-count":3,"editor-sensitivity-radius":20},{"device-id":"FancyZones#MultiMonitorDevice_4480_1440_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{F8C3A2CF-0F9F-4B1E-A7E2-9C67764F937D}","type":"priority-grid"},"editor-show-spacing":true,"editor-spacing":16,"editor-zone-count":3,"editor-sensitivity-radius":20},{"device-id":"FancyZones#MultiMonitorDevice_1920_1200_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{91CC5591-4AA4-4BA0-9779-2996E4018450}","type":"priority-grid"},"editor-show-spacing":true,"editor-spacing":16,"editor-zone-count":3,"editor-sensitivity-radius":20},{"device-id":"FancyZones#MultiMonitorDevice_2560_1440_{DC825A55-3C50-4A7F-A484-5E9B220519B3}","active-zoneset":{"uuid":"{0F10BAF7-95A4-4A91-BDB9-4FD644620732}","type":"priority-grid"},"editor-show-spacing":true,"editor-spacing":16,"editor-zone-count":3,"editor-sensitivity-radius":20}],"custom-zone-sets":[{"uuid":"{80B7905B-79FE-4D99-B371-6FC6521A07BC}","name":"Custom Layout 1","type":"canvas","info":{"ref-width":5120,"ref-height":1410,"zones":[{"X":1280,"Y":0,"width":2560,"height":1410},{"X":3840,"Y":0,"width":1280,"height":699},{"X":3840,"Y":699,"width":1280,"height":711},{"X":0,"Y":0,"width":1280,"height":1410}]}},{"uuid":"{CED83B39-4CFE-47BF-80B2-F06CFB2EE6BC}","name":"Custom Layout 2","type":"canvas","info":{"ref-width":5120,"ref-height":1410,"zones":[{"X":1548,"Y":0,"width":3572,"height":1410},{"X":0,"Y":0,"width":1548,"height":1410}]}}]}

[xrishox]

i'm having issues using fancyzones with remote desktop (rdp) in the latest release. I went back and installed 0.21.1 as was mentioned in this issue and it solved the problem. i'm not sure where the bug was introduced but it appears there was one.