Zone keeps changing to match other monitor

[JerryLaneJohns]

Microsoft PowerToys version

0.82.1

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

FancyZones Editor

Steps to reproduce

I have 3 monitors as shown in the attached image. I'm attempting to make monitor 1 have two equal zones. Monitors 2 and 3 should have a single zone each. I can edit the zones accordingly. However, monitor 3 always changes from a single zone to two zones when I save the configuration.

Note that I am not using the "default for horizontal monitors" option.
Note that monitor 3 is the laptop's built-in monitor; monitors 1 and 2 are external monitors

✔️ Expected Behavior

Monitor 1 have two zones; Monitor 2 have one zone; Monitor 3 have one zone.

❌ Actual Behavior

After saving the configuration, monitor 3 changes to have two zones. When I reopen the editor, monitor 3 shows only one zone even though I originally saved it with two zones.

It seems like monitor 3's configuration is changing to match monitor 1.

Other Software

No response

[similar-issues-ai]

We've found some similar issues:

• Zones Change Size/Shrink on Multi-Monitor Setup with Portrait Monitor #19423 , similarity score: 84%
• Fancy Zone Editor resets setting on second monitor #28237 , similarity score: 83%
• FancyZones Editor keep reducing zone sizes when switching between monitors #20112 , similarity score: 83%
• Fancy Zones #19216 , similarity score: 83%
• FancyZones doesn't remember layout for one monitr/duplicates settings #19279 , similarity score: 83%
• FancyZnoes; not remembering second monitor layout #18625 , similarity score: 82%
• Fancy Zones and multiple monitors #19237 , similarity score: 82%
• Fancy Zones With 3 Monitors - FZ monitor Number Not In Agreement With Windows Monitor # #23555 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[nguyen-dows]

/dup #26729

[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!