FancyZones not allowing differing layouts on different monitors

[twistypigeon]

Microsoft PowerToys version

0.60.0

Running as admin

• Yes

Area(s) with issue?

FancyZones, FancyZones Editor

Steps to reproduce

Open FancyZones layout editor
Select first monitor and assign a template to monitor 1
Select second monitor and assign a different template to monitor 2

✔️ Expected Behavior

Monitors maintain their distinct and different templates

❌ Actual Behavior

Both monitors are assigned the same template layout

Other Software

No response

[SeraphimaZykova]

You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!

[CheoWalker]

I am experiencing the same issue.

[okimurak]

I'm experiencing the same issue.

PowerToysReport_2022-07-08-21-59-17.zip

[twistypigeon]

PowerToysReport_2022-07-08-14-08-14.zip

[permafrown]

PowerToysReport_2022-07-08-09-18-22.zip
same issue

[itmestan]

same issue, here are my full logs as well.

PowerToysReport_2022-07-08-06-04-19.zip

[Fifteen15Studios]

Commenting here because I was told to do so on another issue. Bug Report Tool results attached.

Comment from other issue:

I just experienced this same bug on a 2-monitor setup. Left monitor and right monitor have different zone layouts in the settings. But in practice, both screens have the zone layout of the left screen.

I'm not sure if it matters, but I was using a custom layout on the left screen, and a prebuilt template on the right screen (Priority Grid.) Now, whatever layout I set for the left screen applies to both screens.

Also, the monitors are attached to a laptop. However, the laptop is closed. I'm only using the 2 external monitors, not the laptop monitor. If I open the laptop and use that monitor, the layout set for that monitor works perfectly. This bug seems to only affect externally connected monitors.

Also, my monitors are connected via a USB-C HP dock.

PowerToysReport_2022-07-08-15-54-47.zip

[JokingChicken]

@SeraphimaZykova
is this already fixed?

because i found the problem:
seems that a check is missed when setting the new layouts here:

PowerToys/src/modules/fancyzones/editor/FancyZonesEditor/Utils/FancyZonesEditorIO.cs

Line 839 in c36a80d

if (monitor.Device.MonitorName == layout.Device.Monitor &&

missing: monitor.Device.MonitorInstanceId == layout.Device.MonitorInstanceId

so now if there are duplicate monitors, it will set them both to the same layout

you where on the right track with the last commit;
2f77450e25f07496ff608b96c6ade574d9c494f9

[jonnormandy]

@jaimecbernardo Just wanted to report the test build did resolve the bug I was experiencing with FancyZones in version 0.60.0.

[jaimecbernardo]

Thanks everyone for helping debug and test this!
We'll include this fix in the next release.

[cn-mining]

The test build in #19203 comment is working for me now and resolves the issue I reported in #19389. Thank you for the fix.

[pastansberry-clgx]

If the fix is confirmed as working, are those of us just now discovering the issue this morning better off rolling back to 0.59.1 or just sticking it out and waiting for 0.60.1 to be deployed? How long does that usually take?

[asanjabi]

@asanjabi , you might also want to delete your local "%localappdata%\Microsoft\PowerToys\FancyZones\Logs" and "%localappdata%\Microsoft\PowerToys\FancyZones\Editor\Logs" after that previous build from yesterday, since it must've filled with some logs.

@jaimecbernardo I tried clearing the logs unfortunately did not fix the problem, found something interesting in the app logs though, the last line goes on forever every few milliseconds.

[2022-07-13 09:59:43.839758] [p-27380] [t-27384] [info] fancyzones logger is initialized
[2022-07-13 09:59:43.891583] [p-27380] [t-27476] [trace] OnThreadExecutor::worker_thread(loop) Enter
[2022-07-13 09:59:43.891592] [p-27380] [t-27384] [trace] FancyZonesSettings::LoadSettings Enter
[2022-07-13 09:59:43.899270] [p-27380] [t-27384] [trace] FancyZonesSettings::LoadSettings Exit
[2022-07-13 09:59:43.957830] [p-27380] [t-27476] [trace] OnThreadExecutor::worker_thread(loop) Exit
[2022-07-13 09:59:43.957942] [p-27380] [t-27476] [trace] OnThreadExecutor::worker_thread(loop) Enter
[2022-07-13 09:59:43.958172] [p-27380] [t-27384] [info] Display changed, type: 3
[2022-07-13 09:59:43.960427] [p-27380] [t-27384] [info] No Virtual Desktop Id found in registry
[2022-07-13 09:59:43.979301] [p-27380] [t-27384] [info] Identifying monitors
[2022-07-13 09:59:43.979633] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.979853] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980172] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980371] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980588] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980787] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}

[asanjabi]

@asanjabi , you might also want to delete your local "%localappdata%\Microsoft\PowerToys\FancyZones\Logs" and "%localappdata%\Microsoft\PowerToys\FancyZones\Editor\Logs" after that previous build from yesterday, since it must've filled with some logs.

@jaimecbernardo I tried clearing the logs unfortunately did not fix the problem, found something interesting in the app logs though, the last line goes on forever every few miliseconds.

[2022-07-13 09:59:43.839758] [p-27380] [t-27384] [info] fancyzones logger is initialized
[2022-07-13 09:59:43.891583] [p-27380] [t-27476] [trace] OnThreadExecutor::worker_thread(loop) Enter
[2022-07-13 09:59:43.891592] [p-27380] [t-27384] [trace] FancyZonesSettings::LoadSettings Enter
[2022-07-13 09:59:43.899270] [p-27380] [t-27384] [trace] FancyZonesSettings::LoadSettings Exit
[2022-07-13 09:59:43.957830] [p-27380] [t-27476] [trace] OnThreadExecutor::worker_thread(loop) Exit
[2022-07-13 09:59:43.957942] [p-27380] [t-27476] [trace] OnThreadExecutor::worker_thread(loop) Enter
[2022-07-13 09:59:43.958172] [p-27380] [t-27384] [info] Display changed, type: 3
[2022-07-13 09:59:43.960427] [p-27380] [t-27384] [info] No Virtual Desktop Id found in registry
[2022-07-13 09:59:43.979301] [p-27380] [t-27384] [info] Identifying monitors
[2022-07-13 09:59:43.979633] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.979853] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980172] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980371] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980588] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
[2022-07-13 09:59:43.980787] [p-27380] [t-27384] [info] Get display device for display \.\DISPLAY1 : \?\DISPLAY#MEI96A2#4&289d63ab&1&UID265988#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}

[jaimecbernardo]

@asanjabi, my bad. Please uninstall that version and restart the computer.

@asanjabi, that version was bad for your configuration :) Please uninstall and restart the computer.

[jaimecbernardo]

There's this one #19203 (comment)
But we should be releasing the 0.60.1 hotfix soon that also fixes it.

[asanjabi]

@asanjabi, my bad. Please uninstall that version and restart the computer.

@asanjabi, that version was bad for your configuration :) Please uninstall and restart the computer.
@jaimecbernardo
Opps, I missed that :) I'll wait for the hot fix. Thanks for chasing this down.

[jaimecbernardo]

The hot fix was released in 0.60.1: https://github.com/microsoft/PowerToys/releases/tag/v0.60.1
Thanks everyone for your help here!

[jaimecbernardo]

For those who installed the debug build, please uninstall it and install 0.60.1 instead, so you can continue receiving updates.

[qsergii]

PowerToysReport_2022-07-14-11-31-28.zip

[shouldent]

This is still open but I read from the comments that it should be fixed in v0.60.1. Is that correct?

[danielsamuels]

0.60.1 seems to have completely broken FancyZones' ability to remember which layout was active when using remote desktop. It always defaults to Priority Grid. Uninstalling and installing 0.59.1 fixes it.

[shouldent]

0.60.1 seems to have completely broken FancyZones' ability to remember which layout was active when using remote desktop. It always defaults to Priority Grid. Uninstalling and installing 0.59.1 fixes it.

Yikes... I am keeping my old v0.59.0.. Thanks!

[jeffward01]

I am referencing this comment: #19240 (comment)

My original bug report: #19240 (comment)

Current Install:
Build 0.60.1

Report of my findings:

• At first when I applied the layout to my 3 monitors, Fancy Zones appeared to 'mix my monitors up again'.
• When I went to film a demo video to report this occurring, the issue went away 🙃
• I have not restarted my computer yet, we will see how it goes
• So far, within a short 10 minutes of testing, 0.60.1 appears to have fixed my issue with the mixup of the layouts (Fancy zones was mixing up Layout A with Monitor 1. Then later, Fancy Zones would show Layout A is applied to Monitor 2. This appears to be fixed....
• I am hesitant to say it is 'fixed' because I have not tested appropriately.

Thanks!

[jeffward01]

I am referencing this comment: #19240 (comment)

My original bug report: #19240 (comment)

Current Install: Build 0.60.1

Report of my findings:

• At first when I applied the layout to my 3 monitors, Fancy Zones appeared to 'mix my monitors up again'.
• When I went to film a demo video to report this occurring, the issue went away 🙃
• I have not restarted my computer yet, we will see how it goes
• So far, within a short 10 minutes of testing, 0.60.1 appears to have fixed my issue with the mixup of the layouts (Fancy zones was mixing up Layout A with Monitor 1. Then later, Fancy Zones would show Layout A is applied to Monitor 2. This appears to be fixed....
• I am hesitant to say it is 'fixed' because I have not tested appropriately.

Thanks!

I just wanted to update my comment with so far the issue has vanished. This appears to be fixed 🚀

[permafrown]

PowerToysReport_2022-07-08-09-18-22.zip same issue

The latest update (0.60.1) has resolved the issue for me.
Thanks for the steady and expert work!

[ouTPhaze]

Unsure if a similar issue, but every time I reboot my Win11 PC, the applications I have set to zones switch monitors.

I stick to the latest version, and seems every time I reboot, startup apps that have zones seems to be on the wrong monitors, every time.