FancyZones refuses to use selected layout

[david7a68]

Microsoft PowerToys version

0.61.1

Running as admin

• Yes

Area(s) with issue?

FancyZones, FancyZones Editor

Steps to reproduce

1. Sign in to PC account (PowerToys starts automatically)
2. Open an window and attempt to snap to layout active before shutdown
3. Discover that the Priority Grid default layout is in use
4. Open layout selector
5. Select (double-click) desired custom layout
6. Layout selector closes automatically
7. Click and drag window titlebar while holding Shift key
8. Priority Grid layout is still active
9. Close PowerToys from taskbar
10. Start PowerToys from start menu
11. Attempt to snap active layout
12. Discover that desired custom layout is (somehow) active

✔️ Expected Behavior

FancyZones should remember the layout that was active on shutdown and reactivate that layout on startup.

❌ Actual Behavior

FancyZones defaults to the Priority Grid default layout on startup and refuses to change layouts without restarting PowerToys manually.

Other Software

No response

[Jay-o-Way]

/bugreport

[ghost]

Hi there!

We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? 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!

[david7a68]

Of course.
PowerToysReport_2022-08-05-17-26-34.zip

[Eagle3386]

This bug is even worse than the OP describes as re-opening FZ's selection dialog/window still shows Priority Grid as active while the previously selected (custom or other default) layout is actually active & also stored correctly within FZ's settings file.

In other words: FZ's selection dialog/window refuses to show the correctly selected layout, too.

[cinnamon-msft]

/dup #24817

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