Fancy zones broken on the applicaion used with Workspace feature!

[jacopolepera]

Microsoft PowerToys version

0.84.0

Installation method

PowerToys auto-update

Running as admin

No

Area(s) with issue?

FancyZones

Steps to reproduce

The bug occurred when i used the shortcut for the edito, closed it immediately, and now the shift doesn't snap to the zones anymore

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Other Software

No response

[similar-issues-ai]

We've found some similar issues:

• FancyZones shift key not allowing zone snapping #10866 , similarity score: 89%
• Fancy Zones #34625 , similarity score: 86%
• fancyzones bug needs help #20786 , similarity score: 85%
• Fancy Zones don't work #29552 , similarity score: 85%
• FancyZones not working after update #13852 , similarity score: 85%
• Fancy Zones stop working #15103 , similarity score: 84%
• FancyZone caused my shift key to malfunction #26100 , similarity score: 83%
• FancyZones is not working after waking up from sleep #31262 , similarity score: 81%
• Facyzones: Since new update can not snap chrome windows to zone. Other apps are fine.  #25424 , similarity score: 81%

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.

[jacopolepera]

EDIT: The bug only occurs with application that i use in the new feature Workspace!

[den-dog]

Same here. There is a sort of small work-around when you go into powertoys settings for FanzyZones and disable and enbale again:

Override Windows Snap - This overrides the Windows Snap shortcut (Win + arrow) to move windows between zones

So I fancy there is some sort of context loss when activating workspaces, coudl it overide the Fancy zone layout?

[plante-msft]

/dup #34566

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